CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

jira-integration

Retrieves Jira tickets, analyzes requirements, updates ticket status, adds comments, or transitions issues via MCP or direct REST API patterns.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/jira-integration/SKILL.md
SKILL.md
Quality
Evals
Security

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 highly actionable, well-structured skill with executable MCP and REST examples, explicit transition validation, and strong security guidance including untrusted-ticket-content handling. Its weaknesses are moderate verbosity from generic test-taxonomy and best-practices padding, and a 300+ line monolithic file that would benefit from splitting reference material into bundle files.

Suggestions

Trim the generic edge-case list and "Best Practices" section — Claude already knows standard test edge cases and comment etiquette — and drop the "When to Activate" section in favor of moving that trigger guidance into the description.

Split the Direct REST API reference and comment templates into references/ files (e.g., references/rest-api.md, references/templates.md), keeping SKILL.md as a lean overview with clearly signaled one-level-deep links.

Add a short numbered end-to-end workflow (fetch ticket → analyze → implement → update as work progresses) that ties the MCP, analysis, and update sections into one coherent sequence.

DimensionReasoningScore

Conciseness

The body is mostly efficient — concrete commands, config blocks, and tables — but it includes unnecessary material Claude already knows: the generic edge-case taxonomy ("Invalid inputs... Unauthorized access... Network failures... Concurrent users..."), platitudinous "Best Practices" bullets ("Keep comments concise but informative"), and a "When to Activate" section that restates the description.

3 / 5

Actionability

Fully executable throughout: a copy-paste-ready MCP config JSON, a `jira_curl` helper that keeps credentials off the command line, complete curl+jq pipelines for fetch/comment/transition/search, concrete comment templates, and a troubleshooting table with specific fixes — the common cases are covered.

5 / 5

Workflow Clarity

The "When to Update" table clearly sequences Jira updates across workflow steps, the transition flow has an explicit validation step ("Always call `jira_get_transitions` before transitioning"), and the troubleshooting table provides error-recovery feedback. Minor gap: there is no single end-to-end ordered sequence (fetch → analyze → implement → update) tying the sections together.

4 / 5

Progressive Disclosure

The single file is well organized with clear section headers, but at ~305 lines it inlines substantial reference-style content — the full REST API curl reference and the comment template library — that clearly belongs in separate reference files, and no bundle files (references/, scripts/, assets/) exist at all.

3 / 5

Total

15

/

20

Passed

Description

70%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 specific, distinctive description that clearly names the Jira domain and several concrete actions, written in proper third-person voice. Its main weakness is the complete absence of any 'when to use it' trigger guidance, which caps completeness at 3.

Suggestions

Append a trigger clause such as "Use when fetching or updating Jira tickets, extracting acceptance criteria, commenting on issues, or transitioning ticket status" to satisfy the missing 'when' half of completeness.

Deduplicate the overlapping "updates ticket status" and "transitions issues" phrasing and use the freed space to mention JQL search or issue creation, which the skill body actually supports.

Include one or two natural synonyms such as "Atlassian" or "issue tracking" to broaden natural-language trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("Retrieves Jira tickets, analyzes requirements, updates ticket status, adds comments, or transitions issues"), but "updates ticket status" and "transitions issues" are redundant with each other and JQL search and issue creation are missing — minor gaps in coverage that keep it below the comprehensive anchor 5.

4 / 5

Completeness

The "what" is clearly and concretely stated, but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Jira tickets", "ticket status", "comments", and "issues" are natural terms users would say, giving good keyword coverage; however common variations like "Atlassian", "JQL", "issue tracker", and "sprint" are absent.

4 / 5

Distinctiveness Conflict Risk

"Jira" names a clear niche with distinct triggers, and the mention of "MCP or direct REST API patterns" further scopes it; it is unlikely to trigger for the wrong skill.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

skills/jira-integration/SKILL.md

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.