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.
95
100%
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 an excellent skill description that hits all the marks. It uses third person voice, provides specific concrete actions, includes comprehensive trigger terms that users would naturally say, explicitly states when to use it, and carves out a distinct niche around Atlassian product integration that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: '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', 'debugging Atlassian API integrations'. | 3 / 3 |
Completeness | Clearly answers both what ('Integrates with Atlassian products to manage project tracking and documentation') AND when with explicit 'Use when...' clause listing specific trigger scenarios like querying issues, creating tickets, managing sprints, etc. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Jira', 'Confluence', 'JQL', 'CQL', 'tickets', 'sprints', 'backlogs', 'Atlassian', 'custom fields', 'documentation'. These are terms users naturally use when working with these tools. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused on Atlassian ecosystem (Jira, Confluence) with specific technical terms (JQL, CQL, MCP protocol) that are unlikely to conflict with other skills. The combination of product names and query languages creates a distinct trigger profile. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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-crafted skill that exemplifies best practices: it's concise yet comprehensive, provides executable examples, includes clear validation checkpoints for risky operations, and uses progressive disclosure effectively through a reference table. The constraints section with MUST DO/MUST NOT DO lists provides clear guardrails without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows (like what Jira or Confluence are). Every section provides actionable information without padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable JQL/CQL queries, complete JSON configuration for MCP server setup, and specific examples that are copy-paste ready. The guidance is concrete with real syntax rather than pseudocode. | 3 / 3 |
Workflow Clarity | The 6-step core workflow is clearly sequenced with explicit validation checkpoints (step 3: validate with maxResults=1, step 5: verify permissions with read-only probe). The constraints section reinforces validation and confirmation requirements for risky operations. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear reference table pointing to one-level-deep topic files. Quick-start examples are inline for immediate use, while detailed guidance is appropriately deferred to reference documents with clear loading conditions. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
5b76101
- 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.