README.md

July 27, 2026 · View on GitHub

RoleCraft

rolecraft Registry

Validate Powered by rolecraft MIT

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:

  1. Fork this repo
  2. Edit index.json — add your entry to the skills array
  3. 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

RuleDetails
Slug formatkebab-case only: ^[a-z0-9]+(-[a-z0-9]+)*$. Example: my-skill, react-rules
Slug uniquenessEvery slug must be unique across the entire registry. Check index.json first
Author matchThe author field must match your GitHub username (PR author)
Repo must existThe repo must be a valid GitHub repo containing a SKILL.md
Schema validationYour entry must validate against schema.json
No code uploadOnly metadata goes in index.json. The actual skill stays in your repo

Validation checks

Every PR runs these automated checks:

  1. JSON syntaxindex.json must be valid JSON
  2. Schema validation — Each entry must match schema.json
  3. Duplicate slugs — No two skills with the same slug
  4. Owner verification — The author field must match the PR creator's GitHub username
  5. Source repo check — The repo must 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:

FieldTypeRequiredExample
slugstringyesmy-skill
namestringyesMy Skill
descriptionstringnoDoes something useful
repostringyesuser/my-skill
authorstringyesuser
versionsarrayyes["v1.0.0"]
lateststringyesv1.0.0
categorystringnotesting
installsnumberno0
starsnumberno0

Category distribution

CategoryCount
development23
design6
testing5
security5
frontend5
methodology5
content5
devops4
code-review3
ui-ux2
maintenance2
mobile1

Total: 66 skills across 12 categories. The full list is in index.json.

Want your skill here? Publish it.

License

MIT