How to Sync AI Skills Across Claude Code, OpenClaw, and Codex in 2 Minutes

You use Claude Code at work, Openclaw for side projects, and Codex for quick scripts.

You have 20+ skills. They need to exist in all three tools.

Here's how to set that up in under 2 minutes — and never manually copy a skill again.

The Problem

Every AI CLI stores skills in a different directory:

~/.claude/skills/          # Claude Code

~/.codex/skills/           # Codex CLI

~/.opencode/skills/        # OpenCode

When you install a skill, you pick which tools get it. When you edit a skill in one tool, the others don't know. When you remove a skill from one tool, you might break the others.

The root cause: there's no single source of truth. Skills are scattered.

The Fix: One Source, Symlinks Everywhere

skillshare keeps all your skills in one directory and creates symlinks to each AI CLI.

~/.config/skillshare/skills/     ← single source

  ├── code-review/

  ├── react-guidelines/

  └── _team-repo/

        ├── frontend/

        └── testing/



~/.claude/skills/code-review → symlink to source

~/.codex/skills/code-review  → symlink to source

Edit the source, every tool sees the change instantly.

Step-by-Step Setup

1. Install

# macOS / Linux

curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh



# Homebrew

brew install runkids/tap/skillshare



# Windows PowerShell

irm https://raw.githubusercontent.com/runkids/skillshare/main/install.ps1 | iex

2. Initialize

skillshare init

This does three things:

• Creates ~/.config/skillshare/skills/ (your source directory)


• Detects which AI CLIs you have installed


• Generates config.yaml with your targets

Output looks like:

✓ Created source directory

✓ Detected targets:

    claude  → ~/.claude

    codex   → ~/.codex/skills

✓ Config saved to ~/.config/skillshare/config.yaml

3. Import existing skills

Already have skills scattered across your AI CLIs? Collect them:

skillshare collect --all

This copies every skill from every detected target into the source directory. Duplicates are flagged so you can choose which to keep.

4. Sync

skillshare sync

Done. Every target now has symlinks pointing to your source directory.

Synced 3 targets:

  claude   → 15 linked, 0 skipped, 0 removed

  codex    → 15 linked, 0 skipped, 0 removed

From now on, this is the only command you need. Made changes to your skills? skillshare sync.

Day-to-Day Workflows

Install a skill from GitHub

skillshare install anthropics/skills/skills/pdf

skillshare sync

The skill is downloaded to your source directory, then synced to all targets.

Install a full team/org skill repo

skillshare install github.com/your-org/team-skills --track

skillshare sync

The --track flag preserves .git, so you can update later:

skillshare update _team-skills   # git pull

skillshare sync                  # push changes to all targets

Create a new skill

skillshare new my-custom-skill

Creates a SKILL.md template in your source directory. Edit it, sync, and every AI CLI has it.

Scan for security threats

Before syncing third-party skills to your AI agents, scan them:

skillshare audit

This checks every installed skill for prompt injection, data exfiltration, destructive commands, and other threats. Critical findings block installation by default — no malicious skill reaches your AI agent without you explicitly approving it.

Skills are also scanned automatically during skillshare install.

Pull back edits from a specific tool

You tweaked a skill in codex's UI. Pull the change back to source:

skillshare collect codex

skillshare sync             # propagate to other targets

Check status

skillshare status

Shows which targets are in sync, which have drifted, and which skills are unlinked.

Preview before syncing

skillshare diff

Shows exactly what sync will do — which symlinks will be created, updated, or removed.

Cross-Machine Sync

If your source directory is a git repo:

# Machine A

skillshare push



# Machine B

skillshare pull

skillshare sync

Or just version-control ~/.config/skillshare/ as part of your dotfiles.

Project-Scoped Skills

For skills that should live inside a specific repo:

cd your-project

skillshare init -p                              # Creates .skillshare/

skillshare install org/skills/skills/react -p   # Install to project

skillshare sync                                 # Sync to targets

Commit .skillshare/ to git. Teammates clone the repo and run skillshare sync — everyone gets the same skills, in every AI tool.

Web Dashboard

skillshare ui

Opens a web dashboard at http://localhost:19420 for visual skill management — browsing, installing, syncing, and searching skills without the terminal.

The Config File

Everything is controlled by ~/.config/skillshare/config.yaml:

source: /Users/you/.config/skillshare/skills

sync_mode: merge    # merge (per-skill symlinks) or symlink (whole directory)

targets:

  claude:

    path: /Users/you/.claude

  codex:

    path: /Users/you/.codex/skills

Want to add a new AI CLI? Add a target. Want to remove one? Delete the entry. Then sync.

Quick Reference

Migration from Other Tools

If you're already using npx skills or manual management:

skillshare init          # detect your AI CLIs

skillshare collect --all # import everything

skillshare sync          # symlink to all targets

Full migration guide: skillshare.runkids.cc/docs/guides/migration

Architectural comparison: skillshare.runkids.cc/docs/guides/comparison

skillshare is open source (MIT), written in Go, and supports 40+ AI CLI targets.

GitHub: github.com/runkids/skillshare

Docs: skillshare.runkids.cc

If you found this useful, a ⭐ on GitHub would help others find it too.