CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

to-tickets

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 locally, or native blocking links on a real tracker).

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/to-tickets/SKILL.md

The canonical home for this skill is to-tickets in mattpocock/skills

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

The body is a strong, self-contained instruction skill: a clearly sequenced five-step workflow with an explicit user-approval checkpoint, concrete output paths, and ready-to-use ticket and issue templates. Its only notable weaknesses are a dense wide-refactor paragraph and an unsignaled external 'tracker doc' reference.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no padding or explanations of known concepts, but the wide-refactor paragraph is a dense run-on block that could be tightened or broken up, fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean 5.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact output paths ('.scratch/<feature-slug>/issues/<NN>-<slug>.md', numbered from 01 in dependency order), two copy-paste templates, a concrete expand-contract sequencing recipe, and specific quiz questions — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

The five-step process is clearly sequenced with an explicit validation checkpoint and feedback loop ('Iterate until the user approves the breakdown') before the batch publish, plus a safety guard ('Do NOT close or modify any parent issue'), matching the top anchor with explicit validation and checklists.

5 / 5

Progressive Disclosure

The skill is a well-organized single file with clear sections and tagged rule/template blocks, but it references 'the tracker doc's operation' — an external document not present in the bundle and not clearly signaled — leaving a minor organization gap rather than the clean one-level-deep structure of a 5.

4 / 5

Total

18

/

20

Passed

Description

58%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.

The description communicates a specific, distinctive capability with concrete actions and both local and tracker output forms, but it entirely lacks 'when to use it' trigger guidance and natural user phrasing. Adding an explicit 'Use when...' clause with natural trigger terms would lift the two weakest dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to break a plan, spec, or discussion into tickets, issues, or a task breakdown.'

Include natural trigger terms and synonyms users would actually say: 'break down the work', 'create issues', 'task breakdown', 'GitHub/Linear issues', 'split into tickets'.

Briefly state what each ticket contains (what to build, acceptance criteria, blocked-by edges) to round out the capability coverage toward the top specificity anchor.

DimensionReasoningScore

Specificity

The description lists several concrete actions — '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' with both output forms ('one file per ticket locally, or native blocking links') — matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

The 'what' is clear and specific, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; the 'when' is entirely absent rather than weakly implied.

3 / 5

Trigger Term Quality

It includes some relevant keywords ('plan', 'spec', 'tickets', 'conversation') but misses the natural phrases users would say, such as 'break down work', 'create issues', 'task breakdown', or tracker names like GitHub/Linear, matching the 'relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Tracer-bullet tickets with blocking edges published to a tracker is a distinctive niche with minimal overlap risk, though the broad inputs ('a plan, spec, or the current conversation') leave minor overlap with general planning skills, fitting the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

withcoral/coral

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.