atlassian-automation
Automate Atlassian tasks via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:ComposioHQ/awesome-claude-skills --skill atlassian-automationOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
22%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 description is too vague to effectively guide skill selection. It lacks specific capabilities (what Atlassian actions can be performed), natural trigger terms users would say (Jira, Confluence, tickets), and explicit 'Use when' guidance. The procedural note about searching tools first is implementation detail rather than helpful selection criteria.
Suggestions
Add specific Atlassian capabilities like 'Create and update Jira issues, manage sprints, search tickets, work with Confluence pages'
Include natural trigger terms users would say: 'Jira', 'Confluence', 'tickets', 'issues', 'sprints', 'boards', 'epics'
Add explicit trigger guidance: 'Use when the user mentions Jira, Confluence, Atlassian products, or needs to manage project tracking and documentation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Atlassian tasks' without specifying what tasks (create issues, manage sprints, update tickets, etc.). 'Always search tools first' is procedural guidance, not a capability description. | 1 / 3 |
Completeness | Partially addresses 'what' (automate Atlassian tasks) but very weakly. Completely missing a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Atlassian' and 'Rube MCP' which are relevant but misses natural user terms like 'Jira', 'Confluence', 'tickets', 'issues', 'sprints', 'boards' that users would actually say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Atlassian' and 'Rube MCP (Composio)' provide some distinctiveness, but 'automate tasks' is generic enough to potentially conflict with other automation or Atlassian-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
73%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 that efficiently communicates how to use Rube MCP for Atlassian automation. Its strengths are conciseness and organization, but it could improve actionability with more concrete examples and add validation/error handling steps to the workflow for robustness.
Suggestions
Add a complete, executable example showing a real Atlassian operation (e.g., creating a Jira issue) with actual tool slugs and filled-in arguments
Include validation steps in the workflow: what to check after tool execution, how to handle errors, and when to retry
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what Atlassian or MCP are. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter structures, but examples are pseudocode-like rather than fully executable. The argument placeholders and comments reduce copy-paste readiness. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow pattern with logical sequencing, but lacks explicit validation checkpoints. No guidance on what to do if tool execution fails or returns errors, and no feedback loop for error recovery. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, external toolkit docs linked upfront, and a quick reference table for navigation. Content is appropriately scoped for a single SKILL.md file without needing additional files. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.