What are Claude Code skills — and why do they matter?

the problem

Every session starts from zero

By default, Claude Code has no memory of your previous sessions. Every time you open a new conversation, it starts fresh. You re-explain your tech stack, your coding conventions, your preferences for how components should be structured. You paste the same context every time. And if you're working with a team, every developer gets subtly different output because they write their instructions differently.

Even mid-conversation, context compaction can wipe earlier instructions. You asked Claude to always use TypeScript strict mode and now, ten messages later, it's back to generating loose JavaScript.

Agent skills solve this. Write your instructions once, and Claude loads them before every session — automatically, without you re-explaining anything.

what they are

A skill is a plain text file

An agent skill is a SKILL.md file — plain markdown — that contains instructions for Claude. When Claude Code starts a session, it reads every SKILL.md in your project and loads them into context automatically. The instructions are always there, even after context compaction, because the file is re-read at the start of each session.

There's nothing to install. No extensions, no API keys, no configuration. You drop a file in your project and Claude reads it.

# My frontend skill

Always use the App Router, never the Pages Router.
Prefer server components for data fetching.
Use shadcn/ui components — never write custom CSS for standard UI elements.
When in doubt, use TypeScript strict mode.

That's a skill. Three to five lines of clear instruction is enough to meaningfully change Claude's output. The best skills on theskills.directory encode what took experienced developers hours of iteration to get right.

global vs project skills

Skills can work across every project you own — not just one

This is the part most people miss. A SKILL.md in a project root works for that project. But Claude Code also supports global skills — skills you add to Claude itself, which load automatically for every project you work on, not just one.

To add a skill globally in Claude Code, place it in your user-level configuration directory (typically ~/.claude/skills/ or add it via Claude Code settings). Once it's there, Claude loads it before every session, in every project, on every machine that shares your configuration.

This is the right place for skills that aren't project-specific: your personal code review process, your preferred commit message format, your general quality standards. Project-level skills handle the per-repo conventions. Global skills handle everything else.

The combination means you never start a session from scratch again — your global skills provide the baseline, and the project's skills layer specific context on top.

why they're different from prompts

A prompt is what you write when you're in a hurry. A skill is what you keep when it worked.

The difference between a prompt and a skill is durability. A prompt lives in a conversation that ends. A skill lives in the repo, gets committed to version control, and works the same for every developer on your team — including people who joined last week.

When you find a prompt that gets Claude to generate exactly the kind of output you want — consistent, correct, in the right style — you're looking at a skill. Write it down. Commit it. Share it.

The skills on theskills.directory are the ones that worked well enough to share. Some of them represent weeks of iteration by experienced developers who spent real time refining the instructions until the output was reliable. You can install one in seconds with:

npx skillsadd anthropics/skills/frontend-design

cross-tool compatibility

The same skill works in Claude, Cursor, Copilot, and more

SKILL.md files aren't Claude-specific. The same file works across every major AI coding tool:

• →Claude Code — Read automatically from project root on every session
• →Cursor — Place in project root or paste into .cursorrules
• →GitHub Copilot — Loaded as project-specific context in VS Code and JetBrains
• →Gemini CLI — Pass as system prompt or place in project root
• →OpenAI Codex — Paste into system prompt when calling via API

This matters for teams that use multiple tools. One SKILL.md in the repo root covers the whole team, regardless of which tool each developer prefers. No per-tool configuration, no drift between environments.

getting started

Three ways to start

1. Install a community skill. Browse theskills.directory and copy a skill that matches your workflow. The most-copied skills — frontend design, code review, testing — have been refined by hundreds of developers. You get that iteration for free.

2. Install a curated stack. Browse the stacks — pre-configured collections of skills that work together. If you're building a Next.js SaaS, the Next.js SaaS stack has six skills that cover frontend conventions, database patterns, and testing. Install the whole stack with one command per skill.

3. Write your own. Start with what you wish Claude knew about your codebase. Three to five lines is enough. Commit it. See if the output improves. Refine it. If it gets good enough to share, submit it to the directory — the community benefits, and your skill gets a permanent home.

the bigger picture

Why this matters as the AI coding ecosystem matures

AI coding tools are getting better at raw code generation. The gap that remains is institutional knowledge — the conventions, standards, and patterns that make output consistent and trustworthy across a team and across time.

Skills are how that knowledge gets encoded and shared. Not as documentation that gets ignored, not as onboarding material that goes stale, but as active instructions that shape every session, every suggestion, every generated file.

The best engineering teams already have this figured out. They've invested in skills that encode their standards, committed them to the repo, and stopped re-explaining the same things to Claude every Monday morning. theskills.directory exists to make that knowledge accessible to everyone — starting with the 58 skills available today.