Skills: Bundled Procedural Knowledge

Skills are reusable bundles of instructions plus optional scripts and assets. They're how Claude Code learns a procedure once and reapplies it everywhere.

9 min · Reviewed 2026

What a skill is

A skill is a folder with a SKILL.md (the instructions), optional scripts (helpers the model can call), and optional assets (templates, examples). When the model recognizes that a user request matches the skill's description, it loads the skill and follows its instructions instead of improvising.

Where skills live

User-scoped: in `~/.claude/skills/<skill-name>/` — available across all projects
Project-scoped: in `.claude/skills/<skill-name>/` inside a repo — versioned and shared with the team
Plugin-scoped: shipped by official or third-party plugins, prefixed with the plugin name
Discoverable: the SKILL.md frontmatter description is what triggers the skill

Anatomy of a skill

---
name: release-notes
description: Generate user-facing release notes from recent commits. Triggers when the user asks for release notes, changelog, or what changed since version X.
---

# Release Notes

When invoked:

1. Run `git log --oneline <last-tag>..HEAD`.
2. Group commits by type (feat, fix, perf, docs).
3. Translate each commit subject into user-facing language.
4. Output as Markdown headed by the new version.
5. Suggest a one-line summary at the top.

Output format example: see ./examples/sample-notes.md.A simple SKILL.md. The description is what makes the model find it. The body is what makes the model follow it.

When skills are the right packaging

A workflow you want to share with teammates without making them remember a custom command
A procedure that has multiple steps and benefits from explicit instructions
A task that has a 'usually trips up the model' kind of nuance worth encoding
A workflow that uses a specific template, example, or sub-script
Knowledge that should travel with the project and version-control with it

Skills you should expect to use

Type	Example skills
Personal	Daily standup writeup, weekly review
Team / project	Release notes, deploy checklist, code review rubric
Plugin	Vercel deploy, security review, Anthropic SDK migration

The big idea: skills are how teams encode 'the way we do X' into something the model can find and follow. Spend on the description; reuse the result.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-claude-code-skills-creators

What is the core idea behind "Skills: Bundled Procedural Knowledge"?
1. Skills are reusable bundles of instructions plus optional scripts and assets. They're how Claude Code learns a procedure once and reapplies it everywhere.
2. boundary
3. A list of files it intends to read
4. A web search / browse server — for retrieval the agent can drive itself
Which term best describes a foundational idea in "Skills: Bundled Procedural Knowledge"?
1. procedural knowledge
2. skill
3. trigger description
4. skill bundle
A learner studying Skills: Bundled Procedural Knowledge would need to understand which concept?
1. skill
2. trigger description
3. procedural knowledge
4. skill bundle
Which of these is directly relevant to Skills: Bundled Procedural Knowledge?
1. skill
2. procedural knowledge
3. skill bundle
4. trigger description
Which of the following is a key point about Skills: Bundled Procedural Knowledge?
1. User-scoped: in `~/.claude/skills/<skill-name>/` — available across all projects
2. Project-scoped: in `.claude/skills/<skill-name>/` inside a repo — versioned and shared with the team
3. Plugin-scoped: shipped by official or third-party plugins, prefixed with the plugin name
4. Discoverable: the SKILL.md frontmatter description is what triggers the skill
Which of these does NOT belong in a discussion of Skills: Bundled Procedural Knowledge?
1. Plugin-scoped: shipped by official or third-party plugins, prefixed with the plugin name
2. Project-scoped: in `.claude/skills/<skill-name>/` inside a repo — versioned and shared with the team
3. boundary
4. User-scoped: in `~/.claude/skills/<skill-name>/` — available across all projects
Which statement is accurate regarding Skills: Bundled Procedural Knowledge?
1. A procedure that has multiple steps and benefits from explicit instructions
2. A task that has a 'usually trips up the model' kind of nuance worth encoding
3. A workflow you want to share with teammates without making them remember a custom command
4. A workflow that uses a specific template, example, or sub-script
Which of these does NOT belong in a discussion of Skills: Bundled Procedural Knowledge?
1. A task that has a 'usually trips up the model' kind of nuance worth encoding
2. A procedure that has multiple steps and benefits from explicit instructions
3. A workflow you want to share with teammates without making them remember a custom command
4. boundary
What is the key insight about "Skill vs slash command vs MCP" in the context of Skills: Bundled Procedural Knowledge?
1. Slash commands are user-typed shortcuts. Skills are model-discovered procedures (the model picks one when the request ma…
2. boundary
3. A list of files it intends to read
4. A web search / browse server — for retrieval the agent can drive itself
What is the key insight about "Skill descriptions are the whole game" in the context of Skills: Bundled Procedural Knowledge?
1. boundary
2. If the description doesn't match the user's natural phrasing, the skill never triggers.
3. A list of files it intends to read
4. A web search / browse server — for retrieval the agent can drive itself
What is the key insight about "From the community" in the context of Skills: Bundled Procedural Knowledge?
1. boundary
2. A list of files it intends to read
3. On r/ClaudeAI, a frequent gotcha is that SKILL.md descriptions need to use the words real users actually type — if the u…
4. A web search / browse server — for retrieval the agent can drive itself
Which statement accurately describes an aspect of Skills: Bundled Procedural Knowledge?
1. boundary
2. A list of files it intends to read
3. A web search / browse server — for retrieval the agent can drive itself
4. A skill is a folder with a SKILL.md (the instructions), optional scripts (helpers the model can call), and optional assets (templates, examp…
What does working with Skills: Bundled Procedural Knowledge typically involve?
1. The big idea: skills are how teams encode 'the way we do X' into something the model can find and follow.
2. boundary
3. A list of files it intends to read
4. A web search / browse server — for retrieval the agent can drive itself
Which best describes the scope of "Skills: Bundled Procedural Knowledge"?
1. It is unrelated to tools workflows
2. It focuses on Skills are reusable bundles of instructions plus optional scripts and assets. They're how Claude Cod
3. It applies only to the opposite beginner tier
4. It was deprecated in 2024 and no longer relevant
Which section heading best belongs in a lesson about Skills: Bundled Procedural Knowledge?
1. boundary
2. A list of files it intends to read
3. Where skills live
4. A web search / browse server — for retrieval the agent can drive itself

← Back to interactive lesson

Tendril · Creators · Tools Literacy