Reflect

Analyze the current session and turn what was learned into concrete edits to the skill's authored source package. A skill is the whole folder, not only SKILL.md.

Workflow

1. Identify the Skill

Auto-detect which skills were used by scanning the conversation for:

• <command-name>/skill-name</command-name> tags
• Reads of a skill's source file (a SKILL.md or <skill-name>.md in a skills directory)

If a skill name was provided as an argument, use that directly.

If multiple skills were detected, ask which to analyze. If none were detected and no argument was given, list the available skills and ask.

An installed skill's source repository is recorded in the skills lockfile: ~/.agents/.skill-lock.json for global installs, <project-root>/skills-lock.json for project installs. Use it to find the skill's source package in the matching local checkout before proposing or applying edits (different skills may live in different repositories).