📦

Awesome Omni Skills

Public repository of AI coding skills, curated improved best-practice skills, and runtime surfaces for CLI, API, MCP, and A2A.

0 installs

Trust: 39 — Low

Agents

Ask AI about Awesome Omni Skills

I know everything about Awesome Omni Skills. Ask me about installation, configuration, usage, or troubleshooting.

0/500

Loading tools...

Reviews

Documentation

🧠 Awesome Omni Skills

Public Skill Repository · Curated Improved Best-Practice Skills · Runtime Surfaces

The skill catalog that installs itself.
CLI · API · MCP · A2A — all from a single npx command.

🚀 0 skills · 7 bundles · 9 install clients · 16 MCP clients · 4 runtime surfaces

🇺🇸 English · 🇪🇸 Español · 🇫🇷 Français · 🇩🇪 Deutsch · 🇮🇹 Italiano · 🇷🇺 Русский · 🇨🇳 中文（简体） · 🇯🇵 日本語 · 🇰🇷 한국어 · 🇸🇦 العربية · 🇮🇳 हिन्दी · 🇹🇭 ไทย · 🇻🇳 Tiếng Việt · 🇮🇩 Bahasa Indonesia · 🇲🇾 Bahasa Melayu · 🇳🇱 Nederlands · 🇵🇱 Polski · 🇸🇪 Svenska · 🇳🇴 Norsk · 🇩🇰 Dansk · 🇫🇮 Suomi · 🇵🇹 Português (Portugal) · 🇷🇴 Română · 🇭🇺 Magyar · 🇧🇬 Български · 🇸🇰 Slovenčina · 🇺🇦 Українська · 🇮🇱 עברית · 🇵🇭 Filipino · 🇧🇷 Português (Brasil)

⚡ Install in 1 min · 🛠️ Choose your tool · 📖 CLI Guide · 📦 Bundles · 🔌 Runtime · 💡 Why Awesome Omni Skills

📊 Project at a Glance

	Metric	Value
📦	Published Skills	`4027` native skills across 17 active categories
🎯	Bundles	`7` fully backed curated bundles
🖥️	Install Clients	`9` install-capable AI coding assistants
🔌	MCP Clients	`16` MCP config-capable clients across `33` first-class targets
🔐	Curated Output	`980` enhanced English derivatives in `skills_omni`
🧪	Validation Mix	`3472` passed · `555` warn · `0` errors
📋	Current Release	`v0.12.9`

🚀 New Here? Start Here

🔍 Searched for AI coding skills, Claude Code skills, Cursor skills, Codex CLI skills, Gemini CLI skills, Antigravity skills, or installable SKILL.md libraries? You're in the right place. 👇

1️⃣ What is this?

Awesome Omni Skills is an installable skill catalog and runtime for AI coding assistants. At its core, it is a public repository of reusable SKILL.md playbooks, a curated repository of improved best-practice derivatives, and the CLI, API, MCP, and A2A runtime surfaces that distribute and operate the same catalog.

Native intake enters skills/ in two ways: direct contributor PRs and reviewed repository-based external-import PRs. Curated English-only derivatives are then proposed separately into skills_omni/ by the private enhancement pipeline.

📋 What's included

Component	Description
🧠 Skills	Reusable `SKILL.md`-based playbooks for AI assistants, including native intake from direct contributor PRs and reviewed repository-based external-import PRs
📦 Manifests	Generated JSON manifests, bundles, and archives
🧭 Guided Install	Interactive TTY and visual terminal install flows
🌐 Catalog API	Read-only HTTP API for search, discovery, and downloads
🔌 MCP Server	Discovery, recommendation, and client-aware config tooling
🤖 A2A Runtime	Agent-to-agent task orchestration
✨ Enhancement Pipeline	Private enhancer publishes curated English derivatives into `skills_omni/`

2️⃣ Quick Start

# Open the visual shell in an interactive terminal
npx awesome-omni-skills

# Or force the text guided installer explicitly
npx awesome-omni-skills install --guided

3️⃣ Verify

test -d ~/.gemini/antigravity/skills && echo "✅ Skills installed"

4️⃣ Use your first skill

💬 "Use @brainstorming to plan a SaaS MVP."

💬 "Use @api-design to review this endpoint design."

