Capture the current session's repeatable process into a reusable SKILL.md skill file. Use when the user wants to create a skill, save a workflow as a skill, turn a process into a reusable skill, or mentions "skillify", "create skill", "make a skill", "save as skill", "capture workflow", "turn this into a skill", "new skill", or wants to automate a repeatable process they just performed.
Capture this session's repeatable process into a reusable SKILL.md skill file. Call at the end of the process you want to capture, optionally with a description.
$description: (Optional) Description of the process you want to capture as a skill.Create a well-structured, reusable SKILL.md file that captures a repeatable process from the current session so it can be invoked again later.
Before asking any questions, analyze the conversation to identify:
Success criteria: You have a clear mental model of the process, its steps, inputs, outputs, and success criteria.
Use AskUserQuestion for ALL questions. Never ask questions via plain text. For each round, iterate as much as needed until the user is happy. The user always has a freeform "Other" option to type edits or feedback -- do NOT add your own "Needs tweaking" option. Just offer the substantive choices.
.claude/skills/<name>/SKILL.md) -- for workflows specific to this project~/.claude/skills/<name>/SKILL.md) -- follows you across all reposFor each major step, if it's not glaringly obvious, ask:
You may do multiple rounds of AskUserQuestion here, one round per step, especially if there are more than 3 steps or many clarification questions.
IMPORTANT: Pay special attention to places where the user corrected you during the session, to help inform your design.
Stop interviewing once you have enough information. Don't over-ask for simple processes!
Success criteria: You have all the information needed to write the SKILL.md file and the user has confirmed the design.
Create the skill directory and file at the location the user chose in Round 2. Use this format:
---