Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
42%This skill has strong organizational structure and progressive disclosure, with clear navigation to detailed references. However, it severely lacks actionability - there are no concrete code examples, JQL/CQL queries, or configuration snippets that Claude could immediately use. The skill reads more like a table of contents than executable guidance.
Suggestions
Add at least 2-3 concrete JQL query examples inline (e.g., `project = PROJ AND status = 'In Progress' AND assignee = currentUser()`)
Include a minimal MCP server configuration JSON snippet showing authentication setup
Add a concrete tool call example with error handling code that demonstrates the workflow
Integrate validation checkpoints into the Core Workflow steps (e.g., 'Validate query syntax before execution' as an explicit numbered step)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'Role Definition' that restates obvious context, and 'Knowledge Reference' which lists concepts Claude already knows. The constraints section is valuable but could be more compact. | 2 / 3 |
Actionability | The skill lacks concrete, executable code examples. It describes what to do ('Write JQL for Jira', 'Configure OAuth 2.1') but provides no actual JQL examples, no configuration snippets, no tool call implementations. Everything is delegated to reference files without any inline executable guidance. | 1 / 3 |
Workflow Clarity | The 5-step core workflow provides a clear sequence, but lacks validation checkpoints. For operations involving production data updates, there's no explicit validate-before-execute pattern. The 'test with read-only operations first' constraint hints at validation but isn't integrated into the workflow steps. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-organized reference table pointing to specific topic files. References are one level deep, clearly signaled with a helpful 'Load When' column explaining when to access each reference. | 3 / 3 |
Total | 8 / 12 Passed |
Activation
72%The description has strong trigger terms and distinctiveness due to specific product names (Jira, Confluence, Atlassian), making it easy to identify when this skill should be used. However, it's structured only as a 'Use when' clause without first explaining what the skill actually does, and the listed capabilities are somewhat generic rather than detailing specific concrete actions.
Suggestions
Add a leading 'what' statement before the 'Use when' clause, e.g., 'Integrates with Atlassian tools to query Jira issues, search Confluence pages, create and update tickets, and manage documentation.'
Expand specificity with more concrete actions like 'assign tickets', 'add comments', 'transition issue status', 'create Confluence spaces', 'attach files to issues'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jira, Confluence, Atlassian) and lists some actions (querying issues, searching pages, creating tickets, updating documentation), but the actions are somewhat generic and not comprehensive - doesn't specify concrete capabilities like 'assign tickets', 'add comments', 'link pages', etc. | 2 / 3 |
Completeness | Has a 'Use when' clause which is good, but the description only covers 'when' - it lacks a clear 'what does this do' statement explaining the skill's capabilities before the trigger guidance. The structure is inverted. | 2 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'Jira', 'issues', 'Confluence', 'pages', 'tickets', 'documentation', 'Atlassian'. These are terms users naturally use when working with these tools. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche with specific product names (Jira, Confluence, Atlassian) and MCP protocol mention. Unlikely to conflict with other skills due to the specific tooling references. | 3 / 3 |
Total | 10 / 12 Passed |
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.