💬 "Use @debugging to isolate this regression."

5️⃣ Start with a bundle

🎯 Goal	Bundle	Command
General engineering	`essentials`	`npx awesome-omni-skills --bundle essentials`
Product + app delivery	`full-stack`	`npx awesome-omni-skills --bundle full-stack`
Design systems	`design`	`npx awesome-omni-skills --bundle design`
Security review	`security`	`npx awesome-omni-skills --bundle security`
Infra and release	`devops`	`npx awesome-omni-skills --bundle devops`
LLM applications	`ai-engineer`	`npx awesome-omni-skills --bundle ai-engineer`
OSS maintenance	`oss-maintainer`	`npx awesome-omni-skills --bundle oss-maintainer`

🧩 Core Concepts

Before comparing bundles or picking an install path, understanding these five building blocks helps:

Concept	What it means
🧠 Skills	Reusable `SKILL.md` playbooks that teach an assistant how to execute a workflow well
📦 Catalog Artifacts	Generated JSON and archive outputs enabling search, comparison, download, and install
🔌 MCP Config	Client-side configuration for assistants to discover Awesome Omni Skills through MCP tools
🤖 A2A Runtime	Agent-to-agent orchestration for discovery, recommendation, and install-plan handoff
✨ Curated Output	`skills_omni/` — the Awesome Omni Skills-maintained enhanced surface, separate from native upstream intake

📝 Native/Curated policy:

skills/ accepts native upstream intake in any language, whether submitted directly or proposed by the private external-sync runtime

skills_omni/ is always curated and published in English

skills_omni/ is a one-way surface and does not loop back into native intake

direct contributor PRs and repository-based external intake share the same validator, metadata refresh, and enhancer path

💡 Why Awesome Omni Skills

Not just "another repository with skills in folders." Awesome Omni Skills has a stronger contract and a broader runtime surface.

If you want…	📁 Typical skills repo	✨ Awesome Omni Skills
Install into a real assistant	Manual copy or custom script	`npx awesome-omni-skills`, guided install, visual UI, selective `--skill` and `--bundle`
Search and compare skills	Browse markdown manually	Generated catalog, filtering, bundle planning, search, compare, and recommendation
Use the same data across tools	Separate logic per tool	Shared manifests and catalog for CLI, API, MCP, and A2A
Configure MCP clients	Hand-edit files	`config-mcp`, local sidecar previews, generated recipes, and allowlisted writes
Trust repository content	Minimal or ad hoc linting	Critical static security gate blocks unsafe patterns such as remote content piped into shell or instructions that try to expose prompts, secrets, or hidden context
Trust releases	Best-effort packaging	Checksums, signed archives, ClamAV + VirusTotal verified release CI, and publish preflight
Curate community intake	Whatever lands stays as-is	Native intake in `skills/`, curated English derivatives in `skills_omni/` with attribution

🖥️ Compatibility and Invocation

These skills follow the SKILL.md model and can be used as a normal repository, but the package also installs and configures them across a broad surface:

9 install-capable clients · 16 MCP config-capable clients

🎯 Install-Capable Clients

Tool	Type	Invocation Example	Install Path
🟢 Claude Code	CLI	`Use brainstorming to plan a feature`	`~/.claude/skills`
🔵 Cursor	IDE	`@brainstorming help me plan a feature`	`~/.cursor/skills`
🟡 Gemini CLI	CLI	`Use brainstorming to plan a feature`	`~/.gemini/skills`
🔴 Codex CLI	CLI	`Use brainstorming to plan a feature`	`~/.codex/skills`
🟠 Kiro	CLI / IDE	`Use brainstorming to plan a feature`	`~/.kiro/skills`
🟣 Antigravity	IDE	`Use @brainstorming to plan a feature`	`~/.gemini/antigravity/skills`
🟤 Goose	CLI	`goose session --with-extension ...`	`~/.agents/skills`
🟧 Qwen Code	CLI	`Use @brainstorming to plan a feature`	`<workspace>/.qwen/skills`
⚪ OpenCode	CLI	`opencode run @brainstorming`	`<workspace>/.opencode/skills`

🔌 Broader MCP Configuration Coverage (16 clients)

These targets are part of the supported MCP configuration surface, even when they are not install targets for skill directories:

