CtrlK
BlogDocsLog inGet started
Tessl Logo

jira-automation

Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.

61

Quality

72%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/jira-automation/SKILL.md

The canonical home for this skill is jira-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable guide with concrete tool sequences, parameters, and pitfalls across five core workflows; its main weaknesses are purposeful content duplication and the absence of explicit post-operation verification steps.

Suggestions

De-duplicate the pitfalls: keep them only in the per-workflow sections or only in the consolidated 'Known Pitfalls' section, not both.

Add an explicit verify step after create/edit/assign/move workflows (e.g., call JIRA_GET_ISSUE to confirm the change landed) to strengthen feedback loops.

Consider moving the Quick Reference table into a separate references file to tighten the SKILL.md overview and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no basic concept explanations), but pitfalls are duplicated per workflow and again in a consolidated 'Known Pitfalls' section, and the Quick Reference table repeats tool slugs already listed inline.

4 / 5

Actionability

Concrete tool slugs with [Required]/[Optional]/[Prerequisite] markers and example values (e.g., `project = PROJ AND status = "In Progress"`) give mostly executable guidance; minor gaps include no full ADF payload or account-ID examples.

4 / 5

Workflow Clarity

Setup is a numbered sequence with an explicit validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows'); core create/edit workflows list clear tool sequences but lack explicit verify-after steps, and the operations are non-destructive (no deletes) so the destructive cap does not apply.

4 / 5

Progressive Disclosure

Single well-organized SKILL.md with clearly labeled sections (Prerequisites, Setup, five Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) and no external bundle files; the Quick Reference table is borderline content that could be split out but is reasonable inline.

4 / 5

Total

16

/

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.

The description clearly conveys what the skill does and names a broad set of Jira entities, but it lacks an explicit 'when to use' trigger clause and carries implementation jargon ('Rube MCP (Composio)', 'search tools first') that is not user-facing.

Suggestions

Add an explicit 'Use when...' clause naming user-facing triggers (e.g., 'Use when the user asks to create, search, or update Jira issues, sprints, or comments').

Replace or soften the jargon 'Rube MCP (Composio)' with user-natural language, and drop the implementation guidance 'Always search tools first for current schemas' from the description into the body.

Add common synonyms like 'tickets' and 'backlog' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (Jira automation via Rube MCP/Composio) and enumerates concrete targets — 'issues, projects, sprints, boards, comments, users' — but the verb 'Automate' is generic and lacks per-entity action verbs, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no explicit 'Use when...' trigger clause; per the judging guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('Jira', 'issues', 'sprints', 'boards', 'comments') but leans on jargon 'Rube MCP (Composio)' and omits common synonyms like 'tickets' and 'backlog'.

4 / 5

Distinctiveness Conflict Risk

Scoped to a distinct niche — Jira operations through the Rube MCP/Composio toolkit — with trigger terms unlikely to fire for unrelated skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.