Plugin checklist
Last reviewed October 24, 2026
Go through this before you post the link anywhere. Each item points back to the step that explains it.
Can people find it?
- The repository description says what the plugin does and for which agents, and the topics name each agent (publish).
- The README has the lines to add the marketplace, install, update and remove (publish).
- Each agent you name finds a manifest where it looks (other agents).
This site lists only skills, plugins, plugin marketplaces and MCP servers, and decides from the repository itself. A plugin or marketplace shows up here when one of these is true:
- a manifest folder or file sits at the root:
.claude-plugin/,.codex-plugin/,.cursor-plugin/,.plugin/orgemini-extension.json; - a root
plugin.jsonis an agent plugin's: it has an Agent Plugins or Antigravity$schema, component keys such asskills, or nothing but plugin metadata. Plenty of applications keep aplugin.jsonof their own, so one without these does not count; - a
skills/folder sits at the root, unless it sits beside a build file and a source folder, which marks it as an application's own; - it has a topic such as
claude-code-plugin,agent-plugins,codex-pluginorgemini-cli-extension; - its description calls it a plugin, extension or marketplace for a named agent ("a Claude Code plugin for…"), or its name says skill and the README has an install command such as
/plugin marketplace add,gemini extensions installoragy plugin install.
A name or description that calls the repository a demo, an example, an SDK, a framework or an awesome list cancels the last of those, since most such repositories are something else.
Will people trust it?
- The manifest has an author, a license and the repository, so people can tell where it came from (build).
- The README lists every skill, command, server and hook, and what each hook runs (publish).
- Hooks are few and short, every outside source in the marketplace is pinned to a commit, and no key appears anywhere in the repository (safety).
- Nothing in the manifest or README tells the agent to set aside its own rules. This site's safety scan looks for that.
Can you keep it working?
claude plugin validate --strictpasses, in CI as well as on your machine (build).- You installed it from your own marketplace the way a user will, before you pushed (marketplace).
- Every release people should get has a new version, a tag and a changelog entry (publish).
- Each skill in the plugin passes the skill checklist too (skill checklist).
- Issues get answers. An open, answered issue tracker tells a new user more than any badge.
Building something else? See the guides to a skill and an MCP server.