update-skilllisted

# Update Skill Update an existing skill from explicit conversation feedback. Read the target skill before editing, identify the smallest canonical file that owns the rule, apply the change, and validate links and metadata afterwards. ## Use Call this skill only after feedback or a correction is concrete enough to store: ``` /update-skill <skill-name> ``` Do not update a skill merely because an output was generated. The conversation must contain a durable preference, rule, boundary, or workflow correction. ## Writer routing When the target is `writer`, first resolve the active skills root from the runtime configuration and read `<skills-root>/writer/MAINTENANCE.md`. Do not hardcode a user-specific absolute path or assume `~/.claude/skills`. Classify the feedback as a shared rule, primary type, type add-on, lens, source object, domain, format, format integration, reviewer, check, or routing rule. Edit the corresponding canonical module. Update `writer/SKILL.md` only when the feedback changes module selection or a hard boundary. If a feedback item says that a repository implementation must not be treated as a paper fact, update `writer/references/objects/paper.md` and/or `objects/repository.md`, not a generic explanation paragraph. If it changes module selection, reviewer activation, format precedence, or compatibility behavior, update `writer/SKILL.md` only for that routing contract. Keep one rule in one canonical location. Do not create a compatibility wrapper, copy a