ticket-format
The ticket-format skill provides a standardized three-section template for creating Linear or Superset tickets in the superset-sh/superset repository. Use it when drafting or grooming tickets to ensure consistent structure: a context section explaining the problem or feature request, an optional references section tracking the ticket's origin, and implementation notes with optional subsections for files, approach, related code patterns, and known constraints. This enforces outcome-focused communication and enables progressive detail as codebase context becomes available.
git clone --depth 1 https://github.com/superset-sh/superset /tmp/ticket-format && cp -r /tmp/ticket-format/.agents/skills/ticket-format ~/.claude/skills/ticket-formatSKILL.md
# Ticket Format ## Context 2–4 sentences. What's broken or wanted, and why. Outcome-focused, not solution-focused. ## References Where the ticket came from. Omit section if none. | Source | Who | Link | Date | |--------|-----|------|------| | Slack #feedback | @alice | [thread](…) | 2026-05-10 | ## Implementation notes 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 incidents
Personalized audit that teaches the advanced Superset features the user isn't using yet (automations, parallel agents, tasks, multi-host, terminal remote control, custom commands, MCP) and sets them up live. Use when the user wants to get more out of Superset, asks "what else can Superset do", "how do I 10x my workflow", "what am I missing", or wants to learn a specific Superset feature.
Turn a recurring chore into a Superset automation. Drafts the agent prompt, confirms schedule and target, creates it with the CLI, and reviews the first run together. Use when the user wants a scheduled or recurring agent, a daily or weekly job, or says things like "every morning do X", "automate this", "set up a cron agent", "run this on a schedule".
Open, navigate, screenshot, read, click, and type in web pages from an agent. Use when the user asks to open a URL, preview or verify a running web app, check a page's console, fill a form, click through a web flow, or automate anything in a browser, including "open localhost:3000", "screenshot the page", "what does the console say", "click the submit button". Drives the in-app browser pane of a Superset workspace by default and Browser Use for browsers the panes cannot reach.
Verify UI behavior end-to-end by driving the running desktop app over the Chrome DevTools Protocol. Use when asked to verify, reproduce, or confirm a UI change, bug, or regression in the real app rather than in tests.
Operate the user's real desktop apps and windows on macOS, Windows, or Linux. Use when the user asks to open or drive a native app, click or type in a desktop UI, inspect or arrange a window, use their signed-in system browser, or verify an end-to-end GUI flow, including "open Settings and turn on dark mode", "click Save in that window", "what's on screen". Uses an accessibility-first driver (Cua Driver by default, Peekaboo on macOS). Not for Superset's in-app browser pane, headless scraping, or anything an API or CLI can do directly.
Set up a Superset open-source contribution, from forking and cloning superset-sh/superset through local dev setup and the repo's rules to a merge-ready PR. Use when the user wants to contribute to Superset, fix a Superset bug themselves, add a feature to Superset, or prepare a PR against superset-sh/superset.
Create a database migration with Drizzle on a fresh Neon branch. Use when changing the packages/db schema or generating migrations.
Walk the user through design or implementation decisions one at a time, or review completed code one change at a time. Use when the user says "walk me through each decision", "let's decide together", "help me work through these choices", "walk me through what you did", or "QA step by step". Present concise context, mutually exclusive options, log each answer, and finish with a summary.