mcpField
S
skill-manager

skill-manager

github.com/petekpAgent workflows4845 installsUpdated 3d ago
Repository

About skill-manager

A command-line skill manager for maintaining a skill collection across Claude, Codex, and Agents runtimes. Its scripts report usage, detect overlap, check links, synchronize directories, and identify candidates for pruning.

Key features

  1. 01Audit skill ecosystem health
  2. 02Report skill usage frequency
  3. 03Detect duplicate and overlapping skills
  4. 04Check and sync runtime links
  5. 05Find candidates for pruning

Use cases

  1. 01Reviewing skills before removal
  2. 02Checking links after setup
  3. 03Finding overlap after installing skills

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/petekp/claude-code-setup --skill skill-manager

After installing, type/skill-managerin Claude Code to confirm it loaded.

Details

From the project README

Skill Manager

Unified tool for managing your skill ecosystem across Claude, Codex, and Agents runtimes.

Available Commands

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

When to Run Each Command

CommandWhen to Use
reportPeriodic full health check (weekly or monthly)
usageBefore pruning — see which skills are actually used
dupesAfter installing new skills — check for overlap
checkAfter setup.sh or when skills seem missing
syncAfter editing skills — verify everything is linked
updatePeriodically — check if npx-installed skills have newer versions
pruneWhen the skill list feels bloated — find removal candidates

How Usage Tracking Works

A PostToolUse hook in settings.json fires every time the Skill tool is used. It logs:

  • Skill name
  • Timestamp (UTC)
  • Project directory

Data is stored in ~/.claude/skill-usage.jsonl (one JSON object per line). The usage and prune commands read this data to generate reports.

How to Use This Skill

When the user asks about skill management, run the appropriate command and present the results. For general questions, run report for a full picture.

Interpreting Results
  • Check: Green means properly linked. Yellow means something unexpected. Red means broken.
  • Sync: Verifies all three runtimes (Claude, Codex, Agents) point to the repo's skills directory.
  • Dupes: Groups skills by prefix and checks keyword overlap in descriptions. High overlap (>40%) suggests consolidation.
  • Usage: Shows invocation counts and last-used dates. "Never used" skills are prune candidates.
  • Prune: Combines usage data with overlap analysis to suggest removals.
Archiving Skills

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/).

Comments

Markdown supported