skillsrun

method

How we list Claude skills, and what we do not claim

Every row on this site can be checked in five minutes: the command installs, the prompt fires, or it does not.

What this page is

An independent, short list of Claude skills — eighteen of them — where every entry has to earn its row by being usable: an install command that works, a description of the job it does, the phrasing that makes Claude reach for it, and one prompt you can paste.

It is not affiliated with Anthropic, Vercel, skills.sh, or any repository named on the site. It does not host, mirror, or sell skills. Every skill stays with its authors.

How an entry gets made

  1. Pick from the leaderboard. We read the public skills.sh leaderboard, plus the repositories behind it, and pick skills that solve a job a developer actually repeats. Install counts and first-seen dates come from those pages.
  2. Read the skill itself. The one-line purpose and the "reach for it when" column are written from the skill's own SKILL.md description — what it says it does, not what we wish it did.
  3. Write the trigger. Every skill is matched on its description, so we write the ask the way that description reads. If a skill says it reviews a diff, the prompt says "review my working tree", not "check my code".
  4. Date it. Counts are stamped with the day they were read (currently 2026-11-19). They move; when a number is re-read, the stamp moves with it.

What we do not claim

We do not publish benchmark scores, speed comparisons, or "we ran this for six hours" anecdotes. Running an agent skill is not reproducible enough for a number to mean the same thing on your machine as on ours. What is reproducible is the command, the trigger and the example — so that is what each entry gives you, and you can falsify all of it in five minutes.

Install count is a popularity signal. A skill can sit at 1.6M because its repository is installed whole, not because it is six times better than the one at 260K. Sort by your task, not by the number.

How to get something corrected

If a command is wrong, a skill has been renamed, or an entry describes something the skill no longer does, that is worth fixing immediately. Send a correction to the domain owner listed in the WHOIS record for this domain; corrections that come with a link to the current SKILL.md get applied first.

Who writes it

One operator, building and shipping small web products, who got tired of installing skills that never fired and started writing down which phrasing works. That is the entire editorial process.

Questions people actually ask

Are any of these listings paid placements?
No. Nothing on the site is sponsored, and no repository pays for a row, an order, or a badge. The links to skills.sh pages and GitHub repositories are there so you can check the source yourself.
Where does each field come from?
The install command, the repository and the install count come from the skill's own page. The "reach for it when" line is written from its SKILL.md description, and the prompt is one written to match that description. There are no benchmark numbers anywhere on this site, deliberately.
How often is it updated?
Install counts are cumulative and stamped with the date they were read — currently 2026-11-19. The list is re-checked when a skill is renamed or its command changes, which currently happens often because most of these skills first appeared in January 2026.
Why only eighteen skills?
Because the whole ecosystem is under a year old and the composition of the top of the leaderboard shifts monthly. A long list of stale names is worse than eighteen entries someone actually maintains.