tool-sp-maintain-skillslisted

# Maintain Skills ## Purpose Guide the agent through a short maintenance workflow so project skills stay aligned with current repo behavior, branch changes, and skill-authoring standards instead of drifting into stale commands, stale examples, or missing coverage. Keep project guidance simple by giving each rule one clear home when maintenance reveals duplication or misplaced detail. ## When to use this skill - Repo commands, package-manager choices, workflows, or folder structure changed. - A branch introduced new domains, libraries, or tooling that the current skills do not mention. - Existing skills may still describe old commands, old package managers, or renamed features. - The skill catalog changed and the top-level routing may need a corresponding refresh. ## Scope boundaries This tool maintains the **existing skill catalog**: what drifted, what duplicates what, which skill should own a rule. It is a catalog-level pass, not a single-file edit and not an authoring guide. - `tool-sp-create-skill` — when the change genuinely needs a *new* skill rather than an update to an existing one. Deciding between the two is this tool's job; executing the creation is that one's. - `tool-sp-make-skill-shareable` — when the question is one skill's portability rather than the catalog's freshness. - `tool-sp-maintain-agents-instructions` — when the drift is in `AGENTS.md`, `GEMINI.md`, or `.claude/CLAUDE.md` rather than in the skills. The two hand off to each other: renaming