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 defines 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 of the description is excellent with good specificity, natural trigger terms, and clear distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: create and update Jira issues, epics, and sprints; manage backlog and 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 keywords 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 well-crafted skill that efficiently covers Jira task management with concrete examples, clear workflows, and appropriate progressive disclosure. It respects Claude's intelligence by jumping straight into actionable content, provides executable MCP tool examples and JQL queries, and includes proper validation/retry steps in the workflow. The structure is clean with logical section organization.
| 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 use, exact naming conventions with examples, and a clear issue description template with required fields. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | The Session Workflow section provides a clear 7-step sequence with explicit validation checkpoints (verify each returns a valid issue key, retry on failure with specific troubleshooting, verify all Epic issues are Done, run build/lint/test). Error recovery is addressed in step 5. | 3 / 3 |
Progressive Disclosure | The skill serves as a clear overview and immediately references the project-specific configuration file (tracker-config.md) for customization details. Content is well-organized into logical sections without being monolithic, and the external reference is one level deep and clearly signaled. | 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
f5c8508
- 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.