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

88%

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

81%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, opinionated instruction skill: concrete stamps, labels, and commands, a mandatory human validation gate before publishing, and a tight anti-patterns section. The remaining room is trimming rhetorical reinforcement, adding one worked ticket example, and considering whether the tier/domain rubrics belong in a reference file to slim the main body.

Suggestions

Add a short worked example of a finished ticket body (title, Blocked by / Tier / Domain lines, ready-for-agent label) so the publish format is copy-paste ready.

Trim repeated or rhetorical justification — e.g. the second 'never a model name' passage in the domain rubric section and the 'agent asked to size itself' aside in rule 9.

The body runs ~64 lines; moving the tier and domain rubrics into a references/ file (linked from the rules) would keep SKILL.md a lean overview and earn the top progressive-disclosure anchor.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no explanations of what a PRD or ticket is), but includes rhetorical expansions that could be trimmed — e.g. 'an agent asked to size itself has every incentive to answer "the strongest one"' — and restates the never-name-a-model rule twice ('Still never a model name... the rot rule 9 avoids'). This fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place level.

4 / 5

Actionability

Highly concrete guidance: exact stamps ('Tier: <planner|implementer|mechanical|reviewer>', 'Domain: <token>', 'Blocked by: #N', 'Part of #<prd>'), the ready-for-agent label mechanism, a first-hit-wins tier rubric, and a real command ('gh issue create'). The minor gap keeping it below 'fully executable... specific examples cover the common cases' is the absence of a worked example of a finished ticket body.

4 / 5

Workflow Clarity

The procedure is a clear 5-step sequence with an explicit validation gate before the batch, hard-to-reverse publish step ('Quiz step (mandatory human gate)... Do not publish until they confirm'), a stop-and-surface rule for untrusted PRD content, and an error-recovery heuristic ('A decomposition that came out all one tier is a finding worth stating'). This matches the top anchor: explicit validation steps with feedback loops for the risky publish operation.

5 / 5

Progressive Disclosure

A single well-organized file with clear sections (Rules, tier rubric, domain rubric, Trust boundary, Procedure, Anti-patterns) and repo-level pointers (docs/domain-glossary.md, scripts/agents.config.sh) rather than nested skill references. At ~64 lines it exceeds the under-50-line threshold where a single organized file would merit a 5, and the tier/domain rubrics could arguably live in a reference file, so it fits 'good structure; minor organization gaps'.

4 / 5

Total

17

/

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, comprehensive, third-person, and with explicit use/skip conditions tied to sibling workflow commands. The only weakness is mild reliance on project-specific jargon over natural synonyms, which slightly narrows how users would phrase the trigger.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the skill comprehensively: 'Decompose a PRD issue into tracer-bullet tickets', 'sized to one fresh context window, with blocking edges and autonomy labels, published to the project issue tracker'. No element of the skill's coverage is missing, so it fits the 'multiple specific concrete actions; comprehensive coverage' anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

It explicitly answers both questions: the 'what' (decompose into demoable one-window slices with blocking edges and autonomy labels, published to the tracker) and a concrete 'when' with trigger phrases — '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 explicit skip guidance exceeds the 4 anchor's 'when could be more specific'.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('Decompose', 'PRD', 'tickets', 'issue tracker', 'build spans more than one session') but it leans on project jargon and slash-command names ('tracer-bullet', '/to-prd', '/implement') and misses common variations users might say ('break down', 'split work', 'create tickets'). Fits 'good keyword coverage; a few natural terms missing', not the synonym-level coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — PRD-to-ticket decomposition — chained to sibling commands /to-prd and /implement with explicit skip conditions, so it is unlikely to trigger for the wrong skill. This matches 'clear niche with distinct triggers; minimal conflict risk'.

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/tic-tac-toe-haskell

Path

.agents/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.