Which integrations are available for this server?

Provides a unified skill store and instruction synchronization for JetBrains Junie and JetBrains AI Assistant, enabling access to personal skill repositories and shared instruction files via symlinks and MCP. Provides a unified skill store and instruction synchronization for OpenAI Codex, enabling access to personal skill repositories and shared instruction files via MCP tools like list_skills and read_skill.

How do I use Omni Skills?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Omni Skills list all my skills" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Omni Skills

by moatazhamada

Overview Schema Related Servers Score Discussions

JavaScript

Local

Omni Skills

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

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, and anything else that follows.

The Problem This Solves

I am that person who installs every new AI coding tool the day it drops. Claude Code, Codex, Gemini CLI, Kimi, Cursor, Cline, Continue.dev, Zed — I have tried them all. And each one wanted its own instruction file, its own skill directory, its own configuration.

This is what my system looked like before:

Mess	What I Found
Duplicate AGENTS.md files	70 copies of the same 1,649-byte template across 16 projects
Orphaned skills	15 speckit skills hidden in a tool's skills directory — no other tool could see them
Marketplace dumps	203 generic skills cloned into a project from a public marketplace
Stale templates	Old project-only rules in every repo while my real rules were in a different file
Private skills leaking	Project-specific skills mixed with generic skills in the same repo
Iron laws drifting	A 98KB instruction file manually copy-pasted between two rewrite repos
New tool = manual setup	Every new AI tool meant manually copying config files, one by one

Every tool had a piece of my knowledge. No tool had the full picture. The more tools I tried, the more fragmented my setup became.

Related MCP server: Skillz

What This Toolkit Does

Omni Skills is a single-purpose tool: it finds all the skills and instruction files you've accumulated, puts them in one place, and wires them into every AI tool you use.

# One canonical store. Every tool sees it.
skills sync all   # Claude, Codex, Kimi, Gemini, Cursor, Cline, Zed, etc.

Three Portability Tiers

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

The MCP Server

Every AI tool that supports MCP registers this server and can call:

// list_skills — discover what's available
{
  "name": "list_skills",
  "result": [
    {"name": "clean-code", "description": "Pragmatic coding standards..."},
    {"name": "refine-requests", "description": "Refine a task by comparing acceptance criteria..."}
  ]
}

// read_skill — load the full instructions before acting
{
  "name": "read_skill",
  "arguments": {"name": "systematic-debugging"},
  "result": "# Systematic Debugging\n\nNO FIXES WITHOUT ROOT CAUSE..."
}

Skills are discovered from your private skill repos, live-reloaded when files change, and exposed as both tools and prompts.

Quick Start

Prerequisites

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. Clone this toolkit (the code, not the skills)
git clone https://github.com/YOURUSER/ai-omni-skills.git
cd ai-omni-skills
npm link

# 2. Run the auto-scan setup
skills setup
# Auto-detects your installed AI tools, finds your skill directories,
# suggests cleanup, and generates ~/.config/skills/config.json

# 3. Sync to every AI tool
skills sync all

# 4. Verify health
skills doctor

# 5. Run the verification suite
node verify.js

Setup Flags

# Override defaults without questions
skills setup --public=~/my-skills-public --private=~/my-skills-private
skills setup --toolkit=/path/to/this/repo

25 Supported AI Tools

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	—	—	—

Tools with MCP support get the skills MCP server registered automatically. Tools with skills directories get symlinks to all your canonical skills.

The `skills` CLI

Command	Does
`skills mcp`	Run the MCP server over stdio (what each tool launches).
`skills index`	Regenerate `INDEX.md` files and the managed `SHARED.md` skill block.
`skills sync [tool\|all] [--dry-run]`	Wire instructions, skills dirs, MCP config, hooks, and assets.
`skills check [--move] [--dry-run]`	Find orphaned skills and dangling/foreign symlinks.
`skills classify [path] [--depth=N] [--dry-run]`	Scan for instruction files, detect sensitive content, sort public/private.
`skills discover`	Scan your entire system for AI tools, instruction files, skill directories, and projects.
`skills setup`	Auto-scan system, detect tools, suggest cleanup, generate config.
`skills doctor`	Health check: verify symlinks, config, indexes, and skill counts.
`skills report [--enhance]`	Usage statistics and heuristic improvement tips.
`skills init [--dry-run]`	Interactive setup: scan, classify, route, wire.
`skills help`	Show help.

How to Store Your Skills

This toolkit is code only. Your skills live in a separate repository (or two) that you control.

