CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

76

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable CLI reference with lean copy-paste commands and correct one-level-deep references to real script files. Its main weakness is the absence of validation/verification checkpoints for destructive operations like transitions and updates.

Suggestions

Add an explicit verification step after state-changing operations (e.g. run 'python scripts/jira.py get DEV-123' after 'transition' or 'update' to confirm the change took effect), which would lift workflow clarity.

Consider consolidating the per-command example blocks and the Operations Reference tables to remove the duplicated command listing and tighten token efficiency.

Document a brief error-recovery/feedback loop for setup failures (e.g. what to do when 'auth.py status' shows no credentials) to make the multi-step setup workflow more robust.

DimensionReasoningScore

Conciseness

The body is a lean reference of executable commands with no concept over-explanation or fluff; it assumes Claude's competence about what Jira/Confluence are. Minor redundancy between the per-command example blocks and the Operations Reference tables keeps it from being perfectly tight, but it is not the level-2 'includes unnecessary explanation' case.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands with real flags and arguments (e.g. 'python scripts/jira.py create --project DEV --summary "Fix login bug" --type Bug'), matching the anchor for concrete, executable guidance.

3 / 3

Workflow Clarity

Setup and backend-selection steps are clearly sequenced, but state-changing operations such as 'update', 'transition', and 'comment' have no validation or verification checkpoints; per the rubric, missing validation for destructive/batch operations caps workflow clarity at 2 rather than 3.

2 / 3

Progressive Disclosure

A single overview SKILL.md is organized into clearly signaled sections (First-Time Setup, Backend Selection, Jira, Confluence, Operations Reference, Token Management) and references one-level-deep real bundle files in scripts/ (jira.py, confluence.py, auth.py verified present), with no nested-reference indirection.

3 / 3

Total

11

/

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.

A strong, third-person description that states concrete capabilities and provides an explicit, enumerated 'Use when' trigger list. It is concise yet complete, with low conflict risk against other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'searching/creating/updating Jira issues with JQL', 'managing Jira workflows, transitions, and comments', and 'browsing Confluence spaces and page hierarchies', matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Clearly answers what ('Manage Jira issues and Confluence wiki pages') and when via an explicit 'Use when:' clause with four numbered triggers, satisfying both requirements.

3 / 3

Trigger Term Quality

Uses natural terms a user would actually say — 'Jira issues', 'Confluence wiki pages', 'Jira workflows', 'Confluence spaces' — giving good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Atlassian Cloud Jira + Confluence) with distinct, product-specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
sanjay3290/ai-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.