maintain-skillslisted

# Maintain Skills Keep every skill grounded in the code it describes. The standard: **a skill that cites a dead path, dead symbol, or stale command is worse than no skill** — it makes a cheap session confidently wrong. ## Which library are you maintaining? Work out the target before editing anything — they have different rules. | Target | Lives in | Rule | | --- | --- | --- | | **Shared skills** (this plugin) | the `adora-skills` repo, `skills/<name>/SKILL.md` | Must stay **project-agnostic**. No repo-specific paths, baselines, bundle ids, or module names. Teach Claude to *read* the specifics from the repo it is in. | | **Project skills** | `<project>/.claude/skills/` | May be as concrete as you like — cite real paths, real symbols, real baselines. Concreteness is the point. | | **Third-party skills** | other installed plugins' `skills/` | Read-only. Never edit; if one is wrong, note it and work around it. | Plugin skills are installed as a read-only bundle. To change one, edit it in the `adora-skills` repo, push, and run `/plugin marketplace update adora-skills`. Editing the installed copy does nothing durable. **The promotion test.** A project skill earns promotion into the shared plugin only when it is useful in a *second* project without rewriting its body. If generalizing it would strip out the specifics that make it good, it belongs in the project, not the plugin. ## The grounding standard Every skill must satisfy: 1. Every file path it cites exists (in the rep