CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

89

1.00x
Quality

89%

Does it follow best practices?

Impact

79%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is jira in softaworks/agent-toolkit

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with strong guardrails and validation feedback loops for destructive Jira operations, plus clean progressive disclosure to real reference files. Minor conciseness redundancy and a few incomplete command examples keep actionability and conciseness at 4.

DimensionReasoningScore

Conciseness

Efficient table-driven structure with no concept-overexplaining, but the Quick Reference tables and the Triggers/Issue Key Detection sections overlap somewhat and could be tightened.

4 / 5

Actionability

Provides concrete, copy-pasteable CLI commands and MCP tool names with minor gaps (e.g., shell-substitution patterns like $(jira me) are shown but not all flag combinations).

4 / 5

Workflow Clarity

Multi-step create/update workflows are clearly sequenced with explicit validation checkpoints (fetch first, get approval, verify after applying) and feedback loops for destructive/batch transitions.

5 / 5

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references to real files (references/commands.md, references/mcp.md) and an explicit 'Load reference when' decision table.

5 / 5

Total

18

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly establishes a Jira-specific niche with explicit 'Use when' triggers and comprehensive natural keywords. Minor specificity gaps keep it just below perfect on action enumeration.

DimensionReasoningScore

Specificity

Lists several concrete actions ('create/view/update issues', 'check sprint status', 'manage their Jira workflow') but 'manage workflow' is slightly generic, leaving minor coverage gaps versus a fully comprehensive list.

4 / 5

Completeness

Explicitly answers both 'what' (create/view/update issues, check sprint status, manage workflow) and 'when' ('Use when the user mentions Jira issues...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural keyword coverage including synonyms ('jira', 'issue', 'ticket', 'sprint', 'backlog') plus the concrete issue-key pattern example 'PROJ-123'.

5 / 5

Distinctiveness Conflict Risk

Jira-specific niche with distinct, domain-bound triggers and an explicit issue-key pattern; minimal risk of triggering for the wrong skill.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
softaworks/agent-toolkit
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.