CtrlK
BlogDocsLog inGet started
Tessl Logo

jira-assistant

Manage Jira issues via Atlassian MCP — search, create, update, transition status, and handle sprint tasks. Auto-detects workspace configuration. Use when user says "create a Jira ticket", "update my sprint", "check Jira status", "transition this issue", "search Jira", or "move ticket to done". Do NOT use for Confluence pages (use confluence-assistant).

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, highly actionable skill body with concrete tool calls and worked examples, weakened only by some internal duplication and the absence of post-operation verification steps. Structure is clear but entirely inline with no reference files.

Suggestions

Remove the duplicated JQL queries in 'Common JQL Patterns' (or collapse them into §2) and delete 'Important Notes' entries that restate 'Best Practices' to cut redundancy.

Add a post-operation verification step after transitions and edits — e.g., call getJiraIssue to confirm the new status/fields took effect before reporting success to the user.

Consider moving the 'Default Task Template' and 'Common JQL Patterns' into reference files (e.g. references/task-template.md, references/jql-patterns.md) so SKILL.md stays a lean overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and is mostly efficient, but 'Common JQL Patterns' duplicates queries already shown in §2 and the closing 'Important Notes' largely restates 'Best Practices', so it could be tightened.

4 / 5

Actionability

Provides concrete, parameterized MCP tool calls (createJiraIssue, editJiraIssue, transitionJiraIssue, etc.) with a step-by-step create workflow and four fully worked examples covering the common cases.

5 / 5

Workflow Clarity

Multi-step processes (configuration detection, create a/b/c, transition 1/2) are clearly sequenced with a pre-flight required-fields checkpoint, but there is no post-operation verification (e.g., fetch the issue back to confirm a transition applied).

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections that are easy to navigate, but the skill is a ~325-line monolith with no bundle files; the task template and JQL pattern catalog could live in one-level-deep reference files.

4 / 5

Total

17

/

20

Passed

Description

100%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.

This is an exemplary description: it states concrete capabilities, provides multiple natural trigger phrases, answers both what and when explicitly, and includes a negative boundary to avoid mis-triggering. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'search, create, update, transition status, and handle sprint tasks' — giving comprehensive coverage of the skill's capabilities rather than vague domain language.

5 / 5

Completeness

Explicitly answers 'what' (manage Jira issues via Atlassian MCP, with listed actions) and 'when' (concrete 'Use when user says...' trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Includes six natural user phrases ('create a Jira ticket', 'update my sprint', 'check Jira status', 'transition this issue', 'search Jira', 'move ticket to done') covering synonyms and common phrasings a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear Jira-specific niche with an explicit negative boundary ('Do NOT use for Confluence pages (use confluence-assistant)') minimizing conflict risk with adjacent skills.

5 / 5

Total

20

/

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
tech-leads-club/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.