skills
A catalog of Claude Code skills, published as a browsable, downloadable site by a companion Next.js app.
Table of Contents
Background
Each subdirectory under catalog/ is one self-contained Claude Code skill: a
SKILL.md describing when and how Claude should use it, plus optional reference docs, scripts,
and evals. The site/ app reads that catalog at build time and turns it into a static
site where each skill can be browsed or downloaded as a .skill archive — adding, editing, or
removing a skill under catalog/ requires no frontend code changes.
Install
This repo has two independent parts, and installation depends on which one you want.
To use a skill with Claude Code, either install it as part of a plugin or copy/symlink it — see
Usage below.
To run the catalog site locally:
cd site
npm install
Dependencies
- Node.js (see site/package.json for the exact toolchain: Next.js 15, React 19)
- No dependencies are required to read or use a skill directly from
catalog/
Usage
Using a skill in Claude Code
Skills are loaded from .claude/skills/ by the Claude Code harness, not from catalog/ directly.
Copy or symlink the one you want into your project:
mkdir -p .claude/skills
cp -r catalog/pr-description .claude/skills/
Claude Code picks it up automatically the next time it lists available skills. You can also
download any skill as a .skill archive from the published catalog site.
Using the plugins
The repo is also a Claude Code plugin marketplace
(.claude-plugin/marketplace.json) that bundles catalog skills
into two plugins:
core — organisation-wide priorities: the security, compliance, brand and UX policy skills
other plugins build on.sdlc — the AI-Native SDLC workflow (sdlc-plan → sdlc-design → sdlc-build) plus the
sdlc-status navigator. Depends on core, so installing it installs both.
claude plugin marketplace add JosephSearle/skills
claude plugin install sdlc@searle-skills
Then, in a session, /sdlc:sdlc-status shows where each change under docs/sdlc/ stands and which
skill to run next; /sdlc:sdlc-plan starts a new one.
Running the catalog site
cd site
npm run dev
▲ Next.js 15.x.x
- Local: http://localhost:3000
npm run dev regenerates site/generated/skills-index.json from catalog/ before starting
(via the predev hook), so any skill you add is reflected immediately.
To produce the static export used in production:
cd site
npm run build
The output is written to site/out/.
Skill structure
Every skill under catalog/ follows the same shape:
catalog/<skill-name>/
├── SKILL.md # required: YAML frontmatter (name, description, summary) + instructions
├── references/ # optional: supporting docs loaded conditionally by the skill
├── scripts/ # optional: helper scripts the skill can invoke
└── evals/
└── evals.json # optional: structured eval cases, checked by npm run validate:evals
SKILL.md frontmatter is validated on every CI run — a missing name, description, or
summary field fails the build (see site/scripts/build-skills-index.mjs).
Contributing
Contributions are welcome. To add or change a skill:
- Add or edit a folder under
catalog/, following the structure above
- From
site/, run npm run build:index to confirm the skill is picked up and passes validation
- Run
npm run validate:evals if the skill includes evals/evals.json
- Run
npm run lint:ci and npm run typecheck from site/ before opening a pull request
See CLAUDE.md for the full repository layout and command reference, and
REVIEW.md for what a review looks for.
License
MIT © 2026 Joseph Searle
