Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when creating, drafting, or grooming a Linear or Superset ticket in this repo. Defines the canonical three-section structure.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | -30% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -43% | 0% |
| case-04 | ✗→✓ | ▲ Improved | -60% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -46% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -32% | 0% |
2–4 sentences. What's broken or wanted, and why. Outcome-focused, not solution-focused.
Where the ticket came from. Omit section if none.
| Source | Who | Link | Date | |--------|-----|------|------| | Slack #feedback | @alice | thread | 2026-05-10 |
Agent-groomed. Leave empty if you don't have codebase context — a later grooming pass will fill it in. When you do fill it in, use these sub-headings and skip what doesn't apply:
### Files — path:line + why relevant### Approach — one paragraph### Related code — similar patterns in the repo### Gotchas — constraints, prior incidentsOther measured skills in the registry, with their headline benchmark lift.