Sync Skills
Scans local Claude Code skills, genericizes them, and registers them into a shared skills repo.
Fonctionne avec configuration
Ce que fait
Scans local projects for .claude/skills/*/SKILL.md files, strips personal/project-specific references (names, domains, companies), and registers the genericized skill into the qa-aman/claude-skills repo's role-based catalog via init_skill.py and skills.json. Triggers on phrasings like 'sync skills', 'fetch skills', or 'import skills from projects'. Only fully functions when the working directory is a complete clone of that specific repo, since it depends on repo-root scripts, skills.json, and README tables that are not included if you copy only the skill folder.
Rapport de test
Real friction: the skill's own body calls scripts/init_skill.py, scripts/validate_skill.py, and skills.json at the repo root, none of which survive a plain `cp -r` of just the skill folder — you must keep the whole qa-aman/claude-skills repo as your working directory for this to do anything beyond producing loose genericized text.
Testé le: 2026-07-15 · Claude Code 2.x (agent harness)
Installation
git clone https://github.com/qa-aman/claude-skills.git mkdir -p ~/.claude/skills cp -r claude-skills/.claude/skills/sync-skills ~/.claude/skills/sync-skills
Commandes et exemples de prompts
/sync-skillsScans local Claude Code skills, genericizes them, and registers them into a shared skills repo.
Les skills se déclenchent sur des demandes en langage courant — aucune commande à retenir. Après installation, des prompts comme ceux-ci l'activent (en anglais) :
Pull the Claude skills from my other projects into this shared repoCan you fetch the local skills in ~/Documents/Projects and register them here?Genericize this project skill and strip out the personal references