skillifylisted

# Skillify — capture a repeated workflow as a skill You are going to interview the user, distill what they keep doing into a SKILL.md, and write it to the right place on disk. The output lives at `~/.geny/skills/<id>/SKILL.md` (user-scope) or `<project>/.geny/skills/<id>/SKILL.md` (project-scope) depending on how broadly the workflow applies. ## Step 1 — Sniff the context Before asking anything, glance at the recent conversation. The workflow being captured is *probably* something the user just did (or just asked to redo). If you can already infer the shape, lead with a one-sentence summary and ask the user to confirm. ```! # Where would the project-scope skill go? [ -d .geny/skills ] || mkdir -p .geny/skills echo ".geny/skills/ ready under $(pwd)" ``` ## Step 2 — Interview Ask, in this order, one question at a time. Wait for an answer before the next question. **Don't ask all at once** — operators get overwhelmed and answer poorly. 1. **What should this skill do, in one sentence?** This becomes the `description` frontmatter field. Push back gently if the answer is vague — "produces a report" is too broad; "produces a markdown summary of changed files between two git refs" is right. 2. **What's a short id?** kebab-case, ≤ 32 chars, must match `[a-z0-9][a-z0-9_-]*`. Suggest one based on the description if the user shrugs. 3. **What arguments does it take?** Ask for argument names and a one-line hint. If none, that's fine — many skills are paramete