Documentation
agent-marketplace is a command-line tool that installs shared AI agent resources into your coding tools. A resource is a skill, command, subagent, hook, or MCP server. The tool downloads resources from Git registries or a hosted Marketplace and writes each one into the folders your coding tool reads. These docs call each coding tool a harness. Eight are supported: Claude Code, Codex, Cursor, Devin, Factory Droid, Gemini CLI, OpenCode, and Windsurf.
Start here
New to the tool? Follow the quick start. In about ten minutes you install the tool, select a skill from a public registry, look at it in the terminal UI, and commit the configuration so teammates can reproduce the setup. More install options covers release downloads and building from source.
Look up unfamiliar words in the glossary. Then pick the section that matches your goal.
I use agent resources in my projects
You want skills and other resources in your editor, and you want them to stay the same for everyone on the team.
The user-journey map follows a resource from finding it to recovering it. It links to the guide for each stage.
| Goal | Read |
|---|---|
| Install one skill from Git, end to end, on Claude Code | Tutorial: install your first skill |
| Find and install your first skill from an online Marketplace | Tutorial: install your first Marketplace skill |
| Read a resource's content and security findings, or inspect an older revision | Browse and inspect Marketplace resources |
| Add agent-marketplace to a repository the team shares | Adopt in a repository |
| Make CI prove every clone gets the same files | Keep resources reproducible |
Figure out why sync --check is failing | Troubleshoot sync drift |
| Target more than one harness | Configure multiple harnesses |
| Remove a resource, or keep one out of a team default | Remove or override resources · Personal repository overrides |
| Install from a curated Marketplace instead of a raw Git URL | Install from a hosted Marketplace |
| Understand what the tool does | How agent-marketplace works |
Other guides for people who use resources:
- Find and install: install bundles · local registries · private Git registries
- Set up repositories and harnesses: regular files instead of symlinks
- Troubleshoot and repair: repair owned shared configuration · clean the cache
- Maintain and uninstall: back up machine resources · convert configuration before upgrading · telemetry · remove agent-marketplace
I publish resources for others
You maintain a Git repository of skills that other people install.
| Goal | Read |
|---|---|
| Create a registry from nothing and install from it | Tutorial: create your first registry |
| Add a skill or command | Add a resource to a registry |
| Ship a hook that runs a script | Publish a hook with support files |
| Make resources discoverable by tag and licensed | Declare tags and a license |
| Declare what a resource needs to be installed | Declare resource prerequisites |
| Ship a bundle consumers can install in one step | Publish resource collections |
| Catch broken resources before consumers do | Validate a registry in CI |
| Cut a release consumers can pin | Version and release a registry |
| Look up exactly which files are discovered | Registry layout · Resource metadata · Collections |
I operate a Marketplace
You run the hosted service that indexes and curates registries for an organization.
| Goal | Read |
|---|---|
| See the whole thing working on your laptop | Tutorial: run a local Marketplace |
| Add a registry from the admin panel for the first time | Tutorial: add your first registry |
| Deploy it for real | Deploy a production Marketplace · Test locally with Compose · Configure a reverse proxy |
| Review submissions and policy in a browser | Enable and use the admin panel |
| Index a registry that needs credentials | Connect a private registry |
| Decide what is allowed in | Manage ingestion policy |
| Pull something bad | Revoke a resource revision |
| Keep it healthy and recoverable | Reindex and monitor · Reset and reindex a registry · Back up and restore |
| Understand the moving parts and the trust boundary | Marketplace architecture · Marketplace trust model |
Reference
Exact descriptions of commands, files, and fields.
- CLI: command line · TUI · environment variables · diagnostics · logging · telemetry
- Consumer files: repository configuration · configuration layers · lockfiles · filesystem layout · harnesses and output paths
- Registry files: registry layout · resource metadata · resource prerequisites · collections · hook and tool names
- Marketplace: operator configuration · HTTP API · health and metrics · resource locators
Explanation
Why it works this way.
- Start here: user journeys · how agent-marketplace works · sources and resources
- Core model: scopes, selection, and precedence · native harness materialization · reproducibility and lockfiles · shared configuration ownership
- Marketplace and privacy: Git registries and hosted Marketplaces · Marketplace architecture · Marketplace trust model · telemetry and privacy