Skip to content

rolecraft-sh/registry

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

12 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

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",
  "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:

  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

If all checks pass, a maintainer is notified and merges the PR. 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
installs number no 0
stars number no 0

Currently listed skills

Slug Name Author Stars
task-decomposer Task Decomposer sametcelikbicak 3
coverage-guard Coverage Guard sametcelikbicak 3

Want to see yours here? Publish your skill.

Related

License

MIT

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages