CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

This is a solid skill with strong actionability — the JQL/CQL examples and MCP server configuration are concrete and immediately useful. The workflow includes proper validation checkpoints for destructive operations. The main weaknesses are moderate verbosity (some sections explain things Claude already knows) and the absence of the referenced bundle files, which undermines the progressive disclosure structure.

Suggestions

Remove or condense the 'When to Use This Skill' section since it duplicates the skill description and wastes tokens.

Trim the MUST DO/MUST NOT DO lists to only non-obvious constraints — items like 'Handle rate limits with exponential backoff' and 'Implement error recovery for network failures' are general engineering knowledge Claude already has.

Provide the referenced bundle files (references/jira-queries.md, references/authentication-patterns.md, etc.) or remove the reference table if they don't exist.

DimensionReasoningScore

Conciseness

Generally efficient but has some unnecessary verbosity — the 'Output Templates' section is vague filler, the 'When to Use This Skill' section largely duplicates the description, and some constraint items explain things Claude already knows (e.g., 'Handle rate limits with exponential backoff', 'Implement error recovery for network failures'). The query examples and config JSON earn their place, but the overall content could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready JQL/CQL query examples, a complete MCP server JSON configuration with environment variable patterns, and specific validation techniques (maxResults=1 probe). The guidance is specific and executable rather than abstract.

3 / 3

Workflow Clarity

The core workflow is clearly sequenced with 6 numbered steps including explicit validation checkpoints — 'validate with maxResults=1 before full execution', 'confirm required scopes with a read-only probe before any write or bulk operation', and 'confirm before any write or bulk operation against production data'. This provides proper feedback loops for risky operations.

3 / 3

Progressive Disclosure

The reference table with 5 topic-specific files and 'Load When' guidance is well-structured for progressive disclosure. However, no bundle files are provided, meaning all referenced files (references/mcp-server-setup.md, references/jira-queries.md, etc.) are missing. The skill promises depth it cannot deliver, and the inline content tries to compensate but creates an awkward middle ground.

2 / 3

Total

10

/

12

Passed

Description

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 excels across all dimensions. It provides specific concrete actions, includes natural trigger terms that users would actually say, has an explicit 'Use when' clause with comprehensive trigger scenarios, and is clearly distinguishable from other skills through its Atlassian/MCP focus. The description is well-structured and concise without unnecessary padding.

DimensionReasoningScore

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 to manage project tracking and documentation via MCP) and 'when' (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 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

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
Jeffallan/claude-skills
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.