CtrlK
BlogDocsLog inGet started
Tessl Logo

atlassian-automation

Automate Atlassian tasks via Rube MCP (Composio). Always search tools first for current schemas.

52

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/atlassian-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

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

The content is well-structured and actionable with concrete tool-call examples, but it repeats the search-first directive several times and lacks verification feedback loops around the batch execution step. Tightening the repetition and adding a post-execute validation checkpoint would materially improve it.

Suggestions

Consolidate the "always call RUBE_SEARCH_TOOLS first" guidance into one authoritative location (e.g. Tool Discovery) and reference it rather than restating it in four sections.

Add a validation/feedback loop after RUBE_MULTI_EXECUTE_TOOL: check the response for errors or pagination tokens, retry on failure, and confirm completion before proceeding.

Provide one complete end-to-end worked example (search → connect → execute with realistic field names) to lift actionability toward copy-paste readiness.

DimensionReasoningScore

Conciseness

The body is mostly lean with no conceptual padding, but the "search tools first" directive is repeated across Prerequisites, Setup, Tool Discovery, Core Workflow Step 1, and Known Pitfalls, which could be tightened.

3 / 5

Actionability

Code blocks show concrete tool calls with real parameters and a quick-reference table maps operations to approaches; remaining placeholders (session_id, tool_slug) are inherent to dynamic schemas rather than gaps.

4 / 5

Workflow Clarity

The Discover→Connect→Execute sequence is clear with connection validation, but the batch RUBE_MULTI_EXECUTE_TOOL step lacks post-execution verification, and the rubric caps batch/destructive workflows without validation at 3.

3 / 5

Progressive Disclosure

No bundle files exist; the skill is a single self-contained file with well-organized sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference) and only minor redundancy.

4 / 5

Total

14

/

20

Passed

Description

57%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description states a clear, distinct purpose but omits explicit trigger guidance and the natural product names (Jira/Confluence) users would invoke. It is concise but stops just short of being fully actionable as a routing signal.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when the user asks to automate Jira or Confluence tasks such as creating tickets, updating issues, or managing pages."

Include the product synonyms users actually say (Jira, Confluence) alongside "Atlassian" so the skill routes on natural language.

Replace the generic "Automate Atlassian tasks" with 1-2 specific concrete actions (e.g. "create and update Jira issues, manage Confluence pages").

DimensionReasoningScore

Specificity

Names the domain ("Automate Atlassian tasks via Rube MCP") and one concrete action ("search tools first for current schemas"), but the capability description stays generic and is not comprehensive.

3 / 5

Completeness

There is a clear "what" (automate Atlassian tasks via Rube MCP) but no "Use when..." trigger clause, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

"Atlassian" is a relevant natural keyword, but common variations users actually say (Jira, Confluence) are missing, so coverage has gaps.

3 / 5

Distinctiveness Conflict Risk

The Rube MCP (Composio) + Atlassian niche is distinct with minimal overlap risk against other skills.

5 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
ComposioHQ/awesome-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.