atlassian

Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via MCP server (recommended) or API token authentication (fallback).

1.61x

Quality

84%

Does it follow best practices?

Impact

95%

1.61x

Average score across 2 eval scenarios

Securityby

Low

Low-risk findings worth noting

Quality

Content

76%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 CLI skill body with copy-paste commands and clean sections, held back by a lack of explicit validation checkpoints after destructive Jira/Confluence mutations and minor duplication from the reference tables.

Suggestions

Add an explicit verify/re-read step after destructive operations (e.g., run 'python scripts/jira.py get DEV-123' after create/update/transition to confirm the change applied) to lift workflow_clarity above the cap of 3.

Resolve the 'pip install -r requirements.txt' reference — either include requirements.txt in the bundle or replace with a concrete pip install line listing the actual dependencies.

Drop or trim the 'Operations Reference' tables since the same commands and required args already appear in the per-command sections above, reclaiming tokens without losing information.

Dimension	Reasoning	Score
Conciseness	Largely lean command examples with no over-explanation of concepts Claude already knows, but the 'Operations Reference' tables duplicate the per-command examples already shown above, adding tokens that could be trimmed.	4 / 5
Actionability	Copy-paste-ready CLI commands with realistic arguments cover the common cases ('python scripts/jira.py search "project = DEV AND status = Open"', 'python scripts/jira.py create --project DEV --summary "Fix login bug" --type Bug'), matching the fully-executable top anchor.	5 / 5
Workflow Clarity	Setup is sequenced (OAuth vs API token, status, logout) and backend selection is explained, but destructive/batch operations (create, update, transition, delete-like actions) have no explicit post-operation validation checkpoints, so per the rubric cap workflow_clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Clear sectioned overview (Setup, Backend Selection, Jira, Confluence, Operations Reference, Token Management) with one-level-deep script references (scripts/auth.py, jira.py, confluence.py) that are real bundle files, but 'requirements.txt' is referenced and not present in the bundle and the reference tables duplicate inline content.	4 / 5
	Total	16 / 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 well-crafted description that is specific, third-person, and explicitly pairs a 'what' statement with a numbered 'Use when' trigger list covering both Jira and Confluence. Only minor missing synonyms keep trigger quality off the top.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across both products — 'searching/creating/updating Jira issues with JQL', 'searching/reading/creating Confluence pages with CQL', 'managing Jira workflows, transitions, and comments', 'browsing Confluence spaces and page hierarchies' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers 'what' ('Manage Jira issues and Confluence wiki pages in Atlassian Cloud') and 'when' with a numbered 'Use when: (1)...(4)' clause of concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Strong natural keywords ('Jira issues', 'Confluence wiki pages', 'JQL', 'CQL', 'workflows', 'transitions', 'comments', 'spaces', 'page hierarchies') but a few common synonyms users might say ('tickets', 'docs', 'wiki') are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to Atlassian Cloud with JQL/CQL trigger language, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: sanjay3290/ai-skills
Path: skills/atlassian/SKILL.md
Commit: 281d88d

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.