Agent skills marketplaces: how each agent adds a catalog
There is no one skills marketplace for every agent. How Claude Code, Cursor, OpenCode, Gemini CLI, Codex and Copilot each add a catalog, from their own docs.
- For
- Developers who use more than one coding agent and want a shared skills catalog
- Written for
- Claude CodeCodexCursorGitHub CopilotGemini CLIOpenCodeAny agent that reads SKILL.md folders
- Time
- 8 min read · updated Nov 21, 2026
The short answer
There is no single marketplace for agent skills, because each agent has its own way to add a catalog. Claude Code adds a plugin marketplace with /plugin marketplace add. Cursor imports a GitHub repository only if it has a .cursor-plugin/marketplace.json. OpenCode takes a local folder or an HTTP catalog in its skills setting. Gemini CLI installs from a git URL with gemini skills install. Codex has $skill-installer and a plugin directory. What works in all of them is a plain skill folder, copied to where that agent reads.
Searching for an agent skills marketplace turns up directories, registries and stores, and most of them list skills for one agent or just index GitHub. The agents themselves each ship a catalog mechanism, and they are not the same. This page puts those mechanisms next to each other, using each maker’s documentation read on 21 November 2026, so you can see what “add a marketplace” means in the agent you use, and what you can share across all of them.
Catalog mechanisms, agent by agent
Claude Code
Anthropic’s documentation defines a marketplace as a directory or repository with a .claude-plugin/marketplace.json file that lists plugins and where to fetch each one. You register it with one command and install plugins from it by name. A plugin is the unit, and a plugin can hold skills, agents, hooks and MCP servers, so a catalog of skills in Claude Code is a marketplace of plugins that carry them.
The comparison of the sources Anthropic and others offer is in the Claude skills marketplace guide, and the plugin side is in the best Claude Code plugins. To publish a marketplace of your own, see how to build and host a Claude Code plugin marketplace.
Cursor
Cursor does not import loose skills from a repository. Its documentation says to package them in a plugin and publish that plugin through a marketplace. You then import the repository in Customize with From GitHub Repository, and the repository needs a .cursor-plugin/marketplace.json, or you add it as a team marketplace and install the plugin. The skills appear in Customize with your others. Cursor agent skills walks through each route, including the folders and Cloud Agents. The Cursor Marketplace itself holds official plugins distributed as Git repositories and, the docs say, every one is manually reviewed before it is listed; team marketplaces are a Teams and Enterprise feature.
OpenCode
OpenCode’s catalog can be just a folder or a web address. Its skills setting takes a list of sources: local directories, or an HTTP catalog. An HTTP catalog is a base URL with an index.json that lists each skill by name, version and files. OpenCode downloads each file from the base URL, requires the paths to be safe, relative and same-origin, and refreshes its cache only when you raise version. The documentation also says OpenCode reads ~/.claude/skills and ~/.agents/skills without any setting.
Gemini CLI
Gemini CLI installs a skill straight from a git repository. By default it installs for you; --scope workspace installs for the project, --path picks a sub-directory of the repository, and --consent skips the security confirmation, which you should not do for a repository you have not read. /skills link <path> links skills from a local directory instead. Skills can also arrive bundled in a Gemini extension.
Codex
Codex’s documentation separates two things. For your own machine, $skill-installer installs curated skills from openai/skills (whose README now says the repository is deprecated), and you can prompt it to download skills from other repositories. For sharing, it says to package skills as a plugin, distributed through a plugin directory that ChatGPT and Codex share. The openai/plugins repository describes itself as a curated collection of Codex plugin examples, with its default marketplace at .agents/plugins/marketplace.json and a .codex-plugin/plugin.json manifest for each plugin. Best Codex skills sorts the curated skills by job.
GitHub Copilot
GitHub’s documentation says you can use gh skill in GitHub CLI to discover and install skills from GitHub repositories, and names github/awesome-copilot as a community collection. Copilot reads personal skills from ~/.copilot/skills or ~/.agents/skills.
What works across all of them
Because a skill is a folder with a SKILL.md, the one thing every agent above reads is a folder in the right place. Three routes work without each agent’s marketplace at all.
- A shared folder.
~/.agents/skills/is read by Codex, Gemini CLI, OpenCode, Cursor and GitHub Copilot, according to each one’s docs. Claude Code reads~/.claude/skills/instead. OpenCode also reads~/.claude/skills, and Copilot reads.claude/skillsinside a project. - The skills command.
npx skills add owner/repoasks which skills and which agents to install to. Its README says it supports Claude Code, Codex, Cursor, OpenCode and 75 more, and installs into the current project unless you add-g. Vercel skills (npx skills) covers its commands and what to check first. - Copy the folder. Clone the repository and copy the skill’s folder into each agent’s folder by hand; Claude skills on GitHub compares the main repositories to copy from, and awesome Claude skills the lists that point to more. Where skills live lists every folder and which wins when two hold the same skill.
If you maintain skills for a team, the cleanest setup is one repository with a skills/<name>/SKILL.md layout. Anyone can copy from it today, and you can wrap it in a marketplace file later for each agent that needs one: .claude-plugin/marketplace.json for Claude Code, .cursor-plugin/marketplace.json for Cursor, an index.json for OpenCode.
Before you add a catalog
Adding a marketplace gives its owner a way to put code and instructions in front of your agent, and each update can change what they say. Anthropic’s plugin documentation says plugins can run arbitrary code with your user privileges and that it does not review third-party marketplaces. Treat a catalog in any agent the same way.
Where Lookbk fits
Lookbk’s skills are plain SKILL.md folders, so they work through the folder route in every agent above, and the installer writes ~/.agents/skills/ and, when Claude Code is installed, ~/.claude/skills/. Each skill page shows what the skill rendered before you install it. These four are free.
To install one, run the installer with the last part of the skill page’s address, then start a new session. Install a skill in any agent covers each agent.
Common questions
- Is there one marketplace for agent skills?
- No. Each agent documents its own way to add a catalog: plugin marketplaces in Claude Code and Cursor, a skills array in OpenCode,
gemini skills installin Gemini CLI,$skill-installerand a plugin directory in Codex, andgh skillfor Copilot. A skill folder copied into the right place works in all of them. - Can I use the Claude Code marketplace in Cursor?
- Not directly. Cursor’s documentation says a repository must contain
.cursor-plugin/marketplace.jsonto be imported from GitHub, and that skills arrive inside a plugin. A repository can hold both marketplace files side by side. - Does OpenCode have a skills marketplace?
- Not a store. Its documentation lets you add local directories or an HTTP catalog to the
skillssetting; an HTTP catalog is a base URL with anindex.jsonlisting skill names, versions and files. - How do I install a skill in Gemini CLI?
- Run
gemini skills installwith a git repository URL. Add--pathfor a sub-directory,--scope workspacefor one project, and read the skill first rather than using--consentto skip the security prompt. - Is there one folder that most agents read?
~/.agents/skills/is read by Codex, Gemini CLI, OpenCode, Cursor and GitHub Copilot per their docs. Claude Code reads~/.claude/skills/, so a skill that must work everywhere is copied to both.- Is a skill from a marketplace safe to run?
- Not by default. A marketplace is a way to find and install skills, not a review of them. Read
SKILL.mdand any scripts first.
Sources
What this guide says about other companies’ tools comes from their own documentation, checked on Nov 21, 2026.
- Claude Code: create a marketplace (opens in a new tab)
- Claude Code: host and maintain a marketplace (opens in a new tab)
- Cursor: skills (opens in a new tab)
- Cursor: plugins (opens in a new tab)
- OpenCode: skills (opens in a new tab)
- Gemini CLI: agent skills (opens in a new tab)
- Codex: build skills (opens in a new tab)
- GitHub: openai/plugins (opens in a new tab)
- GitHub Docs: about agent skills (opens in a new tab)
- GitHub: vercel-labs/skills (opens in a new tab)
Did this guide help?
Read next
All guidesClaude skills marketplace: where to get skills in 2026
There’s no single Claude skills marketplace. Compare Anthropic’s repo, plugin marketplaces, open directories and paid catalogs: cost and how to install.
Where skills live: folders for every agent
The folders Claude Code, Codex, Cursor and other agents read skills from, which copy wins when two share a name, and what cloud agents can see.
Install a skill in any agent
Install a Lookbk skill in Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI or OpenCode: where each looks, how to check it loaded and how to run it.
Claude Code plugins: install them, and the best ones
Claude Code plugins explained: browse the marketplace, install one with /plugin, pick a scope, then the best plugins by job, each checked at its source.
Claude skills on GitHub: main repos and how to use them
The GitHub repositories that hold Claude skills, checked on the GitHub API: license, last commit, skill count. Then how to copy one into your agent.
Best Codex skills: where to find them and which to install first
A shortlist of Codex skills by job from OpenAI’s own catalog, where Codex skills come from, how to install them and how many to keep. Read 21 November 2026.
Cursor agent skills: add a skill from GitHub, step by step
How to get a skill from a GitHub repository into Cursor: the folders it loads, the plugin route in its docs, Cloud Agents and the frontmatter.
Vercel skills: install agent skills with npx skills, and what to check
How the npx skills command from Vercel Labs installs agent skills from GitHub into Claude Code, Cursor, Codex and more, where it writes and what to check.
See a skill’s result before you install it.
Every skill page shows what it makes, what it needs and which agents can run it.



