grill-skill

# Grill Skill Interview the user to design a skill's eval, then loop run → measure → improve until it ships. Requires `caliper` (`pipx install caliper-eval` if missing). Commands, spec skeleton, and expect/assert guidance: [REFERENCE.md](REFERENCE.md). ## Entry point `/grill-skill [path]` — optional path to a `SKILL.md`. - **Path given** — use it. - **No path** — look for `SKILL.md` in the cwd; if found, confirm before proceeding, else ask where it is. ## Phase 1 — Understand Read the `SKILL.md`. Summarize what it does, when it triggers, and what a successful run looks like. Ask the user to confirm your reading. **Wait for confirmation before continuing.** ## Phase 2 — Detect eval mode Look for `*.eval.yaml` beside the `SKILL.md` (try `<dir-name>.eval.yaml` first). - **None** → New eval. **Found** → Gap-fill. Interview one question at a time and wait for each answer. Never invent the user's answers or write the spec before interviewing. ### New eval — three tasks Elicit three tasks, one question at a time: 1. **Happy path** — the most common successful use. What did the agent do, and what would confirm it worked? 2. **Edge case** — a tricky-but-valid input that might trip the raw agent. 3. **Adversarial** — what the skill should refuse or avoid. Turn each answer into a task: a realistic `prompt`, an observable `expect`, and an `assert` when the outcome is checkable (see [REFERENCE.md](REFERENCE.md)). Show the proposed YAML and confirm before writing. Write the ...