See and manage every Claude Code and Codex skill across all your projects

The problem

A skill is a folder with a SKILL.md that teaches Claude or Codex how to do something: your review method, a release checklist, how to use a tool. They pile up fast, and they live in many places: ~/.claude/skills, each repo's .claude/skills, nested folders in a monorepo, installed plugins, skills synced from your claude.ai account, and Codex's own folders.

• Neither app shows you the full list, or which skills load in which project.
• Neither app shows you the other's skills, so you can't tell which ones only Claude can use.
• Copies of the same skill drift apart, and a duplicated name can stop Codex resolving $name at all.

How Pairbar solves it

1. Open the Skills tab
   Every skill Claude and Codex can load is there. The list updates by itself when a skills folder changes, and again whenever you open the tab.
2. Read it by where the skills come from
   The list is grouped: This project first (the skills of the repo the chat you're in works in), then Personal, then other projects and Plugins, folded until you open them. Each row has two small app marks, full when Claude or Codex can use the skill and faint when it can't. A skill in only one app is fine: nothing nags you about it.
3. Search and filter
   Search by name, description or how you call it (/review-method, $paseo); every word must match. One Filter menu shows All, This project, Personal or Plugins, for both apps or only Claude's or Codex's, sorted by name, recently changed or most used.
4. Open a skill's page
   It shows how you call it in each app, whether it works in both, Who can use it (and why not, such as "Its plugin is turned off"), every copy with its hash, the workflows and agents that use it, its files and its rendered SKILL.md.
5. Let Pairbar keep them the same
   Turn on Keep skills the same in Claude and Codex and Pairbar mirrors your personal skills between the apps in the background. It never writes over a change you made in both: that's one small line, 1 skill changed in both apps · Review. A skill that's actually broken (no frontmatter, a link to nothing, a name Codex lists twice) gets one line too: N skills have problems · Review.

Where the skills come from

Pairbar learns which repos you work in from your chats. For plugins it reads only which are installed and on; nothing else in those settings files (such as your MCP servers' keys) is kept, shown or logged.

What a row's details offer

Problems (a file that can't be read, a link to nothing, a name clash) each say what's wrong and what to do; Fix the safe ones builds one plan of every low-risk fix there, each with a checkbox.

Using skills from the library

• Right-click a skill: Copy invocation, Use in a workflow, Reveal in Finder.
• The composer's Skill chip asks for the skill by name when the app can load it in that folder, or includes the skill's text when it can't.
• The focused chat's context card offers the skills that fit the chat's project and branch, best first.

Without Pairbar

Without Pairbar, you can list skills from the shell or ask the apps one project at a time:

• List the folders yourself: ls ~/.claude/skills ~/.agents/skills, plus each repo's .claude/skills and .agents/skills.
• Ask inside a session: Claude Code and Codex load skill names and descriptions for the folder you're in, so asking "which skills do you have?" answers for that project and that app only.
• Find stray copies with find ~ -name SKILL.md -not -path '*/node_modules/*' and compare them with diff -r.
• Keep one source in a git repo and symlink it into each app's folder by hand.