ticket-craft

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

Quality

54%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/ticket-craft/SKILL.md

Quality

Discovery

54%

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 has strong distinctiveness and good trigger terms by naming specific project management tools and the Claude Code optimization angle. However, it lacks an explicit 'Use when...' clause and could benefit from listing more specific concrete actions beyond just 'create tickets'. The description reads more like a tagline than a functional skill description.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to write tickets, create issues, or draft task descriptions for Jira, Asana, or Linear that will be executed by Claude Code.'

List specific concrete actions the skill performs, e.g., 'Structures acceptance criteria, defines subtasks, writes clear requirements, and formats descriptions optimized for AI agent consumption.'

Include common user phrasing variations like 'write a ticket', 'create an issue', 'draft a task', 'story writing', 'backlog grooming' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (ticket creation for project management tools) and a general action (create tickets), but doesn't list multiple specific concrete actions like 'write acceptance criteria, define subtasks, structure requirements'.	2 / 3
Completeness	Describes what it does (create tickets optimized for Claude Code execution) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also somewhat thin, bringing it to 1.	1 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'Jira', 'Asana', 'Linear', 'tickets', 'Claude Code', and 'AI-native'. These cover the major project management tools and the ticket-writing context well.	3 / 3
Distinctiveness Conflict Risk	The combination of specific tools (Jira/Asana/Linear), the specific purpose (tickets optimized for Claude Code execution), and the 'AI-native' qualifier creates a very clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	9 / 12 Passed

Implementation

55%

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

The skill provides highly actionable, well-structured ticket templates with excellent verification steps and concrete examples, but is severely undermined by its extreme verbosity. At 500+ lines, it wastes enormous context window space explaining concepts Claude already understands (INVEST, Given-When-Then, story points, what epics are) and includes content that should be split into separate reference files (ticket system integration, agent team mapping, epic slicing techniques).

Suggestions

Reduce to ~150 lines by removing explanations of concepts Claude already knows (INVEST criteria definitions, what Given-When-Then means, what story points represent) and keeping only the templates and Claude-specific context requirements.

Split into separate files: move ticket templates to TEMPLATES.md, anti-patterns to ANTI_PATTERNS.md, agent team mapping to AGENT_MAPPING.md, and ticket system integration to INTEGRATIONS.md, with brief one-line references from the main skill.

Remove the ASCII art boxes - they consume significant tokens while adding no information beyond what a simple bullet list would convey.

Cut the 'Integration with Ticket Systems' section entirely - it contains generic advice about Jira/Asana/Linear labels that Claude can infer, and is not actionable guidance for ticket creation.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~500+ lines. Explains concepts Claude already knows (INVEST criteria, what Given-When-Then is, what story points are, what epics are). The ASCII art boxes, extensive anti-pattern explanations, and ticket system integration guides add significant token bloat. Much of this is general project management knowledge that doesn't need to be spelled out.	1 / 3
Actionability	Provides fully concrete, copy-paste-ready ticket templates with specific field structures, exact verification commands, file path conventions, and complete examples showing good vs bad tickets. The /create-ticket command workflow gives a clear step-by-step process.	3 / 3
Workflow Clarity	The /create-ticket workflow has clear sequential steps (Gather → Auto-Detect → Generate → Validate → Output). The Claude Code Ready Checklist serves as an explicit validation checkpoint. The Bug Fix Workflow includes a TDD feedback loop (write failing test → verify fails → fix → verify passes → regression check).	3 / 3
Progressive Disclosure	This is a monolithic wall of text with no references to external files. The entire content (~500+ lines) is inline, including four complete ticket templates, epic slicing techniques, story point calibration tables, ticket system integration guides, and agent team mapping - all of which could be split into separate reference files.	1 / 3
	Total	8 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: alinaqi/claude-bootstrap
Commit: d4ddb03

Reviewed: 4 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.