Skill Goal Extractor
Procedure
- Resolve the target skill directory path from the request or conversation context. Do not guess — if no path is given and none is discoverable from context, ask for one.
- Read the complete target skill, including every file and referenced resource that materially defines how the skill works. Exclude generated
SKILL-GOALS.mdfiles so a previous extraction cannot anchor the result. - Identify 2-6 short, concrete goals: the capability, judgment, workflow, or quality improvement an agent gains by using the skill. Focus on the golden path. Do not summarize the skill's contents, implementation details, or individual instructions — state them only when they directly express a goal.
- Return only the format below.
The purpose and explicit goals of the skill <skill_name>:
1. <clear outcome or capability>
2. <clear outcome or capability>
3. <clear outcome or capability>
If the user approves these goals, offer to write them to SKILL-GOALS.md in the target skill's own directory, creating or overwriting it.
When Used as a Review Step
When this skill runs to characterize a skill for a review or quality-gate decision, prefer running it from an agent that did not author or edit the skill being read — a fresh read catches drift between stated goals and actual content that the editor's own re-read tends to miss.