distill
Installation
SKILL.md
Distill
You're over-specifying. The artifact tells the reader how to format output instead of what to accomplish. That scaffolding was necessary for weaker models. It constrains stronger ones.
The Problem
When writing skills, prompts, or instructions, you default to showing exactly what the output should look like — filled-in example tables, prescribed column names, template formats. This feels helpful but it creates a ceiling. The model matches your template instead of thinking about what the specific problem needs.
The Test
For each instruction in the artifact, ask: is this intent or format?
| Intent (keep) | Format (cut) |
|---|---|
| Summarize the results in a table | Use these columns: Name, Status, Duration, Owner |
| Assessments should be opinionated | Acceptable values: "ready", "blocked", "needs work" |
| Group items by category | Categories: Infrastructure, Frontend, Backend, Testing |
| Commit your changes after each step | Run git add -A && git commit -m "step N: description" |