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'.
80
100%
Does it follow best practices?
Impact
—
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 for when to activate. The only minor issue is the use of second person ('you say') instead of third person, but the trigger terms themselves are natural and well-chosen. The description is concise, specific, and highly distinguishable from other skills.
| 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 MCP tool examples, clear workflow sequences with validation checkpoints, and appropriate progressive disclosure. It assumes Claude's competence, avoids unnecessary explanation, and provides actionable guidance throughout. The session workflow includes proper error recovery and verification steps for what are essentially batch/state-changing operations.
| 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. The JSON examples, JQL reference, and naming conventions are all tightly written. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready JSON payloads for MCP tool calls, specific JQL queries, exact naming conventions with examples, and a clear issue description template with required fields. The guidance is specific and executable throughout. | 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). The status workflow and transition rules are clearly defined with error recovery steps. | 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.md covers universal workflow patterns while project-specific keys and IDs are deferred to the config file. | 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
cc13aaf
- 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.