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

81%

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

71%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 thorough, highly actionable skill body with excellent executable examples and clear workflows. Its weaknesses are token efficiency (generic testing concepts Claude already knows) and the absence of progressive disclosure via separate reference files.

Suggestions

Trim the 'Test Types Needed' and 'Edge Cases & Error Scenarios' lists, which restate generic testing knowledge Claude already has; keep only Jira-specific guidance.

Move the bulk of the REST API reference, MCP tools table, and comment templates into separate files under references/ and link to them from SKILL.md to improve progressive disclosure.

Add an explicit validation feedback loop for destructive operations (e.g., after transitioning a ticket, verify the new status before reporting success).

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete tables and code, but sections like 'Test Types Needed' (unit/integration/E2E/API) and 'Edge Cases' (invalid inputs, unauthorized access, network failures) restate generic testing concepts Claude already knows.	3 / 5
Actionability	Fully executable, copy-paste-ready guidance throughout: the `jira_curl` helper, complete REST endpoints with `jq` projections, MCP config JSON, and concrete transition/comment workflows covering the common cases.	5 / 5
Workflow Clarity	Clear sequencing with a key checkpoint ('Always call jira_get_transitions before transitioning') and a workflow-step-to-Jira-update mapping table, but lacks an explicit validate→fix→retry feedback loop for state-changing operations.	4 / 5
Progressive Disclosure	Well-organized into sections, but at ~300 lines it is monolithic with no bundle files or external references — the REST API reference, MCP tools table, and comment templates are all inlined rather than split into separate files.	3 / 5
	Total	15 / 20 Passed

Description

92%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, specific description that clearly states both capabilities and activation triggers with good synonym coverage. The only minor gap is the omission of a few natural Jira terms like JQL or sprint.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues' plus 'Jira API patterns via MCP or direct REST calls' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' ('Provides Jira API patterns via MCP or direct REST calls') and 'when' ('Use this skill when retrieving Jira tickets, analyzing requirements...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keyword coverage including synonyms ('Jira tickets' and 'issues', 'ticket status', 'comments', 'transitioning'), but common variations like 'JQL', 'sprint', or 'bug' are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Jira issue tracking) with distinct, domain-specific triggers, making conflict with other skills minimal.	5 / 5
	Total	19 / 20 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: 06c5e11

Reviewed: 3 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.