ticket-craft

Create Jira/Asana/Linear tickets optimized for Claude Code execution - AI-native ticket writing

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ticket-craft/SKILL.md

Quality

Content

58%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 content is highly actionable with clear sequenced workflows and validation checkpoints, but it is a monolithic, token-heavy single file that inlines large templates and reference material instead of progressively disclosing them via bundle files. Tightening the body and extracting templates to references would substantially improve the two lowest dimensions.

Suggestions

Extract the four full ticket templates into references/ files (e.g. references/feature-template.md, references/bug-template.md) and link to them from a compact overview, lifting progressive_disclosure from 2 toward 4–5.

Collapse the large ASCII boxes (Core Principle, Claude Code Ready Checklist) into concise bullet lists or move to a reference file to cut ~100 lines and lift conciseness from 2 toward 3–4.

Move the per-system integration notes (Jira/Asana/Linear/GitHub) and the Story Points calibration table into a single references/integrations.md, keeping only the one-line summary in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The 670-line body is noticeably verbose for an overview skill: large ASCII boxes (Core Principle, Checklist) and repeated template scaffolding across four ticket types pad the token budget. It is above 1 (not a concept-explainer wall of prose) but well below 3 — significant tightening is possible without losing clarity.	2 / 5
Actionability	Provides concrete, copy-paste-ready ticket templates with exact bash verification commands (`npm test -- --grep`, `npm run typecheck`) and real file-path placeholders. Minor gaps keep it below 5: many placeholders (`{file}`, `{path}`) are unexpanded, and some examples are illustrative rather than fully executable.	4 / 5
Workflow Clarity	The '/create-ticket' workflow (Steps 1–5) is explicitly sequenced with a validation checkpoint (Step 4 runs the Claude Code Ready Checklist, flags unchecked items), and the Bug Fix Workflow uses TDD with explicit verify-fail/verify-pass feedback loops. This matches the top anchor's feedback loops and checklists.	5 / 5
Progressive Disclosure	Monolithic single-file design with no references/, scripts/, or assets/ bundle and no links to separate detailed files; the four full ticket templates, slicing techniques, and integration guides are all inlined where they could be split out. It is above 1 (well-sectioned, navigable) but the bulk that belongs in separate files is inlined, matching the score-2 anchor.	2 / 5
	Total	13 / 20 Passed

Description

62%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 is specific to a clear niche (AI-executable tickets across Jira/Asana/Linear) with strong trigger terms and low conflict risk, but it lacks an explicit 'Use when...' trigger clause and uses one slightly generic phrase ('AI-native ticket writing'). Adding a concrete trigger clause and a second action verb would lift the lowest dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when creating tickets, breaking down epics, or writing specs for Claude Code execution.' (lifts completeness from 3).

Replace or expand 'AI-native ticket writing' with another concrete action such as '...break down epics, and write Claude Code Ready specs' to add a second specific action (lifts specificity).

Include common synonyms users say — 'issues', 'epics', 'subtasks', 'specs' — so the description covers natural variations (lifts trigger_term_quality toward 5).

Dimension	Reasoning	Score
Specificity	It names the domain (Jira/Asana/Linear tickets) and a concrete action (Create tickets) plus an optimization target (Claude Code execution), but 'AI-native ticket writing' is generic and the only concrete action is 'Create'. Not below 2 (domain + an action) nor above 4 (several specific actions).	3 / 5
Completeness	Clear 'what' (create AI-optimized tickets for those systems) but no explicit 'Use when...' trigger clause in the description itself; the 'when' is only weakly implied via 'AI-native ticket writing'. The rubric caps completeness at 3 when an explicit trigger guidance is missing.	3 / 5
Trigger Term Quality	Strong natural keywords: 'Jira/Asana/Linear', 'tickets', 'Claude Code', 'Claude Code execution' — terms users would say. Slightly below 5 because it omits common synonyms like 'issues', 'specs', 'epics', and 'subtasks' that the skill actually supports.	4 / 5
Distinctiveness Conflict Risk	The 'optimized for Claude Code execution' framing carves a clear niche distinct from generic ticket-writing or project-management skills, with minimal overlap risk. Even neighboring skills would not trigger on 'Claude Code Ready tickets'.	5 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (678 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/ticket-craft/SKILL.md
Commit: abc600e

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.