Skill Cleaner

Use this when trimming skill prompt budget, finding duplicate skills, auditing enabled/disabled skill roots, or deciding which skills/plugins to remove.

Workflow

1. Run the analyzer from this skill directory or repo root:

node --experimental-strip-types skills/skill-cleaner/scripts/skill-cleaner.ts --months 3

Useful variants:

node --experimental-strip-types skills/skill-cleaner/scripts/skill-cleaner.ts --no-logs
node --experimental-strip-types skills/skill-cleaner/scripts/skill-cleaner.ts --no-live --no-logs
node --experimental-strip-types skills/skill-cleaner/scripts/skill-cleaner.ts --months 6 --max-log-mb 800 --deep-logs
node --experimental-strip-types skills/skill-cleaner/scripts/skill-cleaner.ts --context-tokens 272000 --budget-percent 2 --no-logs
node --experimental-strip-types skills/skill-cleaner/scripts/skill-cleaner.ts --root ~/Dropbox/boxd/skills --no-logs
node --experimental-strip-types skills/skill-cleaner/scripts/skill-cleaner.ts --root ~/.agents/skills --root-only --no-logs

2. Read the report in this order:

• Skill Budget: live Codex inventory, 2% budget, budgeted usage, and full-description pressure.
• Description candidates: long descriptions where relaxed grammar saves prompt budget.
• Duplicates: same skill name or near-identical description/body across Codex, plugin cache, repo siblings, and personal skill roots.
• Unused candidates: no recent user mention or actual SKILL.md read in recent Codex/OpenClaw logs.
• Root summary: where skills came from and whether config marks them disabled.

3. Before deleting or editing:

• Verify the kept copy exists and is loaded.
• Prefer deleting repo-local or agent-scripts duplicates when Codex built-ins cover them.
• Keep repo-local OpenClaw maintainer skills when they encode repo policy or live operations.
• Preserve trigger nouns in descriptions: product, tool, action, object.

Analyzer Notes