README.md
July 27, 2026 · View on GitHub
rolecraft Registry
Central skill registry for rolecraft — discover, publish, and share AI agent skills.
What is this?
The rolecraft Registry is a community-curated index of AI agent skills. Each entry is just metadata (slug, name, repo URL). The actual skill code stays in the author's own repository.
Skills are added via PR. Validation is fully automated — a maintainer reviews and merges once checks pass.
Quick start
Search the registry
npx rolecraft search react --registry
Install from registry
npx rolecraft install coverage-guard
Publish your own skill
# Set your GitHub token (scope: repo)
export GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxx
# Publish from your skill directory
npx rolecraft publish ./my-skill/
How to add a skill (manual PR)
Don't use the CLI? You can add your skill by editing index.json directly:
- Fork this repo
- Edit
index.json— add your entry to theskillsarray - Commit and create a PR
Example entry:
{
"slug": "my-skill",
"name": "My Skill",
"description": "What this skill does",
"category": "development",
"repo": "your-username/your-skill-repo",
"author": "your-username",
"versions": ["v1.0.0"],
"latest": "v1.0.0"
}
Constraints
| Rule | Details |
|---|---|
| Slug format | kebab-case only: ^[a-z0-9]+(-[a-z0-9]+)*$. Example: my-skill, react-rules |
| Slug uniqueness | Every slug must be unique across the entire registry. Check index.json first |
| Author match | The author field must match your GitHub username (PR author) |
| Repo must exist | The repo must be a valid GitHub repo containing a SKILL.md |
| Schema validation | Your entry must validate against schema.json |
| No code upload | Only metadata goes in index.json. The actual skill stays in your repo |
Validation checks
Every PR runs these automated checks:
- JSON syntax —
index.jsonmust be valid JSON - Schema validation — Each entry must match
schema.json - Duplicate slugs — No two skills with the same slug
- Owner verification — The
authorfield must match the PR creator's GitHub username - Source repo check — The
repomust be a valid GitHub repository
If all checks pass, the PR is auto-merged. If any check fails, check the Action logs for details.
Schema reference
Full schema at schema.json. Required fields:
| Field | Type | Required | Example |
|---|---|---|---|
slug | string | yes | my-skill |
name | string | yes | My Skill |
description | string | no | Does something useful |
repo | string | yes | user/my-skill |
author | string | yes | user |
versions | array | yes | ["v1.0.0"] |
latest | string | yes | v1.0.0 |
category | string | no | testing |
installs | number | no | 0 |
stars | number | no | 0 |
Category distribution
| Category | Count |
|---|---|
| development | 23 |
| design | 6 |
| testing | 5 |
| security | 5 |
| frontend | 5 |
| methodology | 5 |
| content | 5 |
| devops | 4 |
| code-review | 3 |
| ui-ux | 2 |
| maintenance | 2 |
| mobile | 1 |
Total: 66 skills across 12 categories. The full list is in index.json.
Want your skill here? Publish it.
Related
- rolecraft — the CLI that uses this registry
- rolecraft-action — GitHub Action for CI/CD
License
MIT