All terms
Agents & toolsUpdated 15 days ago

Skill (Claude Skills)

Also known as: skill, SKILL.md, Claude skill, Agent Skills (open standard)

A folder containing a SKILL.md file that gives Claude a reusable, named capability — like "write a PR description" or "format a sales email" — which Claude loads only when your request matches the skill's description, with no retraining or fine-tuning.

What it means

A Claude Skill is a folder containing a SKILL.md file (and optional supporting files) that defines a named capability Claude can invoke. The SKILL.md has YAML frontmatter with metadata — name, description, when to use it — and a markdown body with instructions, examples, and links to helpers. Drop it in ~/.claude/skills/ and Claude can use it. Skills load by progressive disclosure, in three stages. At startup Claude reads only each skill's name and description from the YAML frontmatter, which costs on the order of tens of tokens per skill. When a request matches that description, Claude loads the full SKILL.md body into context. Only then, while following the instructions, does it open any bundled reference files or scripts the skill points to. This is why a skill's description field matters more than anything else in the file: it is the only part Claude sees when deciding whether the skill applies, so it has to state both what the skill does and when to use it. It is also why you can install many skills without paying a context penalty for the ones you are not using. Think of them as discrete, shareable units of capability that do not require API keys, fine-tuning, or running a server. The format is no longer Claude-specific. Anthropic created it and then released it as Agent Skills, an open standard (specified at agentskills.io), and the same SKILL.md folder now works across a long list of other agents: VS Code and GitHub Copilot, Google's Gemini CLI, OpenAI's Codex, Cursor, JetBrains Junie, and Block's Goose all support it. A skill you write for Claude Code is a portable asset, not a vendor lock-in. Compared to MCP servers (which expose tools and require running code), skills are pure markdown — easier to author, share, and version-control. In practice teams use skills for: codifying internal style guides ("write a PR description like our team does"), wrapping common workflows ("triage a bug report"), and embedding domain knowledge ("explain this FERC regulation"). They're a low-friction way to make an LLM consistently good at something specific.

Example

You create ~/.claude/skills/pr-description-writer/SKILL.md with your team's PR template and tone rules. Anyone on the team running Claude Code with that skill installed gets consistent, on-brand PR descriptions automatically.

Why it matters

Skills are how Claude scales beyond one-off prompts without becoming a fine-tuning project. They make organizational AI knowledge portable, version-controllable, and reusable. If you're tired of pasting the same instructions into every chat, you should be writing a skill.

Related terms

See it in a comparison

Recent changes
  • Aug 27, 2026Noted that the format is now Agent Skills, an open standard originated by Anthropic and supported by VS Code, GitHub Copilot, Gemini CLI, OpenAI Codex, Cursor, JetBrains Junie, and Block Goose; a skill written for Claude is portable across agents.
  • Aug 20, 2026Added the progressive-disclosure loading model (name and description at startup, SKILL.md body on match, bundled files during execution) and led the definition with the SKILL.md folder structure.

Related skills

Get the digest — new glossary terms, skills, and tool updates in your inbox.