Skill Bridge

Sync Agent Skills across Claude Code, Codex, Cursor, Warp, and other tools that adopt the Agent Skills open standard.

Heads up — look at skillshare first.

During the product exploration for Skill Bridge we discovered that skillshare already covers a large part of what this repository set out to do: discovery and consolidation of skills across Claude Code, Codex, Cursor, and 50+ other Agent Skills–compatible tools, with safety primitives like backup, an operation log, built-in security audit, and symlink-based sync. It is MIT-licensed, actively maintained, distributed via Homebrew, and written as a single Go binary.

Before building on top of Skill Bridge, consider using or contributing to skillshare instead. The docs in this repository may still be useful as product thinking, but the working tool lives there.

Status

Paused. This repository is retained as product-thinking only — vision, PRD, UX direction, and implementation specs for what Skill Bridge was going to be. No active development is planned.

During product exploration we found that runkids/skillshare already covers the intended scope with more maturity than a fresh implementation could reach quickly. The documentation here is preserved because it maps reasonably directly onto an open skillshare feature request — see docs/skillshare-issue-135-contribution.md for how to turn this thinking into a contribution.

Why This Exists

Agent Skills are portable, but the user experience around them is still fragmented:

• Claude Code uses ~/.claude/skills/ and plugin-bundled skills
• Codex and other tools increasingly support the shared ~/.agents/skills/ convention
• Cursor uses ~/.cursor/skills/
• Warp supports multiple directories and recommends ~/.agents/skills/

That leaves users with the same skill installed in multiple places, plugin-managed skills that are hard to reuse elsewhere, and no simple way to answer basic questions like:

• What skills do I already have?
• Which ones are available in Claude but not in Codex?
• Which ones are shared already?
• Which ones are vendor-managed and should be treated as read-only?

Skill Bridge aims to solve that with a safe, user-level sync tool.

Product Direction

Core docs

• docs/vision.md - long-term product vision and strategic direction
• docs/prd-v1.md - v1 product requirements document
• docs/product-brief.md - concise product summary
• docs/user-experience.md - terminal UX direction
• docs/architecture.md - implementation architecture
• docs/roadmap.md - milestone plan
• docs/tasks.md - active task list

Principles

• Non-destructive by default
• Clear before clever
• Cross-agent first
• Respect vendor-managed directories
• Treat ~/.agents/skills/ as the canonical shared layer

Planned Core Commands

skill-bridge scan
skill-bridge status
skill-bridge sync --interactive
skill-bridge doctor
skill-bridge prune

Repository Layout

skill-bridge/
├── README.md
├── AGENTS.md
├── CLAUDE.md
├── Makefile
├── pyproject.toml
├── docs/
│   ├── product-brief.md
│   ├── prd-v1.md
│   ├── vision.md
│   ├── user-experience.md
│   ├── architecture.md
│   ├── roadmap.md
│   └── tasks.md
├── specs/
│   ├── 001-discovery-catalog.md
│   ├── 002-sync-planning.md
│   ├── 003-interactive-cli.md
│   └── 004-manifest-and-undo.md
└── src/
    └── skill_bridge/
        ├── __init__.py
        └── cli.py

Local Development

Show available make targets

make help

Install the package in a local virtualenv

make install-dev

Run the CLI help

make run-help

Install a user-level command

make install

This currently installs the package with pip --user, which is a pragmatic local starting point. Before a public release, we may prefer a pipx-based install story.

Open Source Plan

The intent is to make this repository public once the initial product is solid. Before that happens, we should still decide:

• license
• support policy
• minimum supported platforms
• how aggressively we want to support vendor-specific edge cases

For now, assume the public release target is:

• Python 3.11+
• macOS first
• graceful handling of missing tools and unsupported directories

Current Recommendation The Tool Will Encode

• Shared skills live in ~/.agents/skills/
• Claude personal skills remain in ~/.claude/skills/
• Cursor personal skills remain in ~/.cursor/skills/
• Codex personal skills remain in ~/.codex/skills/ where needed for compatibility
• Warp personal skills remain in ~/.warp/skills/ where needed for compatibility
• Claude plugin skills are discovered through the installed plugin registry, but never modified in-place

Near-Term Milestones

1. Build discovery across Claude, Codex, Cursor, Warp, and shared ~/.agents/skills/
2. Normalize results into a single catalog with conflict detection
3. Add interactive selection and sync planning
4. Add manifest tracking, undo, and prune support
5. Ship a stable install story for public use