ticket-craft
Create Jira/Asana/Linear tickets optimized for Claude Code execution - AI-native ticket writing
49
54%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/ticket-craft/SKILL.mdQuality
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 a clear and distinctive niche with good trigger terms covering major 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 such as 'Structures acceptance criteria, defines subtasks, writes implementation-ready descriptions, and formats tickets with clear scope boundaries for AI agent execution.'
Rephrase to use third-person verb form, e.g., 'Creates and optimizes Jira/Asana/Linear tickets for Claude Code execution...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ticket creation for project management tools) and a general action ('Create... tickets'), but doesn't list multiple concrete actions like formatting fields, setting priorities, writing acceptance criteria, or structuring subtasks. | 2 / 3 |
Completeness | Describes what it does (create tickets optimized for Claude Code) but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when' clause caps completeness at 2, and the 'what' itself is also somewhat thin, placing this at 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 specific use case 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 is highly actionable with excellent concrete templates and a well-defined workflow, but it is severely bloated—easily 3-5x longer than necessary. It explains many concepts Claude already knows (INVEST, Given-When-Then, what makes a good user story) and includes extensive reference material inline that should be split into separate files. The core value—the ticket templates and Claude Code Ready Checklist—is buried in excessive context.
Suggestions
Reduce the file to ~100-150 lines by removing explanations of well-known concepts (INVEST, Given-When-Then, story points, what makes good acceptance criteria) and keeping only the Claude Code-specific additions (the +C criterion, the Claude Code Context section, the checklist).
Extract the four ticket templates into separate files (e.g., templates/feature.md, templates/bug.md, templates/tech-debt.md, templates/epic.md) and reference them from the main skill with one-line descriptions.
Move the anti-patterns, epic slicing techniques, story point calibration, and ticket system integration sections into a separate reference file (e.g., REFERENCE.md) linked from the main skill.
Remove the ASCII art boxes entirely—they consume significant tokens while adding no information that a simple heading and bullet list wouldn't convey more efficiently.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Massive ASCII art boxes, lengthy explanations of concepts Claude already knows (INVEST criteria, what user stories are, what Given-When-Then means), extensive anti-pattern explanations, story point calibration tables, and ticket system integration advice that is generic knowledge. The core actionable content could be conveyed in under 100 lines. | 1 / 3 |
Actionability | Provides fully concrete, copy-paste-ready ticket templates with specific field structures, exact verification commands, file path conventions, and a clear /create-ticket workflow with step-by-step instructions. The templates are immediately usable and the good vs bad examples make expectations unambiguous. | 3 / 3 |
Workflow Clarity | The /create-ticket command defines a clear 5-step workflow (Gather → Auto-Detect → Generate → Validate → Output) with an explicit validation checkpoint (Step 4: run the Claude Code Ready Checklist). The bug fix workflow includes TDD steps with verification. The checklist serves as a comprehensive validation gate before any ticket is considered ready. | 3 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no references to supporting files. The four full ticket templates, anti-patterns section, epic slicing techniques, agent team mapping, story point calibration, and ticket system integration guides are all inline. Much of this content (especially templates and reference tables) should be split into separate files with clear navigation from the main skill. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
81%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
65efb33
- 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.