← ClaudeAtlas

skill-refinerlisted

Curation pass over the robium skill catalog: measure bloat against token budgets, find cross-skill duplication and overlap worth merging, sweep dated version/status facts for staleness, and review which skills never fire so their trigger surface or existence gets questioned. Use when: 'refine the skills', 'check skill bloat', 'are the skills bloated', 'prune the skills', 'dedupe the skills', 'stale skill facts', at the end of a skill-updater absorption run (skill-updater routes here), or periodically (~monthly or after every 2-3 app builds). Report-first: produces a findings report, then applies only user-approved edits under skill-author's rules. Developer workflow — runs in the robium source checkout. Not for: absorbing session learnings (skill-updater) or authoring new skills (skill-author).
robium-ai/robium-plugin · ★ 0 · AI & Automation · score 73
Install: claude install-skill robium-ai/robium-plugin
# skill-refiner The catalog's weeding pass. Absorption (skill-updater, skill-author hardening) makes the catalog *grow* by default; this skill is the counterweight that keeps it lean: it measures bloat instead of feeling it, hunts duplication across skills rather than within one, re-verifies dated facts before they rot, and asks the question no addition-focused session asks — "which of these skills earned its context cost?" The research this skill distills from (MUSE-Autoskill's merge-on-overlap + prune-on-disuse, Claude Code's least-invoked-first description dropping, Anthropic's "smallest set of high-signal tokens" principle) all converges on the same posture: a knowledge base that only ever adds is degrading, just slowly. ## When to use this skill - End of a skill-updater absorption run — skill-updater invokes a scoped refine over the skills it just touched (its final step routes here). - Periodically over the whole catalog: roughly monthly, or after every 2-3 app builds, or when the skills list feels heavy — 'refine the skills', 'check skill bloat', 'prune the skills'. - Before a plugin release/tag, as the release-readiness sweep. - When a specific smell appears: two skills answering the same question, a skill that never fires, a version fact that reads stale. - Cross-references — go to the sibling skill instead when the task is: - Folding a session's learnings into skills → `skill-updater` (it feeds this skill, not the reverse). - Writing a new skill,