CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

to-tickets

Decompose a PRD issue into tracer-bullet tickets — demoable vertical slices sized to one fresh context window, with blocking edges and autonomy labels, published to the project issue tracker. Use after /to-prd when a build spans more than one session; skip it (use /implement directly) when the whole change fits one context window.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is to-tickets in agranado2k/google-books-clojure

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction-only skill with an unusually strong workflow: mandatory human gate before batch publishing, a trust boundary on untrusted PRD input, and copy-usable stamp formats. Its weakest dimension is token efficiency — the model-name prohibition and several rules are repeated across sections, and the anti-patterns list mostly restates earlier rules.

Suggestions

State the never-name-a-model rule once (rule 9 or the tier section) and drop the repetitions in the domain rubric and anti-patterns.

Trim the anti-patterns to only the entries not already covered by rules 1-10 (e.g., keep 'tickets that only make sense read together'; drop restatements of rules 4, 9, and 10).

Add one short example ticket body showing the title, 'Part of #<prd>', 'Blocked by:', 'Tier:', optional 'Domain:', and label assembled together.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence (no basic-concept explanations), but it could be tightened: the never-name-a-model rule is stated four times (rule 9, the tier section's 'Never write a model name', the domain rubric's 'Still never a model name', and the anti-patterns), and the anti-patterns bullets largely restate rules 4, 9, and 10.

3 / 5

Actionability

Guidance is mostly executable — exact labels ('ready-for-agent'), exact stamp lines ('Blocked by: #N', 'Tier: <planner|implementer|mechanical|reviewer>', 'Domain: <token>' with a token regex), the concrete command 'gh issue create', and a first-hit-wins decision order for tiers. The minor gap is that no assembled example ticket body shows all the stamped lines together.

4 / 5

Workflow Clarity

The Procedure is a clear 5-step sequence with an explicit validation checkpoint for a batch external operation — the mandatory quiz step ('Do not publish until they confirm') — plus a trust-boundary stop rule before acting on untrusted PRD content and a defined handoff to /implement.

5 / 5

Progressive Disclosure

Sections are well organized and detail is deferred one level deep to clearly signaled external files (root AGENTS.md for the tier definitions, docs/domain-glossary.md for the domain language, scripts/agents.config.sh for tier/domain mappings); the minor gap is that the tier decision procedure is reproduced inline alongside the pointer to its canonical definition.

4 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete about the artifact produced, and explicit about both when to use and when not to use the skill. The only soft spot is keyword coverage, which relies on the /to-prd ecosystem's vocabulary and misses everyday synonyms a user might say.

DimensionReasoningScore

Specificity

The description lists several concrete actions and output attributes — 'decompose a PRD issue into tracer-bullet tickets', 'demoable vertical slices sized to one fresh context window, with blocking edges and autonomy labels, published to the project issue tracker' — but it is one composite workflow rather than the multiple distinct actions of the top anchor.

4 / 5

Completeness

It explicitly answers both questions: the 'what' is the full ticket decomposition with its attributes and publish target, and the 'when' is stated with concrete positive and negative triggers — 'Use after /to-prd when a build spans more than one session; skip it (use /implement directly) when the whole change fits one context window.'

5 / 5

Trigger Term Quality

Natural terms for this workflow chain are present ('PRD', 'tickets', 'session', '/to-prd', '/implement'), giving good keyword coverage; common variations a user might say ('break down', 'split into tasks', 'stories', 'epics') are missing, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (tracer-bullet ticket decomposition after /to-prd) and explicitly disambiguates against the nearest neighbor ('skip it — use /implement directly'), so the risk of triggering for the wrong skill is minimal.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 possibly missing (scripts/agents.config.sh, scripts/agents.lib.sh)

Warning

Total

15

/

16

Passed

Repository

agranado2k/tic-tac-toe-with-agentic-sdlc

Path

.claude/skills/to-tickets/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.