$ registry status: live — 90 real skills · submissions open
The registry for AI skills, versioned like real software.
AI Skill Bank is a versioned vault of reusable AI capabilities — skills you can pin, audit, and upgrade, plus a directory of MCP servers that expose them to your agents. Every entry carries a README, a license, and a changelog.
$ skillbank search "solana" # solana-rpc-toolkit v1.0.0 MIT — Solana mainnet RPC via Helius $ skillbank install solana-rpc-toolkit@1.0.0 # pinned to 1.0.0 · README + changelog fetched · license MIT
Why a registry, not a folder of prompts
Copy-pasted prompts drift, break, and can't be audited. Skill Bank treats capabilities as packages.
Versioned
Strict semver on every skill. Pin solana-rpc-toolkit@1.0.0 in production and upgrade on your schedule — never silently.
Documented
Every listing ships a README: inputs, configuration, worked examples, and a full changelog. No mystery blobs.
MCP-ready
Skills flagged MCP-compatible map cleanly onto Model Context Protocol servers and tools. One catalog, two surfaces.
Featured skills
Production-tested skills from the registry’s own authors — free to download, MIT licensed.
MCP servers directory
Standalone servers speaking the Model Context Protocol — over stdio for local agents or SSE for remote ones. Browse the full directory →
| Server | Description | Transport | Version |
|---|---|---|---|
| fs-tools | Scoped file read/write, search, and patch operations for agent sandboxes. | stdio | v1.6.0 |
| webfetch | Fetch and clean web content to markdown with redirect and robots handling. | SSE | v0.9.2 |
| db-bridge | Read-only SQL execution against Postgres/MySQL with query guardrails. | stdio | v2.0.3 |
How publishing works
Submissions are open — the checklist below is the review bar.
Write a README
Overview, inputs, configuration, and at least one worked example. See the publishing guide.
Follow semver
Start at 0.x or 1.0.0. Breaking changes bump the major; the registry enforces the policy.
Pick a license
MIT or Apache-2.0 to start. The license travels with every version, pinned in the manifest.
Submit your package
Attach the zip or repo URL on the submission page — validation is instant, review takes 1–2 days.
Start with the docs.
Five minutes: installing a skill, pinning versions, and what makes a listing worth publishing.