Client or Surface	Support Type	Notes
Claude settings and desktop	MCP config	Settings, desktop, and project-aware flows
VS Code	MCP config	User, workspace, insiders, and Dev Container targets
Gemini	MCP config	User and workspace settings
Cline	MCP config	First-class config target
GitHub Copilot CLI	MCP config	User and repo config targets
Continue	MCP config	Workspace YAML generation
Windsurf	MCP config	User config target
Zed	MCP config	Workspace config target
Goose	MCP config	User config target with generated recipe
Kilo Code	MCP config	User, project, and workspace targets
Junie	MCP config	Project and user config targets

⚡ Installation

Option A: Install with `npx` (recommended)

npx awesome-omni-skills

Option B: Guided install

npx awesome-omni-skills install --guided

Option C: Specific skill

npx awesome-omni-skills --skill api-design

Option D: Install a bundle

npx awesome-omni-skills --bundle devops

Option E: Target a specific client

npx awesome-omni-skills --cursor --skill omni-figma
npx awesome-omni-skills --codex --bundle full-stack
npx awesome-omni-skills --claude --skill debugging

Option F: Custom path

npx awesome-omni-skills --path ./my-skills --skill architecture

🔎 Discovery before install

npx awesome-omni-skills find figma
npx awesome-omni-skills find mcp --sort quality --min-quality 90 --min-security 95
npx awesome-omni-skills find foundation --bundle essentials --install --yes

🛠️ Choose Your Tool

Tool	Install Command	First Use
🟢 Claude Code	`npx awesome-omni-skills --claude`	`Use brainstorming to plan a feature`
🔵 Cursor	`npx awesome-omni-skills --cursor`	`@brainstorming help me plan a feature`
🟡 Gemini CLI	`npx awesome-omni-skills --gemini`	`Use brainstorming to plan a feature`
🔴 Codex CLI	`npx awesome-omni-skills --codex`	`Use brainstorming to plan a feature`
🟣 Antigravity	`npx awesome-omni-skills --antigravity` (default)	`Use @brainstorming to plan a feature`
🟠 Kiro	`npx awesome-omni-skills --kiro`	`Use brainstorming to plan a feature`
🟤 Goose	`npx awesome-omni-skills --goose`	`goose session --with-extension ...`
🟧 Qwen Code	`npx awesome-omni-skills --qwen`	`Use @brainstorming to plan a feature`
⚪ OpenCode	`npx awesome-omni-skills --opencode`	`opencode run @brainstorming`
🧩 Saved custom target	`npx awesome-omni-skills --target-id custom-team-cli`	Depends on your tool
📂 Custom path	`npx awesome-omni-skills --path ./my-skills`	Depends on your tool

📖 Not sure where to start?

🚀 Getting Started — install and verify in under 2 minutes

🧭 CLI User Guide — full command reference

📗 Usage Guide — prompts, patterns, and runtime modes

🔌 Runtime Surfaces

Awesome Omni Skills is not only a library of skills. It exposes four runtime surfaces that consume the same generated catalog:

Surface	State	What it does	Example
🖥️ CLI	✅ Available	Find, install, diagnose, visual UI, boot services, smoke checks	`npx awesome-omni-skills doctor`
🌐 Catalog API	✅ Available	Read-only catalog, search, bundles, compare, install plans, downloads, Swagger UI on `/docs`	`npx awesome-omni-skills api --port 3333`
🔌 MCP	✅ Available	Discovery, recommendation, install preview, local sidecar, config flows	`npx awesome-omni-skills mcp stream --local`
🤖 A2A	✅ Available	Task lifecycle, handoff, polling, streaming, cancelation, persistence	`npx awesome-omni-skills a2a --port 3335`

🖥️ Visual shell and operator commands

npx awesome-omni-skills ui                # Ink visual terminal hub
npx awesome-omni-skills ui --text         # Text fallback UI
npx awesome-omni-skills doctor            # Environment diagnostics
npx awesome-omni-skills smoke             # Full release preflight
npx awesome-omni-skills publish-check     # Package publication checks

The visual shell now includes:

a grouped home hub for install, runtime, and utility actions
a search-first catalog explorer for skills and bundles
richer install and runtime preview panels with step rails and command previews
persisted local settings for theme, compact mode, and screen reader preference
explicit INK_SCREEN_READER=true and ui --text fallback paths

