Standards
Anyone can zip up instructions and call it a skill.
You would be the one who finds out it does not work, halfway through a job. These ten checks are what a skill goes through before it is admitted here. They catch the failures that can be checked in advance, in the packaging, the claims, and representative runs, and they make the remaining boundaries visible instead of leaving you to find them.
No skill is marked admitted until all ten hold, and the checks are graded from what a run actually produced rather than from what its author says about it. Skills still being checked are listed separately as in validation, and those are not for sale.
The upload zip is under 50 MB and holds one top-level directory named exactly the skill name, with SKILL.md at that directory root.
Packaged the way assistants expect, so it loads instead of quietly doing nothing.
SKILL.md carries valid frontmatter with a name and a description.
The folder states its own name and purpose, so your assistant knows what it is and when to reach for it.
Every relative link resolves inside the bundle.
Every file the instructions point at is actually in the folder, so the work does not stop halfway at a missing page.
The bundle contains no private paths, secrets, internal product details, proprietary prompts, or one harness’s commands presented as universal.
No stray secrets or private paths left in the folder, and no commands from one particular assistant passed off as universal.
The skill states required capabilities, optional paid routes, fallback behavior, support boundaries, and commercial-use caveats.
You learn what your assistant has to be able to do, what would cost extra on your own accounts, and where support stops, before you install.
At least three representative prompts have been run with and without the skill.
Nothing is admitted untried: the skill was tried on representative tasks, and against not using it at all.
Assertions are graded from generated artifacts, not self-reported by the author.
Claims are marked against the files a run actually produced, not against what the author says happened.
Included scripts pass syntax checks and, where applicable, at least one observable smoke scenario.
Code in the folder is checked and exercised, not just written, so basic breakage is caught before the bundle reaches you.
The listing copy makes no unsupported performance, revenue, compatibility, or customer claims.
The sales page has to hold up too: no invented numbers, no borrowed customers, no promise that it works everywhere.
Version, license, installation, and support documents match the shipped bundle.
The paperwork describes the folder you actually downloaded, so the install steps match what is in front of you.
The list is published in full so you can hold any skill to it, including the ones we list.