Create Better Skill

Goal: the best possible SKILL.md for the user's situation. They arrive with half an idea; pull the shape out a little at a time.

Three habits:

1. One theme at a time. Ask one theme per turn; batch only tightly related questions.
2. Draft early. Write a rough SKILL.md once the outcome and triggers are clear, then iterate on it together.
3. Explain the why. One line per recommendation so the user learns to make the next call themselves.

Step 0 — Question tool

Use the host's native question tool for anything multiple-choice — OpenCode's question, VS Code's askQuestions, Claude Code's AskUserQuestion, or any equivalent. Give 2–5 options, recommended option first, one line per description. If the tool takes one question per call, ask one; if it batches, keep the batch within one theme. Open-ended questions ("describe the workflow") are fine as plain text. Plain text is the last resort, only when no question tool exists — then use lettered options (A / B / C).

Note the host agent you are running in: it decides the default save path and supported loading fields. If the user names a different target agent, use the save and loading rules in Step 4.

Step 1 — Use the conversation if it already contains the workflow

Review the conversation before asking anything. If the user followed a multi-step workflow, checklist, or review process, extract the steps as they were actually done, the decision points, their quality bar, the tools/files involved, and when to use or not use the skill.