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.
Overall
score
95%
Does it follow best practices?
Validation for skill structure
Discovery
89%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 a well-structured description that excels at trigger term coverage and completeness, with explicit 'Use when' guidance and natural keywords users would say. The main weakness is that the capability description could be more specific about concrete actions beyond the general 'create/view/update' verbs. Uses appropriate third-person voice throughout.
Suggestions
Expand the capability list with more specific actions like 'assign issues, add comments, transition workflow states, search with JQL, view issue details' to improve specificity.
| 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 general rather than listing multiple specific concrete actions like 'assign issues, add comments, transition status, link issues'. | 2 / 3 |
Completeness | Clearly answers both what (create/view/update issues, check sprint status, manage Jira workflow) AND when (explicit 'Use when' clause with specific triggers including keywords and patterns). The description leads with the 'when' guidance. | 3 / 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 when needing Jira help. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche with Jira-specific triggers including the unique issue key pattern 'PROJ-123'. Unlikely to conflict with other skills due to specific product name and terminology like 'sprint', 'backlog'. | 3 / 3 |
Total | 11 / 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 token efficiency through tables and structured sections, provides fully actionable commands for both backends, includes robust safety guardrails with explicit validation steps, and uses progressive disclosure effectively by keeping the main file scannable while pointing to detailed references only when needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using tables for quick reference, avoiding explanations of what Jira is or how APIs work. Every section serves a clear purpose with no padding or unnecessary context. | 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 backend detection steps are explicit and executable. | 3 / 3 |
Workflow Clarity | Multi-step workflows (creating/updating tickets) include explicit validation checkpoints like 'fetch issue first', 'show current vs proposed changes', 'get approval before updating', and 'verify updates after applying'. The 'NEVER' section provides clear guardrails for risky operations. | 3 / 3 |
Progressive Disclosure | Excellent structure with quick reference tables for common operations upfront, clear signaling of when to load detailed references, and a helpful table showing which tasks need reference files. References are one level deep and clearly organized. | 3 / 3 |
Total | 12 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
- 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.