← ClaudeAtlas

skill-repo-curatorlisted

Maintain a public Agent Skills repository. Use when updating skill catalogs, validating SKILL.md files, preparing a release, deprecating skills, reviewing install commands, checking README consistency, or keeping a skills repo ready for npx skills installation.
stark-ai-de/agent-skills · ★ 5 · AI & Automation · score 77
Install: claude install-skill stark-ai-de/agent-skills
# Skill Repo Curator ## Goal Keep a public Agent Skills repository coherent, installable, safe, and ready for users who install skills through `npx skills`. ## When to use - The user asks to maintain or release a skills repository. - The README catalog may not match the `skills/` tree. - Validation, deprecation, publishing, or install commands need review. ## When not to use - The user wants to write a single skill; use `skill-authoring-review`. - The user wants install help only; use `skill-installation-support`. - The repository is not a skills repository and needs a general audit; use `repo-health-audit`. ## Inputs - `skills/**/SKILL.md` - `README.md`, `CHANGELOG.md`, `CONTRIBUTING.md`, `SECURITY.md`, and `LICENSE` - `package.json`, validation scripts, and CI workflows - Output from `npm run validate`, `npm run list`, and the local `npx skills` discovery command. ## Inputs to inspect - Inspect the skill tree, catalog docs, validation scripts, ignored local helper installs, and install smoke-test output. - Check that upstream helper skills are installed project-locally rather than vendored into the public catalog. ## Process 1. Inspect the skill tree and top-level repository files. 2. Run the local validation and listing commands when possible. 3. Compare README catalog entries against discovered skills. 4. Check install commands for `<github-owner>/<repo>` placeholders or final repository coordinates. 5. Review changelog and release checklist when preparing a r