jira-management
Create and update Jira issues, epics, and sprints; manage backlog and sprint transitions. Use when you say: 'create a ticket', 'open a story', 'link an epic', 'start a sprint', or 'search the backlog'.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 a strong skill description that clearly lists concrete Jira-related capabilities and provides explicit trigger phrases users would naturally say. The only minor issue is the use of second person ('you say') instead of third person, but the overall quality is high with good specificity, natural trigger terms, and clear distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: create and update issues, epics, and sprints; manage backlog; handle sprint transitions. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (create/update Jira issues, epics, sprints; manage backlog and sprint transitions) and 'when' (explicit 'Use when' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would actually say: 'create a ticket', 'open a story', 'link an epic', 'start a sprint', 'search the backlog'. These cover common variations of Jira-related requests. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Jira project management with distinct triggers like 'ticket', 'story', 'epic', 'sprint', and 'backlog' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 a high-quality skill that efficiently covers Jira task management with concrete examples, clear workflows, and appropriate progressive disclosure. It respects Claude's intelligence by avoiding unnecessary explanations while providing all the actionable details needed — MCP tool JSON, JQL queries, naming conventions, and a structured session workflow with validation and error recovery steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Jira is or how MCP tools work, assumes Claude's competence, and every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides concrete JSON examples for MCP tool calls, specific JQL queries ready to copy-paste, explicit naming conventions with examples, and a clear issue description template with required fields. | 3 / 3 |
Workflow Clarity | The Session Workflow section provides a clear numbered sequence with validation checkpoints (verify each returns a valid issue key), error recovery (retry once, check config), and a completion verification step (verify all Epic issues are Done, run build/lint/test). The status workflow and transition rules are explicit. | 3 / 3 |
Progressive Disclosure | The skill serves as a clear overview with a well-signaled one-level-deep reference to tracker-config.md for project-specific configuration. Content is appropriately split — the skill contains the universal workflow while project-specific details are externalized. | 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
- monkilabs/opencastle
- Commit
18c6f2c
- 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.