Recommended Structure

# Your private skills repository (never published)
~/my-skills-private/
  ├── SHARED.md                    ← Generated shared instructions
  ├── INDEX.md                     ← Generated skill index
  ├── config.json                  ← Toolkit configuration
  │
  ├── clean-code/SKILL.md
  ├── systematic-debugging/SKILL.md
  ├── refine-requests/SKILL.md
  ├── codebase-memory/SKILL.md
  ├── mobile-ui-patterns/SKILL.md
  ├── dependency-updates/SKILL.md
  ├── build-optimizer/SKILL.md
  └── ... (all your skills)
  │
  ├── projects/                     ← Per-project instruction files
  │   ├── project-alpha/AGENTS.md
  │   ├── project-beta/AGENTS.md
  │   └── project-gamma/
  │       ├── Core Rules.md
  │       └── Core Rules Compact.md
  │
  └── large-projects/
      └── project-gamma/
          └── ensure_symlinks.sh

Why Private?

Your skills are personal — they contain:

Your coding style and preferences
Your project's internal conventions and architecture
Your proprietary workflows and domain knowledge
Your private project structures

No one needs to see your refine-requests skill or your review-feedback workflow. The toolkit is public because it is generic infrastructure. The skills are private because they are your intellectual property.

How I Use This (Real Stats)

My personal setup — after unifying:

Metric	Value
AI tools wired	9 (Claude, Codex, Kimi, Gemini, Cursor, Kilocode, OpenCode, Windsurf, Claude Desktop)
Skills in canonical store	49 (all private, all mine)
Stale template files deleted	77 — eliminated duplicate AGENTS.md/GEMINI.md copies
Orphaned skills rescued	15 — from `~/.kimi/skills/` to canonical store
Duplicate skills removed	15 — from a project's marketplace clone
Generic marketplace skills archived	203 — removed from active project, not lost
Weekly health check	Auto-runs `skills doctor` every Sunday at 9:17 AM
Instruction files moved to canonical	5 — project-specific rules, no more drift
Core project rules	98KB file, single source, symlinked to 2 other repos
New tool onboarding	`skills sync <tool>` — one command

Weekly Health Check

A scheduled cron job runs skills doctor every Sunday morning to catch drift before it becomes a problem:

skills doctor    # Check all symlinks, config, indexes
skills check     # Scan for orphaned skills
skills report    # Usage stats and improvement tips

Verification

Before trusting the system, verify it:

node verify.js
# === Skills Ecosystem Verification ===
# [config]        ✓ loads successfully
# [skill paths]   ✓ 2 paths exist
# [skills scan]   ✓ 49 skills found, no duplicates
# [skill files]   ✓ all files valid
# [SHARED.md]     ✓ exists
# [instruction]   ✓ 6 symlinks + 1 regular valid
# [skills dirs]   ✓ 4 tools, 49 skills each, all healthy
# [MCP configs]   ✓ 7 tools, all have skills server
# ✓ ALL CHECKS PASSED (24 passed)

Tests

npm test

14 tests, Node's built-in runner, no extra dependencies. Covers:

sensitive.js — denylist detection (company names, ticket IDs, API keys, internal URLs)
fs-utils.js — symlink management, managed block insertion/updates
skills.js — skill scanning, frontmatter parsing, hidden directory filtering

CI runs on every push via GitHub Actions.

License

MIT — see LICENSE.

Star & Contribute

If this tool helps you, give it a star ⭐

Found a bug? Want a new feature? Have a question?

Open an issue — bug reports, feature requests, questions
Open a discussion — ideas, show-and-tell, Q&A
Open a PR — contributions welcome

Built by someone who tries every new AI tool and got tired of watching their skills fragment across 18 projects. If you also have a .claude/, .kimi/, .codex/, .gemini/, .cursor/, and .kilocode/ directory on the same machine, this is for you.

This server cannot be installed

license - permissive license

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

0dRelease cycle

11Releases (12mo)

Commit activity

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/moatazhamada/ai-omni-skills'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Omni Skills

The Problem This Solves

What This Toolkit Does

Three Portability Tiers

The MCP Server

Quick Start

Prerequisites

Setup Flags

25 Supported AI Tools

The skills CLI

How to Store Your Skills

Recommended Structure

Why Private?

How I Use This (Real Stats)

Weekly Health Check

Verification

Tests

License

Star & Contribute

Maintenance

Resources

Looking for Admin?

Latest Blog Posts

MCP directory API

The `skills` CLI