Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →superset-sh/ticket-format
Use when creating, drafting, or grooming a Linear or Superset ticket in this repo. Defines the canonical three-section structure.
Passed 18 of 22 test cases with the skill, and 6 of 22 without it.
and 16 more in the full report
14 fixed4 passed either way2 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Create a ticket because the checkout button is unclickable on mobile Safari. A designer suggested adding CSS z-index 9999 and target-densityDpi settings. Write the ticket's Context section following team guidelines.
| Checked | Without skill | With skill |
|---|---|---|
| The context section describes the unclickable mobile Safari button issue. | Passed | Passed |
| The context section avoids specifying CSS z-index implementation details. | Missed | Passed |
The instructions your model reads when the skill loads.
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 incidentstest cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.