registry
Skill0 starsChanged 6 months agoMITView on GitHub
Private skill distribution system. Use when the user wants to install, use, add, push, remove, sync, list, or search for skills, agents, or prompts from their private registry catalog. Triggers on /registry commands or mentions of registry, skill distribution, or agentic management.
- Reads credentials
- Commits and pushes
7 other projects use a version of this.
Adopted by
Most recently taken up by
- JetBrains/intellij-communitytheir own version, first seen Nov 7, 2026
- JetBrains/MPStheir own version, first seen Nov 3, 2026
- Kairos-commu/socletheir own version, first seen Oct 22, 2026
- Alwurts/simple-aitheir own version, first seen Oct 8, 2026
- DetachHead/rebasedtheir own version, first seen Oct 8, 2026
- xeeva/Genesistheir own version, first seen Mar 29, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- JetBrains/intellij-community★ 21ksame name
- DetachHead/rebased★ 6.5ksame name
- JetBrains/MPS★ 1.7ksame name
- Alwurts/simple-ai★ 755same name
- xeeva/Genesis★ 17same name
- frames-engineering/skills★ 4same name
- Kairos-commu/socle★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 69
Local paths: start with / or ~:
- Distinctive: line 70
Use the path directly. Copy the parent directory of the referenced file.
- Very specific: line 84
When working with GitHub sources, prefer gh api for accessing single files (e.g., reading a SKILL.md to check metadata).
- Very specific: line 96
Commit with message: registry: updated <skill name> <what changed>
- Very specific: line 107
When resolving dependencies: look up each reference in registry.yaml, fetch all dependencies first (recursively), then fetch the requested …
- Very specific: line 126
If the user says "global" or "globally", use the global directory.
- Distinctive: line 127
If the user specifies a custom path, use that path.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The Registry
A meta-skill for private-first distribution of agentics (skills, agents, and prompts) across agents, devices, and teams.
Variables
Update these after forking and cloning the registry repo.
- REGISTRY_REPO_URL:
<your forked repo url> - REGISTRY_YAML_PATH:
~/.claude/skills/registry/registry.yaml - REGISTRY_SKILL_DIR:
~/.claude/skills/registry/
How It Works
The Registry is a catalog of references to your agentics. The registry.yaml file points to where skills, agents, and prompts live (local filesystem or GitHub repos). Nothing is fetched until you ask for it.
The registry.yaml is a catalog, not a manifest. Entries define what's available — not what gets installed. You pull specific items on demand with /registry use <name>.
Commands
| Command | Purpose |
/registry install | First-time setup: fork, clone, configure |
/registry add <details> | Register a new entry in the catalog |
/registry use <name> | Pull from source (install or refresh) |
/registry push <name> | Push local changes back to source |
/registry remove <name> | Remove from catalog and optionally local |
/registry list | Show full catalog with install status |
/registry sync | Re-pull all installed items from source |
/registry search <keyword> | Find entries by keyword |
Cookbook
Each command has a detailed step-by-step guide. Read the relevant cookbook file before executing a command.
| Command | Cookbook | Use When |
| install | cookbook/install.md | First-time setup on a new device |
| add | cookbook/add.md | User wants to register a new skill/agent/prompt in catalog |
| use | cookbook/use.md | User wants to pull or refresh a skill from the catalog |
| push | cookbook/push.md | User improved a skill locally and wants to update the source |
| remove | cookbook/remove.md | User wants to remove an entry from the catalog |
| list | cookbook/list.md | User wants to see what's available and what's installed |
| sync | cookbook/sync.md | User wants to refresh all installed items at once |
| search | cookbook/search.md | User is looking for a skill but doesn't know the exact name |
When a user invokes a /registry command, read the matching cookbook file first, then execute the steps.
Source Format
The source field in registry.yaml supports these formats (auto-detected):
/absolute/path/to/SKILL.md— local filesystemhttps://github.com/org/repo/blob/main/path/to/SKILL.md— GitHub browser URLhttps://raw.githubusercontent.com/org/repo/main/path/to/SKILL.md— GitHub raw URL
Both GitHub URL formats are supported. Parse org, repo, branch, and file path from the URL structure. For private repos, use SSH or GITHUB_TOKEN for auth automatically.
Important: The source points to a specific file (SKILL.md, AGENT.md, or prompt file). We always pull the entire parent directory, not just the file.
Source Parsing Rules
Local paths start with / or ~:
- Use the path directly. Copy the parent directory of the referenced file.
GitHub browser URLs match https://github.com/<org>/<repo>/blob/<branch>/<path>:
- Parse:
org,repo,branch,file_path - Clone URL:
https://github.com/<org>/<repo>.git - File location within repo:
<path>
GitHub raw URLs match https://raw.githubusercontent.com/<org>/<repo>/<branch>/<path>:
- Parse:
org,repo,branch,file_path - Clone URL:
https://github.com/<org>/<repo>.git - File location within repo:
<path>
GitHub Workflow
When working with GitHub sources, prefer gh api for accessing single files (e.g., reading a SKILL.md to check metadata). For pulling entire skill directories, clone into a temp dir per the steps below.
Fetching (use):
- Clone the repo with
git clone --depth 1 <clone_url>into a temporary directory - Navigate to the parent directory of the referenced file
- Copy that entire directory to the target local directory
- The temporary directory is cleaned up automatically
Pushing (push):
- Clone the repo with
git clone --depth 1 <clone_url>into a temporary directory - Overwrite the skill directory in the clone with the local version
- Stage only the relevant changes:
git add <skill_directory_path> - Commit with message:
registry: updated <skill name> <what changed> - Push to remote
- The temporary directory is cleaned up automatically
Typed Dependencies
The requires field uses typed references to avoid ambiguity:
skill:name— references a skill in the registry catalogagent:name— references an agent in the registry catalogprompt:name— references a prompt in the registry catalog
When resolving dependencies: look up each reference in registry.yaml, fetch all dependencies first (recursively), then fetch the requested item.
Target Directories
By default, items are installed to the default directory from registry.yaml:
default_dirs:
skills:
- default: .claude/skills/
- global: ~/.claude/skills/
agents:
- default: .claude/agents/
- global: ~/.claude/agents/
prompts:
- default: .claude/commands/
- global: ~/.claude/commands/- If the user says "global" or "globally", use the
globaldirectory. - If the user specifies a custom path, use that path.
- Otherwise, use the
defaultdirectory.
Registry Repo Sync
The registry skill itself lives in <REGISTRY_SKILL_DIR> as a cloned git repo. When running add (which modifies registry.yaml), always:
git pullin the registry directory first to get latest- Make the changes
git add registry.yaml && git commit && git push
This keeps the catalog in sync across devices.
Example Filled Registry File
default_dirs:
skills:
- default: .claude/skills/
- global: ~/.claude/skills/
agents:
- default: .claude/agents/
- global: ~/.claude/agents/
prompts:
- default: .claude/prompts/
- global: ~/.claude/prompts/
registry:
skills:
- name: firecrawl
description: Scrape, crawl, and search websites using Firecrawl CLI
source: /Users/me/projects/tools/skills/firecrawl/SKILL.md
- name: meta-skill
description: Creates new Agent Skills following best practices
source: /Users/me/projects/tools/skills/meta-skill/SKILL.md
- name: diagram-kroki
description: Generate diagrams via Kroki HTTP API supporting 28+ languages
source: https://github.com/myorg/private-skills/blob/main/skills/diagram-kroki/SKILL.md
requires: [skill:firecrawl]
- name: green-screen-captions
description: Generate and burn AI-powered captions onto green screen videos
source: https://raw.githubusercontent.com/myorg/video-tools/main/skills/green-screen-captions/SKILL.md
requires: [agent:video-processor, prompt:caption-style]
agents:
- name: video-processor
description: Processes video files with ffmpeg and whisper transcription
source: /Users/me/projects/tools/agents/video-processor/AGENT.md
- name: code-reviewer
description: Reviews code for quality, security, and performance
source: https://github.com/myorg/agent-configs/blob/main/agents/code-reviewer/AGENT.md
prompts:
- name: caption-style
description: Style guide for generating video captions
source: /Users/me/projects/content/prompts/caption-style.md
- name: commit-message
description: Standardized commit message format for all projects
source: https://github.com/myorg/team-prompts/blob/main/prompts/commit-message.mdDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

