jira
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
86
86%
Does it follow best practices?
Impact
79%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
72%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 description excels at trigger terms and distinctiveness, making it easy for Claude to know when to select this skill. However, it inverts the typical structure by focusing heavily on 'when' while underspecifying 'what' - the actual capabilities are vaguely listed as 'create/view/update issues' without concrete details about what operations are supported.
Suggestions
Add a clear 'what' statement at the beginning listing specific capabilities (e.g., 'Creates, views, updates, and transitions Jira issues. Manages sprints, queries backlogs, adds comments, and links related tickets.')
Restructure to lead with capabilities before the 'Use when...' clause to follow the standard pattern shown in good examples
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jira) and mentions actions like 'create/view/update issues, check sprint status, manage workflow' but these are somewhat generic and not comprehensively detailed (e.g., doesn't specify commenting, transitions, linking issues, etc.). | 2 / 3 |
Completeness | Strong on 'when' with explicit trigger guidance and keywords, but weak on 'what' - the description focuses almost entirely on when to use it rather than clearly stating what capabilities the skill provides. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'jira', 'issue', 'ticket', 'sprint', 'backlog', issue key patterns like 'PROJ-123'. These are exactly what users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with Jira-specific triggers including issue key patterns (PROJ-123), Jira-specific terminology (sprint, backlog), and the explicit 'jira' keyword. Unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent content organization. It efficiently handles dual-backend complexity through clear tables, provides strong safety guardrails with explicit NEVER rules and validation checkpoints, and appropriately defers detailed content to reference files while keeping common operations immediately accessible.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely efficient use of tokens with tables for quick reference, no unnecessary explanations of what Jira is or how it works. Every section serves a clear purpose and assumes Claude's competence. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands for CLI and specific MCP tool names. The quick reference tables give exact syntax for common operations, and the workflow sections provide specific steps. | 3 / 3 |
Workflow Clarity | Excellent workflow structure with explicit validation checkpoints ('Before Any Operation' checklist), clear NEVER rules that prevent common errors, and the backend detection flow is properly sequenced with explicit decision points. | 3 / 3 |
Progressive Disclosure | Well-structured with quick reference for common tasks inline and clear signposting to reference files for complex operations. The 'Deep Dive' section explicitly tells when to load references vs when the quick reference suffices. | 3 / 3 |
Total | 12 / 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
- softaworks/agent-toolkit
- Commit
3027f20
- 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.