jira-assistant
Manage Jira issues via Atlassian MCP — search, create, update, transition status, and handle sprint tasks. Auto-detects workspace configuration. Use when user says "create a Jira ticket", "update my sprint", "check Jira status", "transition this issue", "search Jira", or "move ticket to done". Do NOT use for Confluence pages (use confluence-assistant).
71
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/skills-catalog/skills/(development)/jira-assistant/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, natural trigger phrases users would actually say, explicit 'Use when' and 'Do NOT use' clauses, and clear boundaries distinguishing it from related skills like Confluence. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: search, create, update, transition status, handle sprint tasks, and auto-detect workspace configuration. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (manage Jira issues — search, create, update, transition, sprint tasks) and 'when' (explicit 'Use when' clause with multiple trigger phrases). Also includes a 'Do NOT use' boundary condition for Confluence, which adds clarity. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases: 'create a Jira ticket', 'update my sprint', 'check Jira status', 'transition this issue', 'search Jira', 'move ticket to done'. These are highly natural phrases users would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche (Jira issues via Atlassian MCP) and explicit boundary against Confluence. The specific trigger terms like 'Jira ticket', 'sprint', and 'transition this issue' are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill covers Jira operations comprehensively but is severely bloated with repetitive notes, redundant sections (Best Practices vs Important Notes), and placeholder reminders after every example. It would benefit greatly from splitting reference material (JQL patterns, examples, task template) into separate files and eliminating the pervasive repetition. The actionability is decent but held back by pseudocode-style function calls rather than truly executable examples.
Suggestions
Eliminate redundancy: merge 'Best Practices' and 'Important Notes' into one concise section, and remove the repeated 'Note: Replace placeholders with detected configuration values' after every example—state it once at the top.
Split the Common JQL Patterns, task description template, and detailed examples into separate referenced files (e.g., JQL_PATTERNS.md, TASK_TEMPLATE.md, EXAMPLES.md) to reduce the main skill's token footprint.
Add validation/error handling steps to workflows—e.g., what to do when JQL returns no results, when a transition ID is not available, or when issue creation fails.
Remove the 'When to Use' section entirely since it duplicates the frontmatter description, and trim the Configuration section to just the essential detection logic.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. The phrase 'Replace placeholders with detected configuration values' appears after nearly every example. The 'Important Notes' section at the end largely repeats the 'Best Practices' section. The 'When to Use' section restates what the frontmatter description already covers. The configuration detection workflow is over-explained. The skill is ~200+ lines when it could be ~80-100. | 1 / 3 |
Actionability | Provides concrete MCP tool names and function signatures with parameters, plus JQL examples and a task template. However, all code uses placeholders like {CLOUD_ID} and {PROJECT_KEY} rather than showing realistic executable examples, and the function call syntax isn't real code in any language—it's pseudocode-style notation. | 2 / 3 |
Workflow Clarity | The numbered workflow (Finding → Searching → Getting Details → Creating → Updating) provides a clear sequence, and the issue creation has a step-by-step process. However, there are no validation checkpoints or error handling steps—e.g., no guidance on what to do if issue creation fails, if JQL returns no results, or if a transition is unavailable. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files for detailed content. The task template, all JQL patterns, all examples, and best practices are all inline. The Common JQL Patterns section and the four full examples could easily be split into referenced files, significantly reducing the main skill's token footprint. | 1 / 3 |
Total | 6 / 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
- tech-leads-club/agent-skills
- Commit
906a57d
- 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.