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).

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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 concrete MCP calls and examples, and its workflows are well-sequenced. It loses points for redundancy, missing post-action verification checkpoints, and a monolithic structure with no progressive disclosure to reference files.

Suggestions

Remove repeated placeholder-substitution notes (consolidate into one statement near the top) and delete the redundant "Common JQL Patterns" or "Important Notes" sections that restate earlier content.

Add explicit validation checkpoints after state-changing operations (e.g., re-fetch the issue after createJiraIssue/transitionJiraIssue to confirm the new state, and handle error responses before proceeding).

Move the long Default Task Template and the JQL pattern catalog into reference files (e.g. references/task-template.md, references/jql-patterns.md) and link to them one level deep, keeping SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly actionable with no concept-padding, but noticeably redundant: "Note: Replace placeholders with detected configuration values" recurs ~4 times, "Common JQL Patterns" reprints section 2's JQL, and "Important Notes" restates "Best Practices" — content that could be tightened.

2 / 3

Actionability

Concrete MCP tool calls with named parameters (createJiraIssue, searchJiraIssuesUsingJql, getTransitionsForJiraIssue), full worked examples, a reusable task template, and ready-to-use JQL — copy-paste ready guidance.

3 / 3

Workflow Clarity

Sequencing and numbered steps are clear (config detection → search → create → transition), but there are no explicit validation/verification checkpoints or error-recovery feedback loops after state-changing create/transition operations, capping clarity at 2 per the destructive/batch guideline.

2 / 3

Progressive Disclosure

A ~325-line monolithic single file with no external references; the long task template and JQL pattern catalog are inline content that could be split out, and the under-50-lines simple-skill exception does not apply.

2 / 3

Total

9

/

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: concrete actions, natural trigger phrases, complete what/when guidance, and active disambiguation from a related skill. It uses third-person voice throughout with no over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "search, create, update, transition status, and handle sprint tasks" — matching the anchor for several specific concrete actions rather than just naming a domain.

3 / 3

Completeness

Explicitly answers both what ("Manage Jira issues via Atlassian MCP — search, create, update...") and when ("Use when user says...") with explicit triggers, satisfying the highest anchor.

3 / 3

Trigger Term Quality

Provides natural user phrases ("create a Jira ticket", "update my sprint", "check Jira status", "transition this issue", "search Jira", "move ticket to done") that users would actually say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Clear Jira-via-Atlassian-MCP niche with distinct triggers and an explicit disambiguation ("Do NOT use for Confluence pages (use confluence-assistant)") that prevents conflicts with a sibling skill.

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.

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.