skills/skill-manager/SKILL.md
Manage, audit, and maintain your skill ecosystem. Use when the user asks to "check my skills", "audit skills", "find duplicate skills", "which skills am I using", "prune unused skills", "are my skills synced", "check for skill updates", "skill report", "skill health", or mentions skill maintenance, cleanup, or organization.
npx skillsauth add petekp/claude-skills skill-managerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Unified tool for managing your skill ecosystem across Claude, Codex, and Agents runtimes.
Run these via the skill-manager.sh script in the repo's scripts/ directory:
# Full audit — runs all checks in one pass
~/.claude/scripts/skill-manager.sh report
# Individual commands
~/.claude/scripts/skill-manager.sh usage # Show skill usage frequency
~/.claude/scripts/skill-manager.sh usage --top 10 # Top 10 most-used skills
~/.claude/scripts/skill-manager.sh dupes # Detect redundant/duplicate skills
~/.claude/scripts/skill-manager.sh check # Verify availability for Claude/Codex/Agents
~/.claude/scripts/skill-manager.sh sync # Validate repo sync status
~/.claude/scripts/skill-manager.sh update # Check for npx skill updates
~/.claude/scripts/skill-manager.sh prune # List candidates for removal
| Command | When to Use |
|----------|-------------|
| report | Periodic full health check (weekly or monthly) |
| usage | Before pruning — see which skills are actually used |
| dupes | After installing new skills — check for overlap |
| check | After setup.sh or when skills seem missing |
| sync | After editing skills — verify everything is linked |
| update | Periodically — check if npx-installed skills have newer versions |
| prune | When the skill list feels bloated — find removal candidates |
A PostToolUse hook in settings.json fires every time the Skill tool is used. It logs:
Data is stored in ~/.claude/skill-usage.jsonl (one JSON object per line). The usage and prune commands read this data to generate reports.
When the user asks about skill management, run the appropriate command and present the results. For general questions, run report for a full picture.
To archive a skill (remove from active use but keep for reference):
mv skills/<name> ~/.claude/skills-archive/
This removes it from all three runtimes (since they symlink to the repo's skills/).
tools
Comprehensively manually test the Circuit plugin's user-facing surface in either Claude Code or Codex. Use this skill whenever the user asks to "manually test Circuit", "QA the Circuit plugin", "exercise the Circuit surface", "run the Circuit checklist", "smoke test Circuit", "find regressions in Circuit", "test the Claude Circuit plugin", "test the Codex Circuit plugin", or when preparing a Circuit release for marketplace publication. Argument is the host package to test — `claude` or `codex`. Produces a Markdown report with per-command pass/fail, exploratory findings ranked by severity, run-folder evidence links, and a concise terminal summary. Use even if the user does not say the word "test" — phrases like "go through every Circuit command" or "make sure Circuit still works end-to-end" should also trigger.
development
Turn the prompt supplied with this skill into a concise, auditable Codex Goal or explain why a Goal is not the right fit. Use when the user asks to draft, formulate, rewrite, tighten, or create a `/goal` from a plain-language task, especially for multi-step work that needs a durable objective, evidence-based completion, constraints, iteration policy, and a default adversarial review loop.
development
Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use this whenever the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", "fill me in", or otherwise signals they have been away and want to get back up to speed quickly. Built for someone steering several agent-driven projects at once who does not read the code closely but needs to grasp the core ideas, the choices made, and the open decisions well enough to steer. Trigger even if they do not use these exact words: any request to get oriented on recent progress should use this skill.
tools
Expert Unix and macOS systems engineer for shell scripting, system administration, command-line tools, launchd, Homebrew, networking, and low-level system tasks. Use when the user asks about Unix commands, shell scripts, macOS system configuration, process management, or troubleshooting system issues.