List your agent skill

How it works

1. Publish the skill in a public GitHub repository as a folder with a SKILL.md, a license and a description that says when to use it.
2. Open a listing request with the repository URL. One request can cover the repository or specific named skills; a request naming selected skills covers only those accepted names.
3. The request is reviewed by hand. An accepted repository is read at the next directory refresh and runs through the Suede Skill Check and the listing rules. Skills that pass the frontmatter check, declare a license and pass at least six of seven graded checks are listed with their quality score and grade.
4. Add either badge. Listed skills scoring 80–99 get two shields: a numeric score and an A/B grade, each linking to their Suede listing. Choose either badge or both from the listing and request README verification for the limited-time feature offer.

Improve your score

Below 80? Send your repository and ask for help with the points you want to raise. Authors are welcome to improve their skill and request a fresh review; skills that reach 80 add the numeric and letter quality shields.

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.

• Start SKILL.md with YAML frontmatter that declares name and description.
• Use a lowercase, hyphenated name that matches the folder name, 64 characters or fewer.
• Write a description of 150 to 600 characters that says what the skill does and when to use it, for example "Use when ...", names when not to use it ("Not for ..."), and quotes an example request.
• Give the agent 500 to 3,000 words of instructions, in 500 lines or fewer; move long reference material into a references/ folder and helper scripts into a scripts/ folder.
• Declare allowed-tools and compatibility in the frontmatter.
• Declare a license in the frontmatter or ship a LICENSE file in the repository, and keep the repository maintained: recent commits earn up to 9 points.

The scoring rubric lists every component and its points.

Updated your skill?

Choose Request a fresh review on the skill’s report or repository listing. The form carries the exact skill name and previous snapshot. Add the changed commit or pull request and the points you improved. Suede reviews requests by hand and rechecks accepted changes at a directory refresh.

Each listing offers a downloadable JSON report with its snapshot date, report version, score breakdown and methodology. Source commit IDs appear when recorded by the refresh; older snapshots say when the revision was not recorded. External skills remain marked not scanned.

Corrections and removals

Use the same request form to correct a category, update details or remove a listing. Removals take effect at the next build.