Skills, tools and knowledge bases are what make Claude Desktop productive. Used well they save time; used badly you get the next plugin glut. Here I sort out the terms and show how a skill library stays clean in a team.
Skills, extensions, tools – what is what?
Skill: an instruction for a recurring task. A skill bundles a description, prompts and examples for a clearly defined task. Claude selects it as soon as the task matches the description.
Tool: a concrete function Claude may call. Tools usually arrive in the app via MCP servers. A tool sends an email, reads a file or creates an appointment – an atomic command with input and output.
Extension: a bundle of skills, tools and configuration. An extension packages a coherent set, for example for research or code review. You install it once and get a consistent experience.
Knowledge base: a structured knowledge store. A knowledge base supplies Claude with long-lived context – product docs, brand ground rules or common answers. It complements skills, it does not replace them.
How I write skills that hold up day to day
A clear task description. The front matter states when the skill applies. If the description is vague, Claude picks it either too rarely or too often.
Two or three examples. Concrete before-and-after examples beat abstract rules. A skill without examples feels like an unused template in practice.
The expected result format. Markdown, table, JSON or free text – define the result and you get reliable output.
Clean boundaries. A skill should describe what it does not do. That avoids hallucinations at the edge of the task.
How to avoid the plugin graveyard
I introduce five ground rules as soon as more than three people are involved.
- Version your skills. A shared repository instead of individual copies on every machine. Changes are traceable, rollback is possible.
- Keep a naming convention. A format such as role.purpose.verb. Everyone finds skills, and Claude selects them more reliably.
- Run a review process. Before rollout, every new skill goes through a short review. Content, examples and permissions are checked.
- Clean up quarterly. Skills nobody uses get removed. A short usage stat from the log file is enough as a basis.
- Document security clearances. Which data the skill may touch, and which not. This list replaces ten discussions in an audit.
When a knowledge base really pays off
Recurring questions. If the same explanation shows up in five threads a week, a knowledge base saves more time than it costs to build.
A stable source. Product docs, brand ground rules or contracts are ideal. Fast-changing content belongs in a live source via MCP instead.
Clear ownership. One person keeps the knowledge base current. Without an owner, every knowledge store goes stale in under six months.
Frequently asked questions
What is the difference between skills and MCP servers?
Skills bundle knowledge, prompts and examples for a recurring task. MCP servers provide functions or data. Skills use MCP but are not servers themselves. Simplified: MCP is the socket, a skill is the tool plugged into it.
Where do I store my own skill?
In the app’s configuration path under the skills directory. Each skill is a folder with a description in the file skill.md and optionally further files such as templates or example prompts.
Do skills work without a Pro or Team plan?
Yes. Skills are a client-side feature of the app and are available on all plans. For shared skill libraries in a team, though, at least the Team plan is advisable because you need central management.
How many skills make sense?
Less is more. Three to seven well-described skills per role are enough in practice. A sprawling library makes Claude pick the wrong skills – that costs time and trust.
Can we share skills across a team?
Yes, via a shared repository. The skill folders are versioned, the configuration path symbolically linked. Everyone sees the same tools and updates roll out in a controlled way.
This article is part of the series Set up Claude Desktop.