To Tickets
bestofjs/bestofjs
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket…
Break a product-task spec into a set of tracer-bullet tickets, each declaring its blocking edges.
Custom licenceAuto-check passed
Install To Tickets
$ npx skills add blockscout/frontend --skill to-tickets -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install blockscout/frontend to-tickets --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/to-tickets .claude/skills/to-tickets && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "to-tickets" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/to-tickets into .claude/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-tickets", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/blockscout/frontend/tree/main/.agents/skills/to-ticketsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add blockscout/frontend --skill to-tickets -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install blockscout/frontend to-tickets --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/to-tickets .agents/skills/to-tickets && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "to-tickets" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/to-tickets into .agents/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-tickets", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add blockscout/frontend --skill to-tickets -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install blockscout/frontend to-tickets --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/to-tickets .cursor/skills/to-tickets && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "to-tickets" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/to-tickets into .cursor/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-tickets", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/blockscout/frontend.git --path .agents/skills/to-tickets--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add blockscout/frontend --skill to-tickets -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install blockscout/frontend to-tickets --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/to-tickets .gemini/skills/to-tickets && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "to-tickets" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/to-tickets into .gemini/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-tickets", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install blockscout/frontend to-ticketsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add blockscout/frontend --skill to-tickets -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/to-tickets .github/skills/to-tickets && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "to-tickets" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/to-tickets into .github/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-tickets", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add blockscout/frontend --skill to-tickets -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install blockscout/frontend to-tickets --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blockscout/frontend.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/to-tickets .opencode/skills/to-tickets && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "to-tickets" agent skill from https://github.com/blockscout/frontend/tree/main/.agents/skills/to-tickets into .opencode/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-tickets", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
to-tickets- GitHub stars
- 307
- Token cost
- ~1.1k tokens
- SKILL.md length
- 625 words
- Files
- 3
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Break a product-task spec into a set of tracer-bullet tickets, each declaring its blocking edges.
- Works in 6 steps: Load → Explore the codebase (optional) → Draft slices → …
- SKILL.md covers Step 1 — Load, Step 2 — Explore the codebase…, Step 3 — Draft slices and Step 4 — Quiz the user, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
To Tickets is an agent skill from blockscout/frontend. Break a product-task spec into a set of tracer-bullet tickets, each declaring its blocking edges.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `progress-template.md` and `ticket-template.md`).
The repository describes itself as: Front-end application for Blockscout chain explorer.
Example prompts
- “/to-tickets”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Load
- Explore the codebase (optional)
- Draft slices
- Quiz the user
- Front-load the executor inputs
- Write the files
What it can do on your machine
Read from SKILL.md and the folder at commit 56ff467. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
To Tickets loads about 1.1k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 625 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 625 words (~1,081 tokens).
“Break a spec into a set of tickets: tracer-bullet vertical slices, each declaring the tickets that block it. Its input is the spec and open questions.”
- name
- to-tickets
- disable-model-invocation
- true
Files
SKILL.md and 2 other files in .agents/skills/to-tickets of blockscout/frontend.
- SKILL.md
- progress-template.md
- ticket-template.md
Open the folder on GitHubat commit 56ff467
Compare with similar skills
To Tickets next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| To Tickets this skillblockscout/frontend | 307 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| To Ticketsbestofjs/bestofjs | 3.1k | 20 repos | ~1.4k | Automated safety check: Pass | MIT | |
| To Ticketsvinvcn/mattpocock-skills-zh-CN | 4.7k | — | ~924 | Automated safety check: Pass | MIT | |
| What Could Breaksickn33/agentic-awesome-skills | 47k | — | ~1.8k | Automated safety check: Pass | MIT | |
| To Ticketsdevcxl/mattpocock-skills-zh | 449 | — | ~693 | Automated safety check: Pass | MIT | |
| V5 Breaking Changesremotion-dev/remotion | 63k | — | ~879 | Automated safety check: Pass | Custom licence |
Similar skills
To Tickets
vinvcn/mattpocock-skills-zh-CN
把 plan、spec 或当前对话拆成一组 tracer-bullet tickets，每个 ticket 声明 blocking edges，并发布到已配置的 tracker；本地用每 ticket 一个文件中的文本 edge，真实 tracker 用 native blocking links。
What Could Break
sickn33/agentic-awesome-skills
Find what a change breaks outside its own diff, then prove the one fact that makes it safe by running real code.
To Tickets
devcxl/mattpocock-skills-zh
将计划、规范或当前对话拆分为一组 tracer-bullet ticket，每个 ticket 声明其阻塞边（blocking edges），发布到已配置的跟踪器——本地文件中每个 ticket 一个文件以文本表示边，真实跟踪器上以原生阻塞链接表示。
- Official
V5 Breaking Changes
remotion-dev/remotion
Implement or review a Remotion 5 breaking change while the v4 and v5 release lines still share code.
Detecting Pass The Ticket Attacks
mukul975/Anthropic-Cybersecurity-Skills
Detect Kerberos Pass-the-Ticket (PtT) attacks by analyzing Windows Event IDs 4768, 4769, and 4771 for anomalous ticket usage patterns, with detection queries for Splunk and Elastic SIEM.
More from blockscout/frontend
All 24 skills in this repoSlack File
blockscout/frontend
Download Slack attachments by file ID, or upload local files into a Slack thread.
Add Env Var
blockscout/frontend
Step-by-step checklist for adding a new NEXTPUBLIC environment variable.
Add New Page
blockscout/frontend
Scaffold a new page (index / detail / general) and optionally wire it to API data.
Create Issue
blockscout/frontend
Create a GitHub issue from the available context. An agent skill from blockscout/frontend.
Deprecate Env Var
blockscout/frontend
Checklist for deprecating a NEXTPUBLIC environment variable — immediate removal, or a grace period before a later removal.
Publish Beta Types
blockscout/frontend
Publish a beta version of a @blockscout/-types npm package and pin it here.
Questions about To Tickets
What does To Tickets do?
Break a product-task spec into a set of tracer-bullet tickets, each declaring its blocking edges. To Tickets is an agent skill from blockscout/frontend. Break a product-task spec into a set of tracer-bullet tickets, each declaring its blocking edges.
How do I install To Tickets in Claude Code?
Run `npx skills add blockscout/frontend --skill to-tickets -a claude-code`. Or copy the skill folder (.agents/skills/to-tickets in blockscout/frontend) into .claude/skills/to-tickets in your project. Claude Code loads it when a task matches its description.
How do I install To Tickets in Codex?
Run `npx skills add blockscout/frontend --skill to-tickets -a codex`. Or copy the skill folder (.agents/skills/to-tickets in blockscout/frontend) into .agents/skills/to-tickets in your project. Codex loads it when a task matches its description.
Can I use To Tickets in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add blockscout/frontend --skill to-tickets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/to-tickets, .gemini/skills/to-tickets, .github/skills/to-tickets and .opencode/skills/to-tickets in your project.
What does To Tickets need to run?
SKILL.md names no scripts, command-line tools or credentials: To Tickets is instructions for the agent only.
Does To Tickets access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is To Tickets safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does To Tickets use?
To Tickets has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does To Tickets use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to To Tickets?
Skills that share tags, products or a category with To Tickets: To Tickets (bestofjs/bestofjs, 3.1k stars), To Tickets (vinvcn/mattpocock-skills-zh-CN, 4.7k stars), What Could Break (sickn33/agentic-awesome-skills, 47k stars) and To Tickets (devcxl/mattpocock-skills-zh, 449 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains To Tickets?
blockscout (a GitHub organization) maintains it in blockscout/frontend, which has 307 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 9, 2026.
Source: blockscout/frontend on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.