Skill 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 skill does and for which agents, and the topics include
agent-skills(publish). - The README has an install line for each way people install it (publish).
- It works in the agents you name, from the folders they read (port).
This site lists only skills, plugins, plugin marketplaces and MCP servers, and decides from the repository itself. A skill shows up here when one of these is true:
- there is a
SKILL.mdat the root, or askills/folder of them. Askills/folder next to a build file and a source folder is read as an application's own, and does not count; - a plugin or marketplace manifest, such as
.claude-plugin/, sits at the root; - it has a topic such as
agent-skills,claude-code-skill,codex-skillorgemini-cli-skill; - it is listed on skills.sh;
- its description calls it a skill for a named agent ("a Claude Code skill for…"), or its name says skill and the README has an install command.
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?
- It triggers on the prompts it should and stays quiet on the near misses (test).
- It does better than the agent does without it, on cases you wrote down (test).
- The README says what it runs, writes and sends, and the installed copy says who made it (publish).
allowed-toolslists only what it needs, and its scripts take--helpand--dry-run(safety).- No key appears anywhere in the repository, and nothing tells the agent to set aside its own rules. This site's safety scan looks for both.
Can you keep it working?
- It passes the validator, and uses only the standard's fields if you mean it to travel (write).
- The trigger prompts and test cases live in the repository, so every change can be checked against them (test).
- Each release has a version, a tag and a changelog entry (publish).
- Issues get answers. An open, answered issue tracker tells a new user more than any badge.
Building something else? See the guides to a plugin or marketplace and an MCP server.