This is a strong skill description that clearly articulates what the skill does (resolves Atlassian API endpoints), when to use it (when identifying which endpoints fulfill a user's Atlassian-related intent, especially when an 'operation' field is present), and includes rich trigger terms spanning Jira and Confluence domains. It uses proper third-person voice and is both specific and distinctive.

Dimension	Reasoning	Score
Specificity	The description lists a concrete action ('Resolves the best-matching Atlassian API endpoints for a given inferred operation') and enumerates specific domains: Jira issues, projects, boards, sprints, workflows, Confluence pages, spaces, and cross-product Atlassian operations.	3 / 3
Completeness	Clearly answers 'what' (resolves best-matching Atlassian API endpoints for a given operation) and 'when' ('Use this skill whenever the agent needs to identify which Atlassian REST API endpoint(s) can fulfill a user's intent... Always trigger when the input includes an operation field describing an Atlassian action').	3 / 3
Trigger Term Quality	Includes strong natural keywords users and agents would reference: 'Atlassian REST API', 'Jira issues', 'projects', 'boards', 'sprints', 'workflows', 'Confluence pages', 'spaces', 'operation field', and 'cross-product Atlassian operations'. Good coverage of common Atlassian-related terms.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — it targets a very specific niche of resolving Atlassian API endpoints from an operation field. The combination of 'Atlassian REST API endpoint resolution' and the explicit trigger on an 'operation' field makes it unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

62%

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

This skill provides a well-structured, clearly sequenced workflow for resolving Atlassian API endpoints, with a strong scoring rubric and good edge case handling. Its main weaknesses are the lack of executable code examples (no sample input/output, no implementation snippets) and the monolithic structure that could benefit from splitting reference material into separate files. The content is moderately concise but could trim some enumerations and repeated emphasis.

Suggestions

Add a concrete example showing a sample `operation` input and the expected structured output, so Claude has a clear input→output reference to follow.

Include at least one executable code snippet (e.g., fetching a spec URL and extracting paths) to move from prose instructions to actionable implementation guidance.

Extract the API Registry table and synonym mappings into separate reference files to improve progressive disclosure and reduce the main file's length.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably detailed for a complex multi-step process, but includes some unnecessary elaboration. The synonym lists, the exhaustive enumeration of resource nouns and action verbs, and the repeated emphasis on $ref expansion could be tightened. However, much of the content is genuinely instructive for a non-trivial task.	2 / 3
Actionability	The skill provides concrete spec URLs, a detailed scoring table with weights, and a clear threshold, which is good. However, there is no executable code — no example fetch call, no example scoring implementation, no sample input/output. The guidance is specific but remains at the level of detailed prose instructions rather than copy-paste-ready implementations.	2 / 3
Workflow Clarity	The four-step workflow is clearly sequenced (parse → fetch → score → deduplicate/output), with explicit validation-like checkpoints such as the threshold retry mechanism ('lower the threshold and retry'), edge case handling, and a clear output normalization step before returning results. The scoring rubric table and deduplication rules provide strong guardrails.	3 / 3
Progressive Disclosure	The content is a single monolithic file with no references to supporting files, despite being quite long and detailed. The scoring table, synonym mappings, and API registry could reasonably be split into separate reference files. However, the internal structure with clear headers and tables provides decent navigability within the single file.	2 / 3
	Total	9 / 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

9 days ago

Table of Contents

Discovery Implementation Validation