Clarify one existing Skill

Locate project-local skills and inspect the names and descriptions of at most three candidates. Choose one used in this conversation, otherwise one with an unclear responsibility. Explain the choice briefly. Read only its SKILL.md and direct references; do not scan global skill collections. If none exists, report that.

Align its intended use, required inputs, output and stopping conditions. Check broad triggers, missing prerequisites, redundant reading and missing references. Deliver complete replacement passages without expanding its responsibility or running bundled scripts.

Include three positive and three negative trigger examples. Walk through one normal input and one missing-input case, labeling this as static inspection rather than an execution test. Every edit must have evidence; preserve the original when no clear benefit exists.

Execution contract:
Start directly. Do not ask me to approve a plan, choose files or fill in a template. Use only this project, this conversation and materials already provided; do not search unrelated projects or private history. Complete what the evidence supports and report missing inputs. If the task is inapplicable, explain why and stop without inventing a result.
Preserve existing files and uncommitted changes. Include complete proposed content in your reply; standalone artifacts may be saved under a new, unused filename. Do not install dependencies, change the environment, commit, push or deploy. Respect access and permission limits and report blocked work. Check your result once, deliver it and stop without asking whether to continue.