jira-tickets
Use when functional requirements are ready and approved. Creates JIRA Epics and Stories for EA then GA sequentially using JIRA MCP.
84
76%
Does it follow best practices?
Impact
96%
2.90xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/jira-tickets/SKILL.mdQuality
Discovery
75%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 functional and clearly states both when to use the skill and what it does, giving it strong completeness. However, it relies on unexpanded acronyms (EA, GA, MCP) that reduce accessibility and trigger term coverage, and the specificity of concrete actions could be improved by listing more detail about what the Epic/Story creation involves.
Suggestions
Expand acronyms (EA → Early Access, GA → General Availability, MCP → the relevant tool name) so the description is self-contained and matches more natural user language.
Add common trigger term variations users might say, such as 'tickets', 'user stories', 'backlog creation', or 'sprint planning' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (JIRA) and some actions (creates Epics and Stories), mentions EA then GA sequentially, but doesn't elaborate on what the creation entails beyond naming artifact types. | 2 / 3 |
Completeness | Clearly answers both 'what' (creates JIRA Epics and Stories for EA then GA using JIRA MCP) and 'when' (when functional requirements are ready and approved), with an explicit trigger condition stated upfront. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'JIRA', 'Epics', 'Stories', 'functional requirements', and 'JIRA MCP', but uses acronyms (EA, GA) without expansion that users might not naturally say, and misses common variations like 'tickets', 'backlog', 'user stories', or 'sprint planning'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of JIRA Epic/Story creation, EA-then-GA sequencing, JIRA MCP tooling, and the trigger of approved functional requirements creates a very specific niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity — clear sequential steps, precondition checks, error handling, and idempotency support. The main weakness is that it's somewhat long for a single file with no progressive disclosure to supporting references, and a few sections could be tightened for conciseness. The concrete templates, exact tool names, and specific formatting examples make this very executable.
Suggestions
Consider extracting the description templates (Epic description, Story description) and work-type suffix mappings into a companion reference file to reduce the main skill's length and improve progressive disclosure.
Tighten the precondition logic — the four bullet points describing which files to check could be condensed into a small decision table or two-line rule.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining concepts Claude already knows, but some sections could be tightened — e.g., the precondition logic is somewhat verbose, and the confirmation message templates include formatting details that could be more compact. | 2 / 3 |
Actionability | Highly actionable: specifies exact MCP tool names (createJiraIssue), exact field mappings, summary formats, description templates with markdown structure, file paths, frontmatter updates, and concrete examples like `PROJ-42` and `PROJ-43`. Copy-paste ready templates throughout. | 3 / 3 |
Workflow Clarity | Clear 6-step sequential workflow with explicit precondition checks, validation gates (status: done check, status: approved check), error handling (MCP failure mid-run: stop and report), idempotency (skip stories with existing keys), and a completion confirmation step with summary metrics. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but it's a moderately long monolithic file (~100+ lines of instruction) with no references to supporting files. The description templates and work-type suffix mappings could be extracted to reference files, though no bundle files exist to support this. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- PagerDuty/ai-forward-planning
- Commit
585e8a6
- 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.