Skillyard

A skill registry for AI agents. Keep open-source skills and your company's private ones in one place, and install them into Claude Code, OpenAI Codex, Cursor and any AGENTS.md agent (Gemini CLI, Copilot, Windsurf, Aider), or let agents search and load them live over MCP.

A skill is a folder with a SKILL.md (YAML frontmatter + instructions) and optional scripts/, references/ and templates/, following the Agent Skills format. Skillyard adds what a team needs around that format: private org scopes with access tokens, immutable versions, a security scan on every publish, one-command installs for every agent, a project manifest teammates can sync, and an audit log.

npx skillyard install code-review @acme/deploy-runbook --agent claude,codex --save

Live demo: https://agentwik-labs.github.io/skillyard/ (read-only; click Sign in and type acme or northwind to see two fictional companies' private skills).

Reports: We scanned the 34 most-installed skill repos · Do skills actually help? Lift evals · Good skills, bad skills: 12 examples and why

Create skills: builder, generators and skill-writer

Six generators cover the knowledge businesses actually keep: procedure (runbooks, month-end close), checklist (review gates), voice (brand and writing), playbook (sales and customer plays), decision (who approves what) and metric (how numbers are defined).

npx skillyard generate                                   # list generators
npx skillyard generate decision --from refund-policy.md  # fill one from your own document, with a test case

The same generators run in the web builder (answer a few questions, download a zip; nothing leaves the page) and in Studio's Create a skill, where the result is tested and waits for approval like every other proposal. The skill-writer skill does the same from inside Claude Code or Codex.

Related MCP server: Omni Skills

Studio: your agents learn from your corrections

npx skillyard studio          # http://127.0.0.1:7430, local only
npx skillyard studio --demo   # try it on a fictional team's data first

Every time someone tells an agent "no, we use pnpm here" or "I didn't ask for that", it's a free test case. Studio turns those moments into skills that stop the mistake from coming back, and proves each one works:

1. Find. Reads Claude Code and Codex session logs on your machine and spots corrections. Keeps only the redacted moment (emails, keys, tokens, long numbers and your home path removed).

2. Propose. Groups corrections that repeat into themes, then drafts a new skill or an edit to one you already use, with test cases built from the real requests where the agent went wrong.

3. Prove. Runs each draft with and without (or against the current version of the skill) and grades the answers. You see the before and after, the diff, and the corrections that led to it.

4. You decide. Approve to install into Claude Code and/or Codex, edit first, or reject (it won't be proposed again). Every approval keeps a backup and can be undone.

Consent is the product. Three separate switches, all off until you turn them on: reading logs, letting a model review redacted excerpts (through your own Claude Code login; you can see exactly what would be sent), and reviewing on a schedule. Projects can be left out (work for an employer or client). Turning reading off deletes everything Studio read. Nothing is ever installed without an explicit approval, and every decision is logged.

The overview tracks the number engineering leads ask for: corrections per 100 prompts, by week. Think of it as your team's defect rate for AI work, with the pipeline from corrections to proven skills next to it.

What's in the box

Quick start

npm run dev                # loads the bundled skills, then serves http://127.0.0.1:7420

seed prints a demo token for each fictional company (also saved to data/demo-tokens.json). Paste one into Sign in in the web UI to see that company's private skills, or use it from the CLI:

export SKILLYARD_REGISTRY=http://127.0.0.1:7420
node bin/skillyard.js search review
node bin/skillyard.js login --token sy_…          # an acme token
node bin/skillyard.js search deploy               # now includes @acme/deploy-runbook
node bin/skillyard.js install @acme/deploy-runbook code-review --agent all

Use from your agent

Install copies skills into the agent's own folder, so they load automatically and work offline:

skillyard install code-review                    # detected agents in this project (default: claude)
skillyard install @acme/incident-response -g     # user-wide (Claude Code, Codex)
skillyard install sql-review --agent cursor      # writes .cursor/rules/sql-review.mdc + .cursor/skills/sql-review/
skillyard list && skillyard update

MCP lets the agent search everything your token can see and pull in a skill when a task calls for it:

skillyard connect claude --write    # runs `claude mcp add --transport http skillyard <registry>/mcp …`
skillyard connect codex --write     # adds [mcp_servers.skillyard] to ~/.codex/config.toml
skillyard connect cursor --write    # .cursor/mcp.json (token read from ${env:SKILLYARD_TOKEN})
skillyard connect vscode | gemini | claude-desktop

Claude Code plugins: /plugin marketplace add agentwik-labs/skillyard, then /plugin install skillyard-engineering@skillyard.

See docs/agents.md for where each agent reads skills and how each config looks.

Roll it out to your team

npx -y skillyard kit .

Copies the team starter kit into your repo: a two-week plan, a 30-minute kickoff agenda, a skill review checklist, fill-in data-handling and definition-of-done skills with evals, a new-skill template, and a CI check. No server needed: skillyard install ./skills/* --agent all installs straight from the folder.

Run it for a company

SKILLYARD_ADMIN_TOKEN=$(openssl rand -hex 24) skillyard serve --host 0.0.0.0 --data /var/lib/skillyard
skillyard org create acme --name "Acme Cloud"            # prints an owner token (read + publish)
skillyard token create --org acme --scopes read --name laptop-dana
skillyard new deploy-runbook && skillyard publish deploy-runbook --org acme

Sign-ups on the public site (the monthly report, audit requests, the Studio waitlist) post to the email-list endpoint in web/config.js; until one is set, the forms point to the contact link instead.

Or with Docker: docker build -t skillyard . && docker run -p 7420:7420 -v skillyard-data:/data skillyard. Put it behind TLS (any reverse proxy). Tokens are stored as SHA-256 hashes; org members manage tokens and see the activity log on their org page. See docs/self-hosting.md.

Authoring skills

my-skill/
  SKILL.md          # required: frontmatter name + description, then instructions
  skill.json        # optional: version, title, summary, category, tags, visibility
  scripts/          # helpers the agent runs (stdlib-only is kindest)
  references/       # long detail the agent reads on demand
  templates/        # fill-in documents

Add evals/evals.json (tasks plus pass/fail checks) and run skillyard eval <dir> --model haiku --runs 3 to see whether the skill helps. skillyard validate <dir> checks the format and runs the same security scan as the server. Versions are immutable; bump version in skill.json to publish a change. Contribution rules for the open-source set are in CONTRIBUTING.md.

API

Development

npm test           # node:test, no dependencies
npm run validate   # validate + scan every bundled skill
npm run build:marketplace

MIT licensed. Skills in registry/public are MIT; the seed/orgs companies are fictional demo data.