Package your methods, standards, and tools into folders that agents can load on demand. Skills turn general assistants into reliable specialists without repeated prompting.
Skills let you package the way you work once. When a task matches a skill name or description, the agent loads that folder automatically and applies your standards up front.
Reusable instructions, tools, and references that load automatically when a task matches.
Long-running workspaces where knowledge builds over time for a specific effort.
Stable rules about how the model should behave everywhere, all the time.
Best when you are trying something new and do not need repeatable structure yet.
At its simplest, a skill is a directory with a single SKILL.md file. The metadata loads at startup, and the body routes the agent to deeper knowledge only when needed.
The agent pre-loads the name and description from SKILL.md. When the skill is relevant, it reads the full file. That is your chance to set principles, routing, and required tags.
--- name: pdf-forms description: Extracts and fills PDF forms. Use when working with PDFs or form fields. --- <objective>...</objective> <quick_start>...</quick_start> <success_criteria>...</success_criteria>
Keep SKILL.md lean and route deeper details to other files for progressive disclosure.
Use workflows for step-by-step tasks. The router in SKILL.md points here, so the agent follows a clear sequence without guessing.
<process> 1. Identify the gap 2. Draft the skill 3. Test on real tasks 4. Iterate based on failures </process>
Store domain knowledge, patterns, and examples here. The agent reads these only when relevant, which keeps the context window efficient.
<common_patterns> Provide examples when format matters. Use consistent terminology. Keep instructions direct. </common_patterns>
Templates define the output structure the agent should copy and fill. They are perfect for reports, specs, and repeatable formats.
# Report Title ## Executive summary ## Key findings ## Recommendations
Scripts give agents deterministic power. The code runs without entering the context window, so results are fast and repeatable.
python scripts/analyze_form.py input.pdf python scripts/fill_form.py input.pdf fields.json output.pdf
Skills scale because the agent only reads the files required for the current task. The rest stays out of the context window until it is useful.
At startup, the agent only knows the name and description of each skill. This metadata is enough to decide if a skill should be loaded.
When a task matches, the agent reads SKILL.md. This file defines essential principles and routes to deeper content.
References load only when needed. The agent pulls patterns, examples, and domain knowledge without stuffing everything into context.
Scripts run outside the context window. The agent executes deterministic tools without reading the code itself.
"Building a skill is like onboarding a new hire."
You capture the steps, standards, and examples that make your work repeatable. That is how knowledge travels through teams and across time.
Claude already understands PDFs, but cannot manipulate them directly. A skill adds scripts so the agent can analyze and fill forms without loading the code into context.
Deterministic tools beat token guessing. The agent can run a script, get a clean result, and move on with confidence.
User asks to fill a PDF form. The agent loads SKILL.md.
Pull instructions for field mapping and validation.
Extract fields and coordinates without manual inspection.
Populate fields and verify output before delivery.
python scripts/analyze_form.py contract.pdf > fields.json python scripts/fill_form.py contract.pdf fields.json signed.pdf
Start with a focused use case. The mini builder below generates a SKILL.md stub and a folder map you can refine into a working skill.
Equipping agents for the real world with Agent Skills. A practical blueprint for why skills work and how they scale.
Open articleHow skills fit with projects, custom instructions, and everyday prompting.
Read the guidePractical templates, XML tag guidance, and testing workflows.
Open the repoOnly install skills you have audited or that come from trusted sources. Skills can include executable scripts and external calls.