A library of skills can save a whole team time every week, but only if people can find the right skill, trust that it is current, and know what it is for. Without structure, a shared folder of skills turns into a junk drawer: five versions of the same workflow, no owner, and no one sure which one still works. This tutorial shows how to build a small skill library for a small business team. You will collect the skills you already have, sort them by job, give each one a standard home, and set up a simple routine for updates and retirement.
Prerequisites
- Claude access: Every team member who will use the library needs access to Claude, so they can actually run the skills you share.
- A shared home: One shared folder or version-controlled repository where the library lives, so there is a single source of truth.
- A named owner: One person responsible for the library, even if others contribute skills, so decisions about updates and retirement get made.
- Your existing skills: Any skills, prompts, or checklists the team already uses, gathered in one place before you start sorting.
Step 1: Collect what you already have
Ask each team member to send you every skill, reusable prompt, and workflow checklist they use regularly. Include the rough, half-finished ones. A skill that only one person uses is still a candidate for the library, because someone else may need the same workflow one day.
Put everything in a single inbox folder first, separate from the finished library. Do not sort yet; just gather.
Step 2: Sort by job, not by author
Create folders named for the job the skill does, not for the person who wrote it. Author-based folders break the moment someone changes roles, while job-based folders stay useful. A small business usually needs no more than six to eight groups. Useful starting groups are Marketing, Sales, Customer support, Operations, Finance, and Hiring, plus one group for company-wide skills such as brand voice or meeting notes.
Place each skill in exactly one group, the group where a new starter would look for it first. If a skill genuinely serves two groups, keep it in one group and note the other group in its description. Duplicating a skill across groups creates two versions that drift apart, and drift is how teams end up following outdated instructions.
Step 3: Give every skill a standard home
A skill in Claude is a folder containing a SKILL.md file, which holds the instructions Claude follows, plus any supporting files the skill needs.
Give every skill the same four pieces of information, and keep them in the same place for each skill:
- Name: Short, plain, and job-based, such as Weekly social captions or Supplier quote request.
- Description: One or two sentences saying what the skill does and when to use it, written for a new starter.
- Owner: The one person who answers questions about it and approves changes.
- Last reviewed date: The date someone last checked that it still works and still matches company practice.
Write the description as if the reader has never met the author. A description that says “Use this for the monthly thing” helps nobody. A description that says “Drafts the monthly supplier email from the price sheet” tells a new starter exactly when to reach for it.
Step 4: Version every change
Treat skills like company documents, not like chat messages. When a skill changes, note what changed, who changed it, and when, in a short changelog kept with the skill. A single line per change is enough.
Keep one current version of each skill in the library, and move older versions to an archive folder rather than deleting them outright. Old versions are occasionally needed to understand past work, but they must never sit beside the current version where a busy team member might pick the wrong one.
Step 5: Share it safely
Before a skill enters the shared library, check it for the leaks that cause real damage: passwords, API keys, private customer names, and internal URLs left in examples. Remove them and replace them with clearly marked placeholders. This check is worth doing even for skills written by careful colleagues, because secrets slip into examples easily and are easy to miss on a quick read.
Then tell the team the library exists, and show them how to find a skill by job in under a minute. A short walkthrough in a team meeting, plus a pinned link, is usually enough.
For the full sharing checklist, including permissions and secret review, see the guide on how to share skills across your team securely.
Step 6: Retire skills without breaking work
Set a quarterly review, and put it in the calendar now. At each review, the owner of each skill answers three questions: Is it still used, does it still work, and does it still match how the company works today? A skill that fails any of the three goes to the archive folder, with a short note saying why it was retired and what replaces it.
Retirement notes stop people quietly reviving an outdated skill, and tell anyone who wonders where a workflow went what replaced it. Archive first, and delete only after a full quarter with no one asking for it.
Tips for keeping the library useful
- Start small: Ten excellent skills beat fifty unreviewed ones.
- Name things plainly: If a new starter cannot guess what a skill does from its name and description, rewrite them.
- Reward contributions: Thank people who add skills and fix outdated ones, or contributions will quietly stop.
- Review on schedule: A quarterly review keeps the library trustworthy.
For cost context on the tools your skills rely on, see the AI Tools Pricing Index.
Frequently asked questions
Q: How many skills should a small business library hold? A: Start with the ten to twenty skills your team actually uses every week. Grow the library only when a repeated task has no skill yet.
Q: Who should own the library? A: One named person should own the library as a whole, while individual skills keep their own owners. The library owner runs the quarterly review and resolves duplicates. The skill owners keep their own skills current.
Q: Should skills live in a shared folder or in version control? A: Either works, provided there is exactly one home for the current version of each skill. A shared folder is simpler for non-technical teams. Version control adds a fuller change history and is the better choice if your team already uses it.
Q: What do we do when a skill stops working? A: Move it out of the current library into the archive the same day, with a note saying what broke. Fix it and return it, replace it, or leave it archived.



