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/).
development
Draft short, plainspoken notes in the author's voice that help reviewers understand non-obvious choices, boundaries, and preserved behavior in the author's own pull request or local diff. Use when the user asks to self-review, annotate, or add reviewer context to their PR or changes. Draft locally when no PR exists, and post approved notes as one GitHub review when a PR does exist. Do not use for reviewing someone else's PR, writing code comments, explaining code generally, or drafting a PR description. Never post without explicit approval.
tools
Design and build pure-CSS (zero-JavaScript) Tailwind CSS v4 plugins of unusual depth and craft. Use when the user wants to create, architect, or refine a Tailwind utility plugin or CSS effect — e.g. "make a tailwind plugin", "build a tw-* plugin", "a CSS-only shimmer/fade/glow/grain/noise utility", "tailwind v4 @utility", "package this effect as a plugin", or wants an effect with surprising visual depth (gradients, masks, filters, SVG filter tricks, scroll-driven animation). Pairs deep CSS/SVG technique research with a bespoke tuning workbench for dialing the effect in. Inspired by tw-fade and tw-shimmer.
content-media
Create clear, polished before-and-after screenshots for a GitHub pull request. Use when a UI change needs visual proof: capture matching states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.
testing
--- name: latent-potential description: First-principles, team-of-experts assessment of a software project that surfaces latent potential; underexploited assets, a sharper north star, missing high-leverage capabilities, better framing and messaging. Produces a prioritized, evidence-grounded report with cheap probes, a reframe candidate, a stop-doing list, and an honest skeptic's case. Use whenever the user wants fresh eyes on a project they have built: "what am I sitting on", "what could this be