atlassian-tasks
Execute Jira or Confluence operations given an Atlassian URL and task instructions. Use when the user wants to create, read, update, delete, or search Jira/Confluence resources and needs endpoint discovery, payload construction, and authenticated API execution. Trigger on any request mentioning Jira, Confluence, Atlassian, tickets, epics, sprints, backlogs, wiki pages, or related Atlassian workflows.
77
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 clearly defines its scope around Atlassian/Jira/Confluence operations, lists concrete capabilities (CRUD, search, endpoint discovery, payload construction, authenticated API execution), and provides comprehensive trigger guidance with natural user terms. It uses proper third-person voice and is both concise and thorough.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: create, read, update, delete, search Jira/Confluence resources, endpoint discovery, payload construction, and authenticated API execution. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (execute Jira/Confluence operations including CRUD, search, endpoint discovery, payload construction, API execution) and 'when' (explicit 'Use when' clause and 'Trigger on' clause with specific trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: Jira, Confluence, Atlassian, tickets, epics, sprints, backlogs, wiki pages, and 'Atlassian workflows'. These are terms users would naturally use when requesting help with these tools. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around Atlassian products. The specific mention of Jira, Confluence, Atlassian URLs, and domain-specific terms like epics, sprints, backlogs makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides clear, actionable, and well-structured guidance for executing Atlassian API operations. The workflow is well-sequenced with appropriate validation checkpoints, error handling, and security constraints around credential handling. The only notable weakness is that all content is inline in a single file, which for a skill of this complexity could benefit from some progressive disclosure into supporting reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Jira or Confluence are, assumes Claude understands REST APIs, authentication patterns, and JSON construction. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, executable command patterns (e.g., the exact `uv run` invocation with flags), specific tool names to call (`atlassian-endpoint-resolver`, `atlassian-rich-text-formatter`, `atlassian-browser-authentication`), and precise rules for field handling, authentication modes, and body construction. The guidance is specific enough to be directly followed. | 3 / 3 |
Workflow Clarity | The 8-step workflow is clearly sequenced with explicit validation checkpoints: step 4 checks for missing fields and halts, step 6 has a fallback/retry on 401, and the authentication section includes error handling (stop and report). The feedback loop for browser auth retry on 401 is explicitly defined. Rich text formatting is called out as a mandatory pre-step before body construction. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections (Inputs, Preconditions, Workflow, Authentication, Request Construction, Sub-Agent Rules, Output), but it's all in a single file with no references to external documentation. Given the complexity of the skill (multiple tools, authentication modes, pagination, sub-agents), some content like the detailed request construction rules or output formatting could benefit from being split into referenced files. However, no bundle files are provided, so this is evaluated in isolation. | 2 / 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
- freneticdisc/grammaire
- Commit
1ce64c0
- 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.