agent skills
directories.
Agent Skills directories solve different discovery problems. skillZs and skills.sh surface install activity, SkillsMP searches a broad GitHub-derived catalog, and Agent-Skills.md accepts direct repository submissions. The best directory is the one that exposes enough source evidence for your decision; no listing, star count, or install total replaces reviewing the actual skill.
Written and checked by skillZs.
How do the main Agent Skills directories compare?
| Directory | Best for | Discovery and ranking | Evidence to inspect |
|---|---|---|---|
| skillZs | Cross-client discovery plus practical guides | Live skills.sh API views for all-time installs, trending, and hot activity | Full manual, canonical source, install command, duplicate status, and available partner audits |
| skills.sh | CLI installation and adoption-ranked discovery | Anonymous skills CLI installation telemetry powers its leaderboard | Source repository, skill files, install count, topics, and available security audits |
| SkillsMP | Broad GitHub search by keyword, creator, category, or occupation | Daily GitHub indexing; stars and recency are visible discovery signals | SKILL.md, repository, creator, update date, stars, forks, and compatibility information |
| Agent-Skills.md | Direct URL submission and consistent skill previews | Parses valid GitHub skill folders submitted through its public form | Rendered SKILL.md, repository, author, file tree, download, and install commands |
These catalogs overlap but are not interchangeable. A broad index may maximize recall while an adoption-ranked view helps identify established workflows. Use the skillZs Agent Skills directory for live comparison, then open the source repository before deciding.
Which Agent Skills directory should you choose?
- Choose skillZs when you want source-aware discovery, live install views, security context, and guides in one place.
- Choose skills.sh when the skills CLI and its installation leaderboard are your primary workflow.
- Choose SkillsMP when you need broad GitHub coverage or want to search by creator, repository, category, or occupation.
- Choose Agent-Skills.md when you want a repository parsed through a direct public submission path.
Do not force a single winner. Search more than one directory when the task is niche, compare no more than a few credible candidates, and follow the safe installation guide before copying files or running commands.
What do directory rankings actually prove?
Install counts show adoption, stars show repository attention, recency shows maintenance activity, and audits show the result of one defined check. None proves that a skill fits your task, remains safe after an update, or works in your client. The live rankings guide explains how skillZs uses install data without treating popularity as endorsement.
Prefer transparent inputs over unexplained scores. Check the publisher, complete instructions, bundled scripts, dependencies, permissions, network behavior, tested clients, revision, and license. Use the Agent Skill security checklist for a repeatable review.
How do creators get listed in each directory?
| Directory | Documented path |
|---|---|
| skillZs | Publish to the skills.sh ecosystem; eligible non-duplicate API records are mirrored automatically. |
| skills.sh | Host the skill on GitHub and earn installations through npx skills add owner/repo; anonymous telemetry can add it to the leaderboard. |
| SkillsMP | Use a public GitHub repository with valid frontmatter and the documented claude-skills or claude-code-skill topic, then wait for daily synchronization. |
| Agent-Skills.md | Paste the GitHub repository or skill-folder URL into its public submission form. |
Start with the creation guide, verify the public source, and use the publishing guide to document compatibility, permissions, installation, and trust signals. Distribution should follow a useful tested workflow, not replace one.
How should you verify a directory result?
- Confirm the listing links to a canonical public source.
- Read the full
SKILL.mdand every referenced executable file. - Check the exact tools, credentials, network access, and write permissions required.
- Separate adoption signals from audits and audits from guarantees.
- Install in a disposable project and test one reversible task.
- Record the revision and re-review meaningful updates.
The Agent Skills Ecosystem Report documents why source concentration and install data need careful interpretation. skillZs also publishes its ranking methodology and catalog policies so those limits remain inspectable.
What do people ask about Agent Skills directories?
Which Agent Skills directory should I use?
Use the directory whose evidence matches your decision. skillZs and skills.sh emphasize install activity, SkillsMP provides broad GitHub discovery, and Agent-Skills.md accepts direct repository submissions. Always inspect the canonical source before installing.
Which directory has the safest Agent Skills?
No directory can make every listed skill safe. Check the complete SKILL.md, scripts, dependencies, permissions, source history, and exact revision. Treat install counts, stars, and directory inclusion as discovery signals rather than security certification.
How can I list my own Agent Skill?
Publish a valid SKILL.md in a public GitHub repository. skills.sh can discover it through skills CLI installs, SkillsMP documents daily GitHub synchronization using relevant repository topics, and Agent-Skills.md accepts a direct GitHub folder URL.
Are Agent Skills directories the same as package registries?
Not necessarily. Most directories index files hosted in source repositories and provide discovery or install guidance. Verify the source, license, revision, and installation behavior instead of assuming package-registry guarantees.
Which sources support this directory comparison?
This guide was checked against the official skills.sh FAQ and CLI reference, the SkillsMP FAQ, the Agent-Skills.md directory and submission documentation, and the public skillZs methodology. Features and indexing policies can change, so follow each primary source for current submission rules.