Claude Code skills

A catalogue of ready-made SKILL.md files for Claude Code — development, testing, docs, DevOps, marketing. Cards and search are open to everyone; files come with a subscription.

Claude Code skills are SKILL.md files that hand Claude Code a ready instruction for a specific job: how to review code against your standard, how to write documentation, how to assemble a report, how to ship a service. The file goes into the `.claude/skills` folder of your project, and from then on Claude invokes it by itself whenever a task matches its description — you do not have to ask for it in every message.

What separates a skill from a prompt is where it lives and when it fires. A prompt is retyped every time and kept in your head or your notes; a skill sits in the repository next to the code, goes into git, works for the whole team and is selected by the meaning of the task. That is why skills are used for the repeatable work: code-review rules, commit and release conventions, framework-specific practice, log analysis, report exports, front-end acceptance checks.

The catalogue holds more than ten thousand skills — open repositories, read and described one by one, plus the platform's own. Every card states what the skill does, which task to reach for it on, and how it differs from its neighbours; a machine-generated folder name tells you none of that, so names and descriptions are rewritten in plain language. Search runs on the meaning of the task rather than word matching: a query like "check dependency security" finds the right skill even when none of those words appear in its name.

Skills are sorted by job: development and review, testing, documentation, data work, DevOps and infrastructure, security, marketing and content, process automation. One shelf is separate — the platform's own skills. These are pipelines that do complete work on top of the AI SKILLS MCP connector: building a video from idea to edit, preparing a product card, running Instagram analytics. They are free and they work straight from a Claude chat.

Getting started: find the skill for your job, download its SKILL.md, drop it into `.claude/skills/<name>/SKILL.md` in your project, and describe the task to Claude in ordinary words — it picks the skill itself. Nothing to configure, nothing to restart. Cards and descriptions are open without an account; the file itself and the link to the original source come with a subscription, starting from the Basic tier.

FAQ

What is a SKILL.md file and how is it different from a prompt?
SKILL.md is an instruction file that lives in your project repository and is picked up by Claude Code automatically when a task matches its description. A prompt lives in the conversation and is retyped every time; a skill goes into git, works for the whole team, and needs no reminding.
Where do I put a skill so Claude Code finds it?
In `.claude/skills/<skill-name>/SKILL.md` inside the project. Claude reads that folder on start and invokes the matching skill by the meaning of your task — nothing to restart and nothing to switch on.
How many skills can I have installed at once?
There is no cap on the number: keep as many in the folder as the project needs. Claude selects by description, so non-overlapping descriptions matter more than how many files sit side by side.
Do skills only work in Claude Code?
The SKILL.md format is built for Claude Code, where it is picked up automatically. The content is plain instruction text, so you can apply it in a chat as well, but automatic task-based invocation exists only inside Claude Code.
How is this catalogue different from searching GitHub?
On GitHub skills sit inside other people's repositories under machine-generated folder names that tell you nothing about what they do. Here every skill has a human name and a written description, and search works on the meaning of the task rather than matching words.
What is open without a subscription?
The whole catalogue: cards, descriptions, categories and search. What is closed is the SKILL.md file itself and the link to the original source — those open from the Basic tier, and advanced skills from Creator.
How do I tell a maintained skill from an abandoned one?
The card shows which repository the skill comes from and when it was last updated, and the description is written from the actual contents of the file. Cards whose source has gone dead are deactivated, so broken links do not pile up.
Can I write my own skill?
Yes, and it is an ordinary markdown file: a title, the task it covers, and the instruction. The catalogue even has skills that help Claude Code write a new skill from your description.