Omni Skills

I try every AI tool. My skills scattered everywhere. This unifies them.

🎉 v1.4.0 is out — native binaries for macOS, Linux, and Windows; Homebrew and Winget support; and a skill compiler pipeline. Read the announcement →

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.

The Problem This Solves

Every new AI coding tool wants its own instruction file, skill directory, and configuration. The result is fragmentation:

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.

Install

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.

Quick Start

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

What It Does

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.

Supported AI Tools

¹ 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.

CLI Commands

Core commands are the ones you run every day. Secondary commands are grouped under manage to keep the main surface small.

Core commands

Secondary commands (omni-skills manage <subcommand>)

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.

Why These CLI Changes?

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.

Automatic Pre-Sync Backup

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/<ISO-timestamp>/

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.

Session-Aware Consent

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.

Picking the Right AI Tool for the Task

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).

Documentation

• Installation options & why brew tap
• Architecture: compiler, execution boundaries, MCP server
• Workflows: chainable skill sequences
• Security scanning with NVIDIA SkillSpector
• Creating new skills
• How to store your skills
• Usage guide, health checks, verification

License

MIT — see LICENSE.