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

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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-crafted instruction-only skill: exact output formats, two operational decision rubrics, and a procedure with a mandatory human validation gate before the irreversible publish step. The two 4-scores reflect polish gaps — some persuasive padding in the rules/anti-patterns, and no worked example ticket — rather than structural problems.

Suggestions

Add one worked example ticket (title + full body with Blocked by/Tier/Domain lines and the ready-for-agent label where applicable) so the output artifact is copy-paste exemplified rather than only described — this closes the actionability gap.

Trim the justificatory asides in the rules and anti-patterns (e.g. rule 9's incentive explanation, "wearing a different label", "the second is just 'no decision' with extra words") down to their operative sentences; the rationale is useful but currently costs tokens on every load.

In the tier rubric, the pointer to "this repo's local workflow article" is the least concrete reference in the body — either name the file path (as done for scripts/agents.config.sh) or drop the pointer.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — it cites "shared invariant §2/§4/§6/§10" and root AGENTS.md rules without re-explaining them — and it never explains concepts Claude already knows. It sits at 4 rather than 5 because several passages are persuasive rationale rather than instruction, e.g. rule 9's "an agent asked to size itself has every incentive to answer 'the strongest one'" and anti-patterns' "the second is just 'no decision' with extra words", which could be trimmed without losing guidance.

4 / 5

Actionability

Guidance is highly concrete for an instruction-only skill: exact stamp formats ("Blocked by: #N", "Tier: <planner|implementer|mechanical|reviewer>", "Domain: <token>" with regex "[a-z][a-z0-9-]*"), a real command ("gh issue create"), label names, and two decision rubrics with worked examples ("A rename across call sites, a codemod, a dependency bump"). It misses the 5 anchor only because no assembled example ticket (title + body) is shown, leaving the output artifact described rather than exemplified.

4 / 5

Workflow Clarity

The procedure is a clear 5-step sequence (read PRD → draft → quiz → publish → hand off) with an explicit mandatory validation gate before the risky batch action: "Quiz step (mandatory human gate)... Do not publish until they confirm." The quiz functions as a full feedback loop — the user challenges granularity, ordering, labels, and tiers, and tier uniformity is surfaced as a finding — and the anti-patterns section enumerates failure modes.

5 / 5

Progressive Disclosure

No bundle files exist, and the skill appropriately delegates detail to clearly-signaled repo files one level deep — tier definitions to "the root AGENTS.md", tier→model mappings to "scripts/agents.config.sh", domain vocabulary to the same config, terms to "docs/domain-glossary.md" — rather than duplicating or nesting them. The remaining content is a single well-sectioned file (rules, two rubrics, trust boundary, procedure, anti-patterns) where every section is needed at decision time.

5 / 5

Total

18

/

20

Passed

Description

92%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: concrete actions, explicit use/skip triggers tied to sibling commands, and a distinct niche in the workflow chain. Its only weakness is trigger-term coverage — jargon like "tracer-bullet" and missing lay synonyms ("break down", "split up") keep it just below comprehensive.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with their distinguishing properties: "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." Each noun is a specific, verifiable deliverable rather than generic filler, matching the comprehensive-coverage anchor.

5 / 5

Completeness

Both what and when are explicitly answered: the what is the full decomposition-and-publish action, and the when is stated twice with concrete 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." The negative trigger (when NOT to use it) exceeds the clarity of the 5-anchor examples.

5 / 5

Trigger Term Quality

Natural terms for this workflow chain are present — "PRD", "tickets", "issue tracker", "/to-prd", "/implement" — and the skip-condition phrasing gives a user concrete language for deciding. It falls short of the 5 anchor because common synonyms like "break down", "split into tasks", or "create issues" are absent and "tracer-bullet" is internal jargon a user would not naturally say.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche anchored to sibling commands (/to-prd, /implement) and a specific artifact (tracer-bullet tickets with blocking edges and autonomy labels), so it is unlikely to fire for an unrelated skill. It is far more differentiated than the 4-anchor example, which still overlaps neighboring file-format skills.

5 / 5

Total

19

/

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/google-books-clojure

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.