atlassian-mcp
Integrates with Atlassian products to manage project tracking and documentation via MCP protocol. Use when querying Jira issues with JQL filters, creating and updating tickets with custom fields, searching or editing Confluence pages with CQL, managing sprints and backlogs, setting up MCP server authentication, syncing documentation, or debugging Atlassian API integrations.
92
92%
Does it follow best practices?
Impact
90%
1.12xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a strong skill description that clearly defines its scope around Atlassian product integration via MCP protocol. It excels in all dimensions by listing specific concrete actions, including natural trigger terms users would use, providing explicit 'Use when' guidance with multiple scenarios, and maintaining a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: querying Jira issues with JQL filters, creating/updating tickets with custom fields, searching/editing Confluence pages with CQL, managing sprints and backlogs, setting up MCP server authentication, syncing documentation, and debugging Atlassian API integrations. | 3 / 3 |
Completeness | Clearly answers both 'what' (integrates with Atlassian products for project tracking and documentation via MCP) and 'when' with an explicit 'Use when...' clause listing seven specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Jira', 'Confluence', 'JQL', 'CQL', 'tickets', 'sprints', 'backlogs', 'Atlassian', 'MCP', 'custom fields', 'documentation'. These are all terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Atlassian-specific (Jira + Confluence) via MCP protocol. The combination of product names (Jira, Confluence), query languages (JQL, CQL), and MCP protocol makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and excellent progressive disclosure through its reference table. The workflow is clear with appropriate validation checkpoints for destructive operations. The main weakness is moderate verbosity in the 'When to Use' section and constraints lists, which include guidance Claude would already know.
Suggestions
Remove or significantly trim the 'When to Use This Skill' section since it duplicates the skill description and frontmatter triggers.
Trim the MUST DO/MUST NOT DO lists to only non-obvious constraints specific to Atlassian MCP integration, removing general best practices Claude already knows (e.g., 'don't hardcode secrets', 'implement error recovery').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary items like the 'When to Use This Skill' section which largely duplicates the skill description, and the Output Templates section is vague filler. The MUST DO/MUST NOT DO lists contain some items Claude would already know (e.g., 'don't hardcode secrets', 'handle rate limits'). | 2 / 3 |
Actionability | Provides concrete, copy-paste ready JQL/CQL query examples, a complete MCP server JSON configuration, and specific validation techniques (maxResults=1 probe). The examples are executable and immediately useful. | 3 / 3 |
Workflow Clarity | The core workflow is clearly sequenced with explicit validation checkpoints: validate queries with maxResults=1 before full execution, verify permissions with read-only probes before writes, and confirm before bulk operations. Error recovery and feedback loops are addressed in both the workflow and constraints. | 3 / 3 |
Progressive Disclosure | Excellent use of a reference table with clear 'Load When' guidance for five separate reference files. The main skill provides a concise overview with quick-start examples while deferring detailed guidance to one-level-deep references. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
3d95bb1
- 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.