CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 naming conventions, explicit workflow sequences with validation checkpoints, and appropriate progressive disclosure to project-specific config. It respects Claude's intelligence throughout and provides actionable, copy-paste-ready guidance for every operation.

DimensionReasoningScore

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 JQL examples, naming conventions, and workflow are all tightly written.

3 / 3

Actionability

Provides concrete JSON examples for MCP tool calls (search, create, transition), executable JQL queries, specific 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 validation checkpoints: verifying issue keys after creation, retry logic with a fallback to config on failure, and a completion verification step (all Epic issues Done, run build/lint/test). The status workflow and transition rules are explicit.

3 / 3

Progressive Disclosure

The skill serves as a clear overview and appropriately delegates project-specific configuration (project keys, workflow state IDs, board config) to tracker-config.md via a well-signaled one-level-deep reference. Content is well-organized into logical sections without being monolithic.

3 / 3

Total

12

/

12

Passed

Description

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 use it. The only minor issue is the use of second person ('you say') instead of third person, which slightly deviates from the voice guidelines but doesn't significantly impact functionality. The trigger terms are natural and well-chosen, covering common Jira terminology users would employ.

DimensionReasoningScore

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

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.