← ClaudeAtlas

skill-librarianlisted

Audit, refresh, and maintain a library of existing skills so it stays lean, non-duplicated, and written for current models. Use whenever the user wants to review, clean up, consolidate, merge, dedupe, refresh, or "update all my skills", asks whether two skills overlap, wants to know which skill owns a piece of guidance, asks why an installed skill behaves differently from the repo, or is about to add a new skill to a library that already has many. Also use before creating a new skill, to check that its job isn't already owned. Do NOT trigger for auditing project documents (use drift-check), for writing one brand-new skill's body from scratch, or for verifying an AI-generated plan (use reality-check).
scoobydrew83/skills · ★ 0 · AI & Automation · score 76
Install: claude install-skill scoobydrew83/skills
# Skill Librarian This skill is about the library as a whole: which skills should exist, where each piece of guidance lives, and whether each skill is still written for the model that reads it. Structural rules for this repository (coordination header, Next-steps line, phases, renames, tombstones) live in `CONVENTIONS.md` and `CONTRIBUTING.md`; follow them rather than restating them here. For drafting and evaluating a single skill in depth, Anthropic's skill-creator skill is the companion tool. ## The goal A library where every piece of guidance has exactly one home, every skill has a job no other skill claims, installed copies match the source, and instructions are as light as the current model allows. Done means: an inventory, a decision for every overlap, drafted edits for skills the user owns, passing repository tests, and a short trigger test for each change. ## Principles ### 1. One home per piece of information Each fact, rule, or procedure lives in one skill. Anything else that needs it links to that skill by name instead of repeating it. Why: a duplicated rule drifts. When one copy is updated and the other isn't, the model sees two conflicting instructions and has to guess which is current. - **Across skills.** Before adding guidance, ask whether it warrants its own skill or belongs inside an existing one. If another skill needs it, link. - **Within a skill.** Say each rule once, where it matters most, not in the description, the body, and an example. - A