Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
steipete avatar

Skill Cleaner

  • 433 installs
  • 6.5k repo stars
  • Updated August 3, 2026
  • steipete/agent-scripts

skill-cleaner is an agent skill that audits Codex and OpenClaw skill inventories for duplicates, unused skills, and prompt-budget costs for developers trimming overloaded agent skill directories.

About

skill-cleaner is an agent maintenance skill from steipete/agent-scripts that audits Codex and OpenClaw skill roots without deleting files automatically. Run node --experimental-strip-types skills/skill-cleaner/scripts/skill-cleaner.ts --months 3 to report loaded roots, duplicate SKILL.md names, unused candidates from history logs, and description candidates that waste prompt budget. The analyzer realpath-dedupes symlinked roots, scans ~/.codex/history and session logs for heuristic usage evidence, and suggests deletion priorities across system, plugin, and personal skill copies. Developers reach for skill-cleaner when skill lists bloat context, duplicate names collide, or the 2% Codex skills budget pressure grows. Recommendations only—manual review required before removal.

  • skill-cleaner

Skill Cleaner by the numbers

  • 433 all-time installs (skills.sh)
  • +12 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #970 of 4,348 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/steipete/agent-scripts --skill skill-cleaner

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs433
repo stars6.5k
Last updatedAugust 3, 2026
Repositorysteipete/agent-scripts

How do you audit duplicate agent skills and prompt budget?

Use skill-cleaner for development tasks

Who is it for?

Developers maintaining large Codex or OpenClaw skill directories who need data-driven duplicate and unused-skill triage.

Skip if: Greenfield projects with few skills, automatic skill deletion without review, or teams not using Codex or OpenClaw skill roots.

When should I use this skill?

User wants to trim skill prompt budget, find duplicate skills, audit enabled skill roots, or decide which plugins or SKILL.md files to remove.

What you get

Skill budget report, duplicate and unused candidate lists, description compression suggestions, and deletion priority recommendations.

  • Skill budget audit report
  • Duplicate and unused candidate list
  • Description trimming recommendations

By the numbers

  • Default analyzer window uses --months 3 flag
  • Reports Codex 2% skills budget and description candidates for prompt savings

Files

SKILL.mdMarkdownGitHub ↗

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

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

  • By default, codex debug prompt-input supplies the exact model-visible skill list, order, names, and aliased paths. --no-live forces the broader filesystem fallback.
  • The broad filesystem scan remains for duplicate, disabled, and archived-cache diagnostics; it is not treated as the loaded inventory.
  • The script mirrors Codex's model-visible line shape: - name: description (file: path).
  • It applies Codex-like frontmatter rules: YAML frontmatter only, default name from parent dir, single-line sanitized name and description.
  • It follows Codex core-skills/src/render.rs: 2% of raw context_window, token cost ceil(utf8_bytes / 4), then full descriptions -> equal description truncation -> omitted minimum lines. Alias-table line cost is included.
  • It reads ~/.codex/models_cache.json for GPT-5.5 context_window; fallback is 272,000 tokens and 2%.
  • It scans only normal Codex/plugin/repo skill roots by default. Extra folders such as Dropbox archives are included only with --root <path>.
  • It realpath-dedupes roots, so symlinked roots such as ~/.codex/skills/agent-scripts -> ~/Projects/agent-scripts/skills do not create false duplicates.
  • For duplicate names, it reports description/body similarity and suggests deletion candidates only when bodies are near copies. Keep priority defaults to direct Codex system skills, then direct Codex skills, then plugin skills, then personal/repo copies.
  • It scans ~/.codex/history.jsonl and recent ~/.codex/sessions/**/*.jsonl by default. Add --deep-logs for archived sessions and common OpenClaw/Clawd log folders.
  • Usage evidence is heuristic: user $skill/use skill mentions and paths observed in tool-call arguments.

Output Policy

  • Suggest first; edit only when the user asks.
  • If asked to apply cleanup, make small grouped commits: descriptions, deletes, config disables.
  • Do not delete ignored/untracked skill dirs without naming the destination or confirming they are disposable.

Related skills

How it compares

Use skill-cleaner over manual folder browsing when Codex or OpenClaw skill roots symlink across repos and need usage-aware duplicate detection.

FAQ

Does skill-cleaner delete unused agent skills automatically?

skill-cleaner only analyzes and recommends; it does not delete files. Run skill-cleaner.ts, review duplicate and unused candidate reports, then remove skills manually after confirming bodies and usage evidence.

How do you run the skill-cleaner analyzer?

skill-cleaner runs via node --experimental-strip-types skills/skill-cleaner/scripts/skill-cleaner.ts --months 3 from the agent-scripts repo root, scanning Codex and plugin skill roots plus history logs.

Backend & APIsbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.