🔌 MCP transports and config

# Start MCP transports
npx awesome-omni-skills mcp stdio
npx awesome-omni-skills mcp stream
npx awesome-omni-skills mcp sse
npx awesome-omni-skills mcp stream --local     # Local sidecar with filesystem tools

# Configure MCP for any supported client
npx awesome-omni-skills config-mcp --list-targets
npx awesome-omni-skills config-mcp --target continue-workspace --transport stream --url http://127.0.0.1:3334/mcp
npx awesome-omni-skills config-mcp --target windsurf-user --transport sse --url http://127.0.0.1:3335/sse --write

📦 Catalog, Bundles, and Curated Output

📊 Current Catalog

Metric	Current State
🧠 Native intake skills	4027
📂 Active categories	17
📦 Fully backed bundles	7
✨ Curated derivatives	980 in `skills_omni`
🧪 Validation	3472 passed / 555 warn / 0 errors
📋 Release	v0.12.9

📦 Bundle Availability

Bundle	Skills	Members
🧰 `essentials`	4/4 ✅	`find-skills` · `brainstorming` · `architecture` · `debugging`
🌐 `full-stack`	5/5 ✅	`frontend-design` · `api-design` · `database-design` · `omni-figma` · `auth-flows`
🎨 `design`	5/5 ✅	`frontend-design` · `omni-figma` · `design-systems-ops` · `accessibility-audit` · `design-token-governance`
🛡️ `security`	4/4 ✅	`security-auditor` · `vulnerability-scanner` · `incident-response` · `threat-modeling`
⚙️ `devops`	5/5 ✅	`docker-expert` · `kubernetes` · `terraform` · `observability-review` · `release-engineering`
🤖 `ai-engineer`	7/7 ✅	`rag-engineer` · `prompt-engineer` · `llm-patterns` · `eval-design` · `context-engineering` · `data-contracts` · `model-serving`
🔧 `oss-maintainer`	4/4 ✅	`find-skills` · `create-pr` · `changelog` · `documentation`

✨ Native Intake → Curated Output

Surface	Purpose	Language
📥 `skills/`	Native intake	Any language
✨ `skills_omni/`	Curated Omni-maintained output	Always English

ℹ️ Changes to native skills are reprocessed by the private enhancer and refreshed in the curated baseline. This makes skills_omni/ a maintained catalog surface, not a second copy.

🛡️ Security and Release Posture

Awesome Omni Skills ships a stronger release and verification story than a plain markdown repository.

🧪 Validation and Smoke Checks

npm run validate         # Skill validation and metadata generation
npm run build            # Full build pipeline
npm test                 # Legacy integration tests + Vitest unit suite
npm run test:unit        # Fast Vitest unit tests only (~500ms)
npm run test:coverage    # Vitest with V8 coverage
npm run smoke            # Full release preflight

📋 What the pipeline validates

✅ Skill validation and metadata generation
✅ Critical security gating on native intake before PR merge
✅ Taxonomy normalization and recategorization tooling
✅ Catalog and archive generation
✅ Legacy integration tests (Python PTY + Node TUI assertions)
✅ Vitest unit suite for catalog-core scoring, search, and filtering logic
✅ API, MCP, and A2A boot paths
✅ Archive verification
✅ OpenAPI 3.1 contract served via Swagger UI at /docs
✅ Package preflight with npm pack --dry-run

🔐 Release posture

Control	Description
🔒 SHA-256 checksums	Checksum manifests for all archives
✍️ Signed artifacts	Detached signatures on release artifacts
🤖 CI-enforced	Release verification in CI before publication
🦠 Scanner gates	ClamAV and VirusTotal both required in release verification before publish
📦 GitHub Release	Automated GitHub Release generation
📋 npm publication	From verified tarball only
🔄 Auto release	On qualifying skill merges to `main`

Auto-release triggers only when a merge changes:

skills/*/**
skills_omni/*/**
data/bundles.json

Doc-only changes do not trigger package publication.

🛡️ Repository safety contract

Native intake does not accept skills with critical security findings.
The static validator blocks high-risk patterns before a skill can merge into the public catalog.
The current hard blockers include:
- remote content piped directly into shell execution
- instructions that try to reveal prompts, secrets, or hidden runtime context
Published releases go through a stricter second layer:
- ClamAV scanning
- VirusTotal hash lookup
- archive checksum verification
- detached signature verification in release CI

