A skills manager for Claude Code: find, fix and use your skills in one place

The problem

Claude Code looks for skills in several places: ~/.claude/skills, each repository's .claude/skills (and nested ones in a monorepo), installed plugins, and skills synced from your claude.ai account. After a few months there are dozens, and the questions are hard to answer from Claude itself:

• Which skills does Claude load in this repository, and which only elsewhere?
• Which of them do my chats actually use, and which just take up room in every chat's skill list?
• Are my personal copy and the repository's copy of the same skill still the same?
• What was that skill called, and does it fit what I'm doing right now?

How Pairbar solves it

1. Open the Skills tab
   Every skill Claude can load is listed under its source group (Personal, Projects or Plugins), with a description preview and app marks showing which app can use it. On a narrow sidebar, names wrap and the marks sit below the text; open the row for the full description and actions. The list updates by itself when a skills folder changes.
2. Filter, search and sort
   Type to search by name, description or how you call it (/review-method). Filter chips narrow it to Personal, Project or Plugin, or to one repository (only what Claude loads there); sort by Name, Recently changed, Most used or Issues first.
3. Use the suggestions for the chat you're in
   When Claude shows a chat, Suggested here at the top lists the skills that fit it: the project's own first, then those its workflows and agents use, then those whose name shares a word with the chat's title or branch. It's plain word matching on your Mac, sent nowhere.
4. Use a skill in chat
   Use in chat types /review-method into Claude's message box and leaves the cursor after it, without sending, so you add what you want it to do. You can also drag any skill onto the message box.
5. Fix copies that drifted apart
   When the same skill has copies that differ, a card such as "paseo has 3 copies, 2 versions" recommends which to keep (a pinned version, then a copy a tool manages, then the newest). Its button opens a plan; nothing changes until you Approve, the others are backed up first, and Undo puts everything back. See fixing skill drift.

Where Claude Code's skills come from

A skill's page

• How you call it, its description, allowed tools and model.
• Who can use it: whether Claude loads it everywhere or only in some projects, and why not ("Its plugin is turned off").
• Where it's installed: every copy, with its folder, the start of its hash and tags such as differs, linked or managed by ….
• Used by: how often your chats used it in the last 30 days, and the workflow steps and agents that use it. A skill nobody uses still costs room in every chat's skill list, and the page says about how many tokens.
• Problems with the file: no frontmatter, a name that isn't lowercase with hyphens, an over-long description.

Where else your skills show up

• The focused chat's context card lists the skills that fit here, with Insert into a new message. See the focused chat's context.
• New chats: Skills in the composer's options, so the first message asks for the skill by name.
• Workflows: a Skill chip on every step, and the workflow planner may pick one that clearly fits.
• Agents: an agent can list skills it always uses.

Without Pairbar

Without Pairbar, managing Claude Code skills is done with the file system and Claude itself:

• Ask Claude which skills it has: it can list what it loaded in the current folder, one project at a time.
• Browse the folders (~/.claude/skills, each repo's .claude/skills, the plugins folder) in Finder or a terminal.
• diff -r two copies of a skill to see whether they drifted, and copy files over by hand.
• /plugin in Claude Code to see and toggle installed plugins.