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.

92

1.48x
Quality

92%

Does it follow best practices?

Impact

95%

1.48x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is highly actionable with executable commands, well-sequenced workflows carrying explicit validation and safety checkpoints, and clean one-level-deep progressive disclosure. The only weakness is mild redundancy between the Backend Detection block and its table and between the Quick Reference and Issue Key Detection sections.

Suggestions

Collapse the 'Backend Detection' numbered code block into the backend table below it to remove a verbatim restatement.

Drop the duplicate view commands in 'Issue Key Detection' since they already appear in the Quick Reference tables.

Fix the MCP tool name mismatch: 'Issue Key Detection' references `mcp__atlassian__jira_get_issue` but the correct tool (per the MCP table and references/mcp.md) is `mcp__atlassian__getJiraIssue`.

DimensionReasoningScore

Conciseness

Mostly lean tables and commands with no concept re-explanation, but the 'Backend Detection' numbered code block restates the table directly beneath it and 'Issue Key Detection' repeats view commands from the Quick Reference, so it could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready commands (`jira issue view ISSUE-KEY`, `jira issue list -a$(jira me)`) and named MCP tools with parameter signatures in the references, matching the fully-executable anchor.

3 / 3

Workflow Clarity

Multi-step workflows are sequenced with explicit validation checkpoints (fetch first, get approval before updating, verify after applying) plus a 'Before Any Operation' checklist and NEVER guards for destructive/batch operations.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview pointing to two real one-level-deep references (commands.md, mcp.md) with a 'Deep Dive' section and a 'Load Reference when' guidance table for clear navigation.

3 / 3

Total

11

/

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.

The description is strong across all dimensions: it names concrete actions, includes a broad set of natural trigger terms, uses an explicit 'Use when...' clause, and carves out a distinct Jira niche. Third-person voice is maintained.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create/view/update issues', 'check sprint status', 'manage their Jira workflow' — matching the anchor for enumerating specific actions rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' (create/view/update issues, sprint status, workflow) and 'when' via an explicit 'Use when...' clause, satisfying the top anchor.

3 / 3

Trigger Term Quality

Covers natural terms users would say ('jira', 'issue', 'ticket', 'sprint', 'backlog') plus the PROJ-123 issue-key pattern, giving broad coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to Jira with distinctive triggers including the issue-key pattern, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
jdrhyne/agent-skills
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.