This is a user-facing benefit, not just build plumbing: the catalog favors installable skills that already passed the same restrictive security gate the project uses internally.

📖 Documentation Map

👤 For Users

Doc	What You'll Learn
🚀 Getting Started	Install, verify, and invoke in under 2 minutes
🧭 CLI User Guide	Full command reference and real-world patterns
📗 Usage Guide	CLI commands, install modes, runtime, and MCP config
📦 Bundles	Curated bundles and availability
📚 Catalog	Auto-generated catalog of published skills
🔧 System Runbook	Build, serve, secure, and troubleshoot

🏗️ For Architects

Doc	What You'll Learn
🗂️ Project Structure	What is actually tracked in this workspace and where each runtime lives
🌐 Catalog API	HTTP endpoints, filtering, governance, and downloads
🧩 CLI Guided Installer	Behavioral contract for the guided installer
🖥️ CLI Visual Shell	Ink visual shell and state model
🧬 Skill Family, Variant, and Provenance Model	Catalog grouping, variant selection, and provenance contract
🔌 Local MCP Sidecar	Filesystem tools and allowlist model
📊 Client Support Matrix	Full client and writer reference
🏷️ Skill Classification	Taxonomy, scoring, and metadata
🛡️ Security Validation	Scanners, archives, and signatures
📋 Skill Manifest	Machine-readable manifest format

🤝 For Contributors

Doc	What You'll Learn
📝 Contributing Guide	Repo workflow and PR expectations
🧾 Skill PR Workflow	Native intake, enhancer processing, reviewer expectations
📄 Skill Template	Starter `SKILL.md` with frontmatter and structure
🔬 Skill Anatomy	Structure and quality expectations
✅ Quality Bar	Acceptance criteria
🏆 High-Score Playbook	What drives high scores

🗂️ Repository Layout

Path	Purpose
📂 `skills/`	Canonical authored skills and native intake from direct PRs or reviewed repository-based imports
✨ `skills_omni/`	Curated Omni-maintained enhanced derivatives
📖 `docs/`	User, contributor, architecture, operations, and spec documentation
📦 `dist/`	Generated manifests, bundles, catalog, and archives
📁 `data/`	Bundle definitions and static supporting data
🧠 `packages/catalog-core/`	Shared catalog runtime with `ICatalogStorageAdapter` dependency injection
🌐 `packages/server-api/`	Read-only HTTP API with OpenAPI/Swagger UI on `/docs`
🔌 `packages/server-mcp/`	MCP server and local sidecar
🤖 `packages/server-a2a/`	A2A runtime and task orchestration
🖥️ `packages/cli/`	Unified CLI entrypoints, install logic, and Ink visual TUI (ESM-native)
⚙️ `tools/scripts/`	Validation, generation, release, and test scripts
🧪 `vitest.workspace.js`	Vitest monorepo workspace configuration

ℹ️ dist/ is intentionally versioned because the generated artifacts are part of the install, API, MCP, A2A, smoke, and release contract.

🤝 Contributing

Awesome Omni Skills accepts native upstream skill intake under skills/.

Rule	Details
📥 Native intake	May be rough, authored in any language, and can arrive from direct PRs or reviewed external-import branches
✨ Curated output	`skills_omni/` reserved for automation-authored Omni derivatives
🌍 Upstream repo proposals	Add a URL to `SOURCES.txt` — one line, one URL — or update one row in REPOSITORY-SOURCES.md to nominate a repository for operator review; repo-first proposals can now use `branch=auto` and `skills_path=auto`
🚫 Manual edits	Public manual edits to `skills_omni/` are rejected
🔄 Reprocessing	Private enhancer reprocesses native changes and refreshes curated baseline

📖 Start with: Contributing Guide · Skill PR Workflow · Repository Sources

📄 License

Type	License
💻 Code and tooling	MIT License
📝 Documentation and skill content	CC BY 4.0

Made with 🧠 by the Awesome Omni Skills Team

⭐ Star this repo · 🐛 Report a bug · 💬 Discussions

If Awesome Omni Skills helps you build faster, consider giving it a ⭐ — it helps others discover the project!