agent-marketplace

原文涵盖的主题

• agent-marketplace
• Quick Start
• Configuration
• Layers
• Sources and resource groups
• Output paths
• Shared aggregate ownership
• Locks

The full user documentation lives in the repository's site/docs. This skill caches what an agent needs most often; the CLI reference, configuration reference, and agent-marketplace --help own the exhaustive detail. For a new setup, use the example below. For an existing installation, first follow Convert before upgrading; do not overwrite authored configuration or relabel legacy fields as v4. Bare agent-marketplace on a terminal opens the TUI; on first launch it asks for the target harnesses. When no user config exists, a plain sync creates one with harnesses: [factory, windsurf], so declare targets first. apiVersion: agent-marketplace/v4 is the only supported consumer schema; init, install, remove, and the TUI create v4 files. Every existing root, including organization and personal-local, requires that exact string. An omitted root version fails with v4.api-version-required; explicit unsupported or invalid values fail with v4.api-version, naming the authored file and apiVersion field. Included fragments under a validated v4 root may omit the field or declare exact v4. An existing empty/versionless file is not absent. Unsupported input refuses before new acquisition, config/lock s

这里只展示节选，请以完整原文和当前要求为准。