skill-registry-sync
Skill5 starsChanged 8 months agoMITView on GitHub
Synchronise README.md references with installed skills from .skill-lock.json. Use when updating external skill registry references in documentation, ensuring all skill sources are properly documented, or maintaining accurate reference lists.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- charm-vhsSkill
- cloud-foundation-fabricSkill
- d2Skill
- duckdbSkill
- github-profile-architectSkill
- jqSkill
- opencode-devSkill
- playwright-cliSkill
- skill-crawlerSkill
- tech-writerSkill
- terminal-ui-engineerSkill
- terraformSkill
- worktrunkSkill
- writingSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 58
After installing new skills from external repositories, update README references:
- Distinctive: line 160
Always sync after installing skills from new repositories to keep documentation accurate:
- Distinctive: line 178
If you have multiple environments or configurations:
- Distinctive: line 203
If no external skills are installed, the section will remain unchanged.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Registry Sync
Synchronise external skill repository references in README.md based on installed skills from .skill-lock.json.
Quick Start
# Sync references using default lock file path
npx opencode -s skill-registry-sync sync
# Sync with custom lock file path
npx opencode -s skill-registry-sync sync --lock-file /path/to/.skill-lock.json
# Sync with custom README path
npx opencode -s skill-registry-sync sync --readme /path/to/README.mdHow It Works
This skill:
- Reads the
.skill-lock.jsonfile (or path you specify) - Extracts all unique
sourceUrlvalues from installed skills - Updates the "Other Skill Registries" section in README.md
- Adds any missing repository URLs as
npx skills addcommands
Commands
sync
Synchronise README.md with installed skills from lock file.
# Default usage - uses ~/.agents/.skill-lock.json and ./README.md
skill-registry-sync sync
# Custom lock file path
skill-registry-sync sync --lock-file /custom/path/.skill-lock.json
# Custom README path
skill-registry-sync sync --readme /custom/path/README.md
# Both custom paths
skill-registry-sync sync --lock-file /custom/lock.json --readme /docs/README.mdExamples
Example 1: Basic Sync
After installing new skills from external repositories, update README references:
# Install skills from various repositories
npx skills add https://github.com/googleworkspace/cli
npx skills add https://github.com/google-gemini/gemini-skills
# Sync references to README
skill-registry-sync syncExample 2: Manual Lock File Analysis
Extract unique source URLs manually using jq:
# Extract all unique source URLs
cat ~/.agents/.skill-lock.json | jq -r '.skills[].sourceUrl' | sort -u
# Count skills per source
cat ~/.agents/.skill-lock.json | jq -r '.skills[].source' | sort | uniq -c
# Get skills from specific source
cat ~/.agents/.skill-lock.json | jq -r '.skills | to_entries[] | select(.value.source == "googleworkspace/cli") | .key'Implementation
Using jq to Parse Lock File
The skill uses the jq-tooling skill to parse .skill-lock.json:
# Extract unique source URLs
cat ~/.agents/.skill-lock.json | jq -r '.skills[].sourceUrl' | sort -u
# Output format:
# https://github.com/googleworkspace/cli.git
# https://github.com/google-gemini/gemini-skills.git
# https://github.com/google-gemini/gemini-cli.git
# https://github.com/google-labs-code/stitch-skills.git
# https://github.com/vercel-labs/skills.gitREADME.md Section Format
The skill updates the "Other Skill Registries" section:
### Other Skill Registries
Expand your agent's toolkit with these supplementary skill collections:
- 📦 `npx skills add https://github.com/google-gemini/gemini-skills`
- ⚛️ `npx skills add https://github.com/google-labs-code/stitch-skills --skill react:components`
- 🛠️ `npx skills add https://github.com/google-gemini/gemini-cli`
- 🏢 `npx skills add https://github.com/googleworkspace/cli`
- 📦 `npx skills add https://github.com/vercel-labs/skills`Common Workflows
Workflow 1: After Installing New Skills
# 1. Install new skills from external repo
npx skills add https://github.com/example/new-skills-repo
# 2. Sync references to README
skill-registry-sync sync
# 3. Review changes
git diff README.md
# 4. Commit updates
git add README.md && git commit -m "docs: add new skill registry reference"Workflow 2: Audit External Dependencies
# List all external skill sources
cat ~/.agents/.skill-lock.json | jq -r '.skills[].sourceUrl' | sort -u
# Identify which skills come from external repos (not local)
cat ~/.agents/.skill-lock.json | jq -r '.skills | to_entries[] | select(.value.source != "benjaminwestern/google-engineer-skills") | [.key, .value.source] | @tsv'Workflow 3: Generate Custom Reference Documentation
# Create a custom markdown file with all skill sources
cat ~/.agents/.skill-lock.json | jq -r '
[.skills[].sourceUrl] | unique |
"## External Skill Registries\n\n" +
(map("- `npx skills add " + . | rtrimstr(".git") + "`") | join("\n"))
' > SKILL_SOURCES.mdTips and Best Practices
Run After Skill Installation
Always sync after installing skills from new repositories to keep documentation accurate:
npx skills add https://github.com/org/new-skills
skill-registry-sync syncVerify Before Committing
Review changes before committing:
skill-registry-sync sync
git diff README.mdHandle Multiple Lock Files
If you have multiple environments or configurations:
# Production environment
skill-registry-sync sync --lock-file ~/.agents/prod/.skill-lock.json --readme README.prod.md
# Development environment
skill-registry-sync sync --lock-file ~/.agents/dev/.skill-lock.json --readme README.dev.mdIgnore Local Skills
The skill automatically filters out local skills (from the current repository) and only includes external registries in the references section.
Troubleshooting
Lock file not found
# Specify correct path
skill-registry-sync sync --lock-file /correct/path/.skill-lock.jsonNo changes detected
If no external skills are installed, the section will remain unchanged. Install some external skills first:
npx skills add https://github.com/googleworkspace/cli
skill-registry-sync syncDuplicate entries
The skill automatically deduplicates URLs. If you see duplicates, ensure you're using the latest version.
Related Skills
| Skill | Purpose |
jq-tooling | Parse and query JSON data including .skill-lock.json |
playwright-cli | Crawl documentation for creating new skills |
skill-crawler | Convert crawled docs into opencode skills |
Resources
- Skills CLI: https://github.com/vercel-labs/skills
- Skills Standard: https://agentskills.io
- jq Documentation: https://jqlang.github.io/jq/manual/
Does 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.

