jira-integration

Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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 executable curl/jq/MCP examples and useful tables, but it is a long monolithic file with no external references and validation checkpoints scattered as tips. Conciseness, workflow_clarity, and progressive_disclosure are the weakest dimensions.

Suggestions

Move the REST API reference, comment templates, and structured-analysis output template into separate files under references/ (e.g. REST_API.md, COMMENT_TEMPLATES.md) and link to them from SKILL.md to improve progressive_disclosure and conciseness.

Condense the comment templates into a single parameterized template with the variants noted inline, and trim the structured-analysis output block to a shorter schema to reduce token overhead.

Add an explicit gated workflow for ticket transitions and updates (e.g. get transitions → choose ID → transition → verify status changed → retry on error) so validation checkpoints are sequenced rather than scattered as tips.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete and avoids explaining concepts Claude already knows, but it runs ~300 lines with multiple full comment templates and a large structured-analysis output template that could be tightened. Not a 3 because not every token earns its place; not a 1 because it is not padded with concept explanations.	2 / 3
Actionability	"jira_curl" helper, copy-paste curl/jq examples, a complete MCP config JSON block, and a tool reference table with examples are fully executable and specific. Not a 2 because the guidance is real code rather than pseudocode or abstract direction.	3 / 3
Workflow Clarity	Sequences exist (the 2-step transition flow, the When-to-Update table) with some checkpoints ("Always call jira_get_transitions before transitioning", "validate credentials... fail fast"), but validation is scattered as tips rather than an explicit gated validate→fix→retry loop. Not a 3 because checkpoints are implicit; not a 1 because steps and some validation are clearly present.	2 / 3
Progressive Disclosure	The file is well-organized by headers, but at ~300 lines it is a monolithic single file with no bundle files (references/, scripts/, assets/ absent), and content like the REST API reference and comment templates that could be separate is inline. Not a 1 because organization is decent; not a 3 because nothing is split into one-level-deep references.	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 concise and complete: it names multiple concrete actions, includes an explicit 'Use this skill when' trigger, and carves out a distinct Jira-specific niche. It answers both what the skill does and when to use it without padding.

Dimension	Reasoning	Score
Specificity	"retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues" lists multiple specific concrete actions rather than vague language. Not a 2 because the actions are comprehensive and distinct, not just a domain name with partial actions.	3 / 3
Completeness	"Use this skill when retrieving..." gives an explicit when-trigger, and "Provides Jira API patterns via MCP or direct REST calls" states what it does. Both what and when are explicitly present, matching the level-3 anchor.	3 / 3
Trigger Term Quality	"Jira tickets", "ticket status", "adding comments", and "transitioning issues" are natural terms a user would actually say when needing this skill. Not a 2 because it covers several common phrasings rather than a single generic keyword.	3 / 3
Distinctiveness Conflict Risk	The "Jira" niche with ticket/comment/transition triggers is clearly distinct and unlikely to fire for unrelated skills. Not a 2 because the domain and triggers are specific enough to avoid overlap with general project-management skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/jira-integration/SKILL.md
Commit: 754b8dd

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.