Skills, tools and knowledge bases are what make Claude Desktop productive in the first place. Used well they save time; used badly they turn into the next flood of plugins. Here I sort out the terms and show how a shared skill library stays clean in a team.
Skills, extensions, tools, which is which?
Skill: instructions for a recurring task. A skill bundles the description, the prompts and the examples for one clearly scoped task. Claude picks it as soon as the task matches the description.
Tool: a concrete function Claude is allowed to call. Tools usually reach the app through MCP servers. A tool sends an email, reads a file or creates an appointment, one atomic command with an input and an output.
Extension: a bundle of skills, tools and configuration. An extension packages a set that belongs together, for research or code review, say. You install it once and get a consistent experience.
Knowledge base: a structured store of knowledge. A knowledge base supplies Claude with long-lived context, product documentation, brand rules or frequent answers. It complements skills, it does not replace them.
How I write skills that survive daily use
A clear task description. The front matter states when the skill applies. If the description is vague, Claude will either pick it too rarely or too often.
Two or three examples. Concrete before-and-after examples beat abstract rules. In daily use, a skill without examples feels like a template nobody opens.
The expected output format. Markdown, a 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 is how you avoid hallucinations at the edges 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. One shared repository instead of separate copies on every machine. Changes are traceable and a rollback is possible.
- Stick to a naming convention. A format such as role.purpose.verb. Everyone finds skills that way, and Claude picks them more reliably.
- Run a proper review. Before rollout, every new skill goes through a short review. Content, examples and permissions all get checked.
- Clean up every quarter. Skills nobody uses get removed. A short usage count from the log file is enough of a basis.
- Document the security clearances. Which data may the skill touch and which may it not. That one list replaces ten discussions in an audit.
When a knowledge base really pays off
Recurring questions. If the same explanation turns up in five threads a week, a knowledge base saves more time than it costs to build.
A stable source. Product documentation, brand rules or contracts are ideal. Content that goes out of date quickly belongs in a live source via MCP instead.
Clear ownership. One person keeps the knowledge base current. Without an owner, any store of knowledge goes stale in under six months.
This post is part of the series Setting up Claude Desktop.
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.