Review Triage Phase
prisma/orm
Runs the triage step of the review-framework loop: reads fetched PR review state, builds `review-actions.json`, validates it and renders `review-actions.md`.
Break a plan, spec, or conversation into dependency-aware, independently verifiable tickets.
Install To Tickets
$ npx skills add stevesolun/ctx --skill to-tickets -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stevesolun/ctx 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/stevesolun/ctx.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/stevesolun/ctx/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/stevesolun/ctx/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 stevesolun/ctx --skill to-tickets -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stevesolun/ctx to-tickets --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stevesolun/ctx.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/stevesolun/ctx/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 stevesolun/ctx --skill to-tickets -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stevesolun/ctx to-tickets --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stevesolun/ctx.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/stevesolun/ctx/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/stevesolun/ctx.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 stevesolun/ctx --skill to-tickets -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stevesolun/ctx to-tickets --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stevesolun/ctx.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/stevesolun/ctx/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 stevesolun/ctx 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 stevesolun/ctx --skill to-tickets -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stevesolun/ctx.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/stevesolun/ctx/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 stevesolun/ctx --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 stevesolun/ctx to-tickets --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stevesolun/ctx.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/stevesolun/ctx/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
- 588
- Token cost
- ~416 tokens
- SKILL.md length
- 197 words
- Files
- 3
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- MIT
At a glance
Break a plan, spec, or conversation into dependency-aware, independently verifiable tickets.
- Wants work sliced for local planning
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- An issue tracker
What it does
To Tickets is an agent skill from stevesolun/ctx. Break a plan, spec, or conversation into dependency-aware, independently verifiable tickets. Use explicitly when the user wants work sliced for local planning or an issue tracker.
Its SKILL.md is about 420 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `TICKET-FORMAT.md` and `agents/openai.yaml`).
It sits in Development, covering Issue triage. The repository describes itself as: CTX Fit finds the cheapest AI coding setup that reliably works on your repository, then applies the winner as a reviewable change. The licence is MIT.
When your agent uses it
- Wants work sliced for local planning
- An issue tracker
Example prompts
- “/to-tickets”
What it can do on your machine
Read from SKILL.md and the folder at commit 11b582a. 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 416 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 197 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
The full file from stevesolun/ctx at commit 11b582a, republished under its MIT licence (© stevesolun). 197 words, ~416 tokens.
Download SKILL.mdSave it as
.claude/skills/to-tickets/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- to-tickets
- description
- Break a plan, spec, or conversation into dependency-aware, independently verifiable tickets. Use explicitly when the user wants work sliced for local planning or an issue tracker.
Create tickets
Read the source plan, spec, issue, or conversation and inspect enough of the repository to avoid fictional boundaries. Use the project's established domain language and preserve relevant architectural decisions.
Prefer narrow vertical slices that deliver observable behavior and can be verified independently. Size work for the actual team and risk rather than a fixed context-window rule. Use horizontal or mechanical slices when the change cannot remain coherent vertically.
Model only real blocking edges. Tickets without blockers form the available frontier and may proceed concurrently. For a broad compatibility migration, consider an expand–migrate–contract sequence so intermediate states remain usable.
Each ticket should communicate:
- the behavior or outcome it delivers;
- concrete acceptance criteria;
- genuine dependencies;
- relevant constraints or source references; and
- scope boundaries when adjacent work is easy to confuse.
Use the ticket format when the destination has no stronger convention. Avoid brittle line numbers and implementation recipes unless the ticket is intentionally mechanical.
Present a draft when granularity or dependencies remain uncertain. Publish or write tickets only when requested and authorized, following the configured tracker's native dependency model. Do not alter a parent item or apply workflow labels unless that action is part of the request.
© stevesolun, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in .agents/skills/to-tickets of stevesolun/ctx.
- SKILL.md
- TICKET-FORMAT.md
- agents/openai.yaml
Open the folder on GitHubat commit 11b582a
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 skillstevesolun/ctx | 588 | — | ~416 | Automated safety check: Pass | MIT | |
| Review Triage Phaseprisma/orm | 48k | — | ~995 | Automated safety check: Pass | Apache-2.0 | |
| Triagearcee-ai/nac | 281 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Harbor Issue and PR IntakeYeachan-Heo/oh-my-claudecode | 40k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Marketplace Health Checkdaymade/claude-code-skills | 1.4k | — | ~2k | Automated safety check: Pass | MIT | |
| Setup Matt Pocock Skillsnodetool-ai/nodetool | 560 | — | ~589 | Automated safety check: Pass | AGPL-3.0 |
Similar skills
- Official
Triage
arcee-ai/nac
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked…
Harbor Issue and PR Intake
Yeachan-Heo/oh-my-claudecode
Triages incoming issues and pull requests for a maintainer: verifies claims, reuses past decisions and delivers a docket of open questions, and never merges.
Marketplace Health Check
daymade/claude-code-skills
Runs a 6-dimension evidence-based health audit of this skills marketplace repo — code safety, docs/SSOT, security/PII, PR/issue triage, manifest integrity — via a parallel workflow, then verifies…
Setup Matt Pocock Skills
nodetool-ai/nodetool
Configure repository issue-tracker, triage-label, and domain-document conventions when setup or reconfiguration is requested.
Wayfinder
bestofjs/bestofjs
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
More from stevesolun/ctx
All 26 skills in this repoDiagnosing Bugs
stevesolun/ctx
Diagnose hard bugs and performance regressions with reproducible evidence, focused hypotheses, and proportional instrumentation.
Repo Stats Autoupdate
stevesolun/ctx
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory.
Code Review
stevesolun/ctx
Review a Git diff against repository standards and its originating requirements.
No Mistakes
stevesolun/ctx
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI.
Skill Router
stevesolun/ctx
Repo-aware recommendation manager for ctx. An agent skill from stevesolun/ctx.
Codebase Design
stevesolun/ctx
Design or improve module interfaces using deep-module heuristics.
Related
Categories
Questions about To Tickets
What does To Tickets do?
Break a plan, spec, or conversation into dependency-aware, independently verifiable tickets. To Tickets is an agent skill from stevesolun/ctx. Break a plan, spec, or conversation into dependency-aware, independently verifiable tickets.
When should I use To Tickets?
To Tickets fits situations like: wants work sliced for local planning; an issue tracker.
How do I install To Tickets in Claude Code?
Run `npx skills add stevesolun/ctx --skill to-tickets -a claude-code`. Or copy the skill folder (.agents/skills/to-tickets in stevesolun/ctx) 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 stevesolun/ctx --skill to-tickets -a codex`. Or copy the skill folder (.agents/skills/to-tickets in stevesolun/ctx) 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 stevesolun/ctx --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 is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does To Tickets use?
About 416 tokens (SKILL.md is roughly 1.7k 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: Review Triage Phase (prisma/orm, 48k stars), Triage (arcee-ai/nac, 281 stars), Harbor Issue and PR Intake (Yeachan-Heo/oh-my-claudecode, 40k stars) and Marketplace Health Check (daymade/claude-code-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains To Tickets?
stevesolun (a GitHub user) maintains it in stevesolun/ctx, which has 588 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 4, 2026.
Source: stevesolun/ctx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.