How skills are listed and graded
The directory lists public Agent Skills that pass a published, mechanical check. This page is the whole method: where skills come from, what is checked, what gets a page of its own, and how to change a listing.
Where the skills come from
The directory reads the repositories cited by at least two of these 8 curated lists: BehiSecc/awesome-claude-skills, ComposioHQ/awesome-claude-skills, VoltAgent/awesome-agent-skills, heilcheng/awesome-agent-skills, hesreallyhim/awesome-claude-code, karanb192/awesome-claude-skills, skillmatic-ai/awesome-agent-skills, travisvn/awesome-claude-skills. It adds the official collections those lists name and repositories accepted through listing requests. Every SKILL.md in those repositories is read from the default branch, except in hidden folders and dependency or build folders (node_modules, vendor, dist, build), and nothing in them is executed. Accepted requests may name exact canonical skill folders, including a publisher’s hidden distribution folder; only those reviewed roots and skill names are included. System skills, unreviewed mirrors and fixtures remain excluded. This snapshot was taken on October 19, 2026.
The Suede Skill Check
Reviewed listings may also supply supplementary citations from independent curated collections. Each document is pinned to a commit, checked for a direct repository link and reverified on refresh. These citations use the same scoring rubric and do not expand the discovery lists above.
Every SKILL.md runs through a required frontmatter check and seven graded checks: five on the SKILL.md format, following the Agent Skills format, plus a declared license and a commit to the repository in the last year. These checks decide the listing. The quality score then measures how much each listed skill gives an agent to work with.
| Check | What passes | Listed skills passing |
|---|---|---|
frontmatter | Frontmatter parses and declares a name and a description | 3,798 of 3,798 |
name_format | Name uses lowercase letters, digits and hyphens, 64 characters or fewer | 3,798 of 3,798 |
name_matches_folder | Name matches the skill's folder name | 3,682 of 3,798 |
description_length | Description is between 50 and 1,024 characters | 3,789 of 3,798 |
description_trigger | Description says when an agent should use the skill | 2,734 of 3,798 |
concise_body | SKILL.md body is 500 lines or fewer | 3,696 of 3,798 |
license | A license is declared in the frontmatter or the repository | 3,798 of 3,798 |
maintained | Repository has a commit in the last 12 months | 3,798 of 3,798 |
How the quality score is built
The score adds whole points from eleven components, all read from published evidence: the SKILL.md frontmatter, description and body, the files in the skill folder, the repository’s last commit and the curated lists that cite it. The rubric totals 100 points.
| Component | Points | How the points are earned |
|---|---|---|
| Structural checks | 56 | 8 points for each of the seven graded checks |
| Description length | 5 | 5 for 150–600 characters; 3 for 100–900; 1 for 50–1,024 |
| Boundary clause | 4 | 4 when the description says when not to use the skill (“Not for …”, “Do not use …”, “Use … instead”) |
| Example request | 3 | 3 when the description quotes an example request (3–60 characters in quotation marks) |
| Instruction depth | 7 | 7 for a SKILL.md body of 500–3,000 words; 4 for 250–4,500; 1 for 100 or more |
| Reference files | 3 | 3 when the skill folder ships a references/, reference/ or docs/ folder |
| Bundled scripts | 2 | 2 when the skill folder ships a scripts/ folder |
| Recent maintenance | 9 | 9 for a repository commit within 30 days of the snapshot; 6 within 90; 3 within 180; 1 within 365 |
| Curated-list citations | 7 | 7 for a repository cited by four or more curated lists; 4 for three; 3 for two; 1 for one |
| Tool permissions declared | 2 | 2 when the frontmatter declares allowed-tools |
| Compatibility declared | 2 | 2 when the frontmatter declares compatibility |
The published score is the total, capped at 99. 100 is reserved: structural evidence can show that a skill is well formed, well described, documented and maintained, but it cannot prove a skill perfect, so the scale tops out at 99. All arithmetic uses whole numbers; nothing is rounded. Missing evidence earns zero points for its component. A source fetch failure is unscored and stops a refresh from replacing the published snapshot.
Grades in this snapshot
| Grade | Score | Listed skills |
|---|---|---|
| A | 90–99 | 125 |
| B | 80–89 | 1,576 |
| C | 70–79 | 1,373 |
| D | 0–69 | 724 |
Across 3,798 listed skills, the highest score is 95 and the median is 78. No listed skill scores 96–99, and 1,701 score 80–99 and carry the quality shields. Failed required frontmatter receives grade F and is not listed.
The score measures the recorded SKILL.md structure and description, instruction depth, bundled files, license declaration, maintenance and citation evidence. It does not measure runtime performance. Frontmatter is a separate required gate; a declared license and all listing-policy rules still apply.
Security scan status is separate
External directory skills are marked not scanned. The HOL/Cisco CI scanners run on Suede’s own repository; their results do not certify the external repositories listed here. The shields’ “Suede Certified” label refers to the published structural quality check. A security result needs its own per-skill scan evidence.
Two README badges and a limited-time feature offer
Skills scoring 80–99 receive separate numeric and A/B shields, each linking to their actual Suede listing. Scores from 90–99 and grade A use gold; scores from 80–89 and grade B use cool metallic styling. The Suede S remains the main mark on both shields. Every listed skill, at any score, keeps its listing badge, and its existing badge.svg and score.svg links keep working.
Display either the numeric or letter badge in your repository or skill README, linked to your Suede listing, then request verification. Displaying both also qualifies. Suede checks the rendered README at a recorded commit before a feature placement is activated. An unverified request, no valid linked badge or failed fetch cannot activate promotion. Verification is checked again after a dataset refresh. Existing editorial full pages keep their separate rules.
Limited-time feature offer: display either the numeric or letter badge in your repository or skill README (both also qualify), then request badge verification. Eligible skills scoring 80–99 can receive a featured placement after Suede verifies at least one valid badge linked to the skill’s listing. Suede has not announced an end date.
Scored below 80? We welcome authors who want help improving their skills. Each full skill page lists its points by component. Send your repository and the points you want to raise, then request a new review after updating the skill.
Listing rules
- The required frontmatter check, a declared license and at least six of the seven graded checks on the Suede Skill Check. Every listed skill shows its quality score and grade.
- A license declared in the SKILL.md frontmatter or the repository. Every listing states it; 97% of listed skills use an open-source or open-content license, and pages for the rest flag the terms next to the license.
- A description written mainly in English, so the directory's pages read consistently.
- Templates, examples, drafts, test fixtures and folders named archive, deprecated, internal or prompts, or starting with an underscore, are skipped.
- One listing per skill. A copy is the same skill name with a mostly matching description, or a description repeated word for word under another name. When copies appear in several repositories, the copy in the repository cited by the most lists keeps the listing.
- Skills are not listed when they:
- automate posting, messaging or account activity on a social platform (skills that draft posts or replies for a person to approve are listed);
- work around a site's blocks, CAPTCHAs or official API;
- have scraping a third-party site as their main job;
- collect people's personal data by scraping a social network or map listings (skills that use licensed B2B data providers within their terms are listed).
- Skills are also left out when their name or description trips the site's content filters: adult content, malware terms, jailbreaks outside a defensive context, the short list of terms the site's own public-copy guard rejects, and listing text that fails the site's public-privacy check (an email address, a phone number or a home-directory path). The exact terms are in curate.py. Removals at an author's request, and skills whose text matches the pack's reserved-text guard, are recorded with their reason in exclusions.json.
- Suede's own skills are catalogued separately on this site and pass the same rules; a test in the repository checks every one of them against the policy.
Which skills get a full page
Every listed skill appears in its category directory and on its repository's page. Skills that pass all seven graded checks get a page of their own once the directory's editors have written their one-sentence summary, up to twelve per repository, chosen by how much ships with the skill: reference files, scripts, assets and a structured SKILL.md. A skill keeps its page while it stays listed, so its README badge and link keep working. Each page carries the summary, a pre-install list of the scripts, commands, environment variables and network use found in the skill's files, install steps (or, where the license restricts copying, the publisher's terms), and a README badge. 733 skills have a full page in this snapshot. A repository whose single listed skill has a page is listed through that page.
Categories
Categories group skills by their main task, so you can compare alternatives side by side. Each skill sits in one of 16 categories, assigned from its name and description.
Refreshes and changes
Each refresh re-reads the source repositories, so quoted descriptions, file facts and check results follow the published SKILL.md. To request a listing, a correction or a removal, use the listing request page; requests are reviewed by hand.