winget install --id=moatazhamada.omni-skills -e Omni Skills unifies scattered AI skills across all your tools. One canonical store, zero drift. Compile skills for Claude, Cursor, Kimi, Codex, Gemini, OpenCode, KiloCode, and more.
> I try every AI tool. My skills scattered everywhere. This unifies them.
> 🎉 v1.5.0 is out — automatic pre-sync backups, session-aware consent, a smaller core CLI (sync, setup, doctor, restore, update, help), and secondary commands moved under manage. Read the changelog →
A CLI + MCP server that takes the skills you've collected across all your AI coding tools and unifies them into a single canonical store. Then it syncs them into every tool you use — Claude, Codex, Kimi, Gemini, Cursor, Zed, Cline, Z.AI, and anything else that follows.
If you find this useful, please consider
starring the repo — it helps
us reach the criteria for inclusion in homebrew/core so users can run
brew install omni-skills without the brew tap step.
Every new AI coding tool wants its own instruction file, skill directory, and configuration. The result is fragmentation:
| Mess | What I Found |
|---|---|
| Duplicate AGENTS.md files | 70 copies of the same template across 16 projects |
| Orphaned skills | 15 skills hidden in a tool's skills directory, invisible to other tools |
| Marketplace dumps | 203 generic skills cloned into a project |
| Stale templates | Old project-only rules in every repo |
| Private skills leaking |
| Project-specific skills mixed with generic skills |
| Iron laws drifting | A 98KB instruction file manually copy-pasted between repos |
| New tool = manual setup | Every new AI tool meant copying config files one by one |
Omni Skills is a single-purpose tool: find all your skills, put them in one place, and wire them into every AI tool you use.
# One canonical store. Every tool sees it.
omni-skills sync all # Claude, Codex, Kimi, Gemini, Cursor, Cline, Zed, etc.
Choose one of the following. Native binaries do not require Node.js.
# macOS / Linux
brew tap moatazhamada/tap
brew install omni-skills
# Windows
winget install omni-skills
# npm
npm install -g ai-omni-skills
See docs/install.md for details on why brew tap is needed
and how each distribution channel works.
You need your own private repository for your skills. This toolkit does not include skills — it connects the skills you already have to every AI tool you use.
# 1. Run the auto-scan setup
omni-skills setup
# Auto-detects your installed AI tools, finds your skill directories,
# suggests cleanup, and generates ~/.config/skills/config.json
# 2. Sync to every AI tool
omni-skills sync all
# 3. Verify health
omni-skills doctor
# 4. Run the verification suite
node verify.js
Override defaults without questions:
omni-skills setup --public=~/my-skills-public --private=~/my-skills-private
omni-skills setup --toolkit=/path/to/this/repo
| Tier | What | Mechanism |
|---|---|---|
| A | SKILL.md skills + shared instructions + MCP server | Symlinks + local MCP server exposing list_skills / read_skill |
| B | Hooks | Canonical hooks transpiled into each tool's native hook format |
| C | Other assets | Symlinks from your config repo to per-tool paths |
When you run omni-skills sync, each SKILL.md is compiled on the fly into the
format each target tool expects. You can also add executionBoundary guards in
the YAML frontmatter to restrict file writing, network access, or require shell
execution confirmations per tool.
See docs/architecture.md for the full compiler pipeline, execution boundaries, and MCP server details.
| Tool | Type | Config | Skills Dir | MCP |
|---|---|---|---|---|
| Claude Code | CLI | ~/.claude/CLAUDE.md | ✓ | ✓ |
| OpenAI Codex | CLI | ~/.codex/AGENTS.md | ✓ | ✓ |
| Kimi | CLI | ~/.kimi/AGENTS.md | ✓ | ✓ |
| Gemini CLI | CLI | ~/.gemini/GEMINI.md | — | ✓ |
| Cursor | Editor | ~/.cursor/rules/ | — | ✓ |
| Kilocode | VS Code | ~/.kilocode/rules/ | ✓ | ✓ |
| OpenCode | CLI | ~/.config/opencode/ | — | ✓ |
| Aider | CLI | ~/.aider.conf.yml | — | — |
| Continue.dev | VS Code | ~/.continue/config.yaml | — | ✓ |
| Cline | VS Code | ~/.cline/rules.md | ✓ | ✓ |
| Roo Code | VS Code | ~/.roo/rules.md | ✓ | ✓ |
| Windsurf | Editor | ~/.windsurf/rules.md | — | ✓ |
| Zed | Editor | ~/.config/zed/settings.json | — | ✓ |
| Tabby | Self-hosted | ~/.tabby/config.toml | — | — |
| PearAI | Editor | ~/.pearai/config.json | — | — |
| Void | Editor | ~/.void/config.json | — | — |
| JetBrains Junie | IDE | .junie/guidelines.md | — | — |
| JetBrains AI Assistant | IDE | .aiassistant/rules/ | — | — |
| Claude Desktop | Desktop | ~/Library/…/Claude/… | — | ✓ |
| Devin | Desktop | — | — | — |
| Factory Droid | CLI | — | — | — |
| Z.AI (GLM 5.2) | Model API | — | — | —¹ |
¹ Z.AI works through existing tools. Point Claude Code, Cline, or Zed at the
GLM Coding Plan endpoint. For VS Code Copilot, install the glm-copilot
extension.
Core commands are the ones you run every day. Secondary commands are grouped
under manage to keep the main surface small.
| Command | Does |
|---|---|
omni-skills sync [tool|all] [--dry-run] [--no-backup] | Wire instructions, skills dirs, MCP config, hooks, assets. |
omni-skills setup | Auto-scan, detect tools, generate config. |
omni-skills doctor | Health check symlinks, config, indexes, skill counts. |
omni-skills restore [index] [--prune[=N]] [--empty-trash] | List or restore trashed files, prune old trash. |
omni-skills update [--check] | Check for updates. |
omni-skills help | Show help. |
omni-skills manage )| Subcommand | Does |
|---|---|
manage mcp | Run the MCP server over stdio. |
manage index | Regenerate INDEX.md and managed SHARED.md. |
manage workflow [list|run ] | List or run chainable skill workflows. |
manage check [--move] [--dry-run] | Find orphaned skills and dangling symlinks. |
manage classify [path] [--depth=N] [--dry-run] | Scan and sort instruction files public/private. |
manage discover | Scan system for AI tools, instruction files, skill dirs. |
manage report [--enhance] | Usage statistics and improvement tips. |
manage init [--dry-run] | Interactive setup: scan, classify, route, wire. |
manage security [scan] | SkillSpector vulnerability scanning. |
manage create [name] | Create a new skill with a wizard. |
manage create from | Convert an existing file into a skill. |
manage uninstall | Remove omni-skills wiring. |
Legacy top-level commands (e.g., omni-skills check) still work for backward
compatibility, but new scripts should prefer omni-skills manage check.
See docs/usage.md for detailed usage, real stats, health checks, verification, and tests.
The original CLI had ~15 top-level commands. That made the tool look heavier
than it is and increased the chance of running the wrong thing. The refactor
keeps the daily surface tiny (sync, setup, doctor, restore) and moves
everything else behind manage. The goal is less friction, not more
features.
omni-skills sync can rewrite instruction files, MCP configs, hooks, and skill
directories. Before it writes anything, it copies the current versions to:
~/.config/skills/backups//
If a sync ever breaks a tool config, you can restore manually from that
directory. Backups are skipped with --dry-run (nothing is changed) or
--no-backup (you know what you're doing). Old backups are pruned after 30
days automatically.
Several commands (sync, setup, check, classify, init) default to a
dry-run preview before they write anything. If you run several of them in a row,
re-confirming every time is tedious; --yes is risky because it persists for
only that single invocation. Use the environment variable instead:
export OMNI_SKILLS_SESSION_YES=1
omni-skills setup
omni-skills sync all
omni-skills doctor
This skips confirmations for the current shell session only. When the shell closes, the override disappears.
Omni Skills keeps your skills in one place; it does not tell you which AI agent
to use for a given task. For that, see
ai-tool-router — a separate,
zero-dependency skill that scans your installed agents, remembers their costs
and strengths, and suggests the cheapest capable tool (plus a fallback).
MIT — see LICENSE.