Teach AI how you work.
Modular knowledge that compounds over time.
Claude can write code, review contracts, and build applications. But it doesn't know:
Every time you start a new conversation, you lose all that context. You re-explain the same processes. You correct the same mistakes. Over and over.
Skills close that gap — permanently.
A skill is a modular, self-contained package of knowledge and workflows. Think of it as an onboarding guide — it transforms Claude from a generalist into a specialist for your domain.
A skill describes how things work — your processes, schemas, conventions, and rules. It doesn't execute workflows; it provides the expertise to do them right.
AI only loads what it needs. The skill description is always visible. The body loads on trigger. References load on demand. No context waste.
Put a skill in a plugin marketplace and everyone on your team gets the same consistent knowledge base. One source of truth.
Start rough, iterate based on feedback. The best skills aren't written in one go — they're refined through real usage and real corrections.
Optional: scripts/ for executable code, assets/ for templates and images.
The core file. Contains the name and description in YAML frontmatter (determines when AI triggers the skill), plus a compact body with essential knowledge.
Detailed docs that AI reads only when needed. Process guides, schemas, examples, field requirements. This is where depth lives — without polluting the context window.
The model always knows the skill exists. It reads only what it needs. A massive, complex knowledge base feels lightweight because only relevant parts enter the context window.
Knowledge. Describes how things work, what fields exist, how processes are structured. Matter-of-fact documentation.
Action. A workflow prompt that guides the user through a process. Asks questions, calls tools, produces output.
/slash)Rule of thumb: If you update the skill, commands don't need to change — they point to the same source of truth.
Skills don't live alone. A plugin bundles related skills, commands, agents, and MCP servers into one installable package.
Org-wide catalog
Themed bundle
Knowledge
Workflows
Tool access
Sales Plugin
Fireflies MCP + meeting prep skill + proposal command
Developer Plugin
Code review agent + tool design skill + cleanup command
Hackathon Plugin
Recap skill + prep skill + communication commands
Install a plugin → get skills, commands, and MCPs in one click. No setup.
What does the user actually need? Which processes are repeated? What context gets lost between sessions?
Which parts need scripts? Which need reference docs? What's core enough for SKILL.md vs a reference file?
Strong trigger description. Compact body in imperative form. Point to references. Stay under 2000 words.
The best skills come from iterating on real feedback — not from writing the perfect document upfront.
Use the /skill-creator skill to generate a first draft from a conversation. It structures your existing knowledge into the right format — then you iterate.
The description field in frontmatter determines when AI triggers your skill. Vague descriptions mean your skill never gets used.
BAD — won't trigger
GOOD — triggers reliably
When someone types /new-build, here's what happens:
The /new-build command prompt loads and starts the workflow.
Command references the ClickUp Delivery skill → AI reads which fields are required, what statuses exist, how builds are structured.
With the right knowledge, AI calls the ClickUp MCP to actually create the build with correct fields.
When the process changes, only the skill gets updated. All commands still work — they reference the same source.
If you have 5 different commands that need to know how builds work, they all point to one skill. Update once, everything stays consistent.
Each skill has a domain owner:
Nobody blindly edits someone else's skill. Feedback goes to the owner.
1500–2000 words max. Move detailed process docs, schemas, and examples to references/. The body is for essential knowledge only.
When a skill gets too large, break it into multiple focused skills within the same plugin. Finance has audit + close management as separate skills.
External skills from community sources can contain hidden instructions. Always review imported skills before trusting them with sensitive workflows.
Unlike skills, commands are never auto-discovered. They only activate on explicit /slash invocation. Perfect for setup flows and onboarding.
If the same knowledge appears in multiple skills, extract it into one skill and have others reference it. Avoid duplication across your plugin.
Build a feedback loop — a simple MCP or ClickUp integration where users can report what went wrong. Rich feedback makes skills better fast.
Pick one process
you keep re-explaining
Use the skill creator
to draft a SKILL.md
Test, iterate,
share with your team
Every skill you build is knowledge your team never has to re-explain. The investment compounds.