This is an excellent skill description that clearly defines its scope around Atlassian/Jira/Confluence operations, lists concrete capabilities (CRUD, search, endpoint discovery, API execution), and provides comprehensive trigger guidance with natural user terms. It follows best practices with third-person voice, explicit 'Use when' and 'Trigger on' clauses, and domain-specific terminology that makes it highly distinguishable.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: create, read, update, delete, search Jira/Confluence resources, endpoint discovery, payload construction, and authenticated API execution. These are specific, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (execute Jira/Confluence operations including CRUD, search, endpoint discovery, payload construction, API execution) and 'when' (explicit 'Use when' and 'Trigger on' clauses with specific trigger conditions).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: Jira, Confluence, Atlassian, tickets, epics, sprints, backlogs, wiki pages, and 'Atlassian workflows'. These are terms users would naturally use when requesting help with these tools.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche around Atlassian products. The specific mention of Jira, Confluence, and Atlassian-specific concepts like epics, sprints, backlogs, and wiki pages makes it very unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

92%

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

This is a high-quality skill that provides clear, actionable, and well-structured guidance for executing Atlassian API operations. The workflow is well-sequenced with appropriate validation steps, security constraints are explicit, and the content respects Claude's intelligence by avoiding unnecessary explanations. The only minor weakness is that the content is moderately long for a single file, though the logical section organization partially compensates for this.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It avoids explaining what Jira or Confluence are, assumes Claude understands REST APIs, authentication patterns, and JSON construction. Every section serves a clear purpose with no padding or unnecessary context.	3 / 3
Actionability	Provides concrete, executable commands (e.g., the exact `uv run` invocation with flags), specific tool names to call (`atlassian-endpoint-resolver`, `atlassian-rich-text-formatter`, `atlassian-browser-authentication`), and precise rules for authentication modes. The guidance is specific enough to be directly followed.	3 / 3
Workflow Clarity	The 8-step workflow is clearly sequenced with explicit validation checkpoints: checking for missing fields before proceeding (step 4), formatting rich text before body construction (step 5), and a retry loop on 401 errors in Mode B authentication. The preconditions section adds further guardrails, and the output section handles failure cases explicitly.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections (Inputs, Preconditions, Workflow, Authentication, Request Construction, Sub-Agent Rules, Output), but everything is in a single file. Given the complexity and length (~80+ lines of substantive content), some sections like Request Construction details or Authentication modes could benefit from being split into referenced files. However, no bundle files are provided, so this is evaluated in isolation.	2 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

1 day ago

Table of Contents

Discovery Implementation Validation