$ ~/registry/skill/composiohq-composio-skills-atlassian-automation

SKILL

atlassian-automation

Name: atlassian-automation
Author: Composio

Automate Atlassian tasks and workflows through Rube MCP integrations.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill appears to be a prompt-oriented wrapper with no local API key requirement and no stated local code execution or file access. However, it relies on remote Rube MCP/Composio and an Atlassian connection for actual operations, so external platform trust and downstream authorization scope still require attention.

CredentialsCaution

The material says the skill itself requires no local keys, but it does require creating an Atlassian connection via `RUBE_MANAGE_CONNECTIONS` and completing external authentication, implying third-party OAuth/account authorization. There is no explicit request to paste secrets into the skill, but tokens may be managed by Rube/Composio, so permission scope should be reviewed.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and executing operations through Composio's Atlassian toolkit. This means task content, parameters, and related business data may be sent to Rube/Composio and then to Atlassian. The endpoint is a declared, relevant service in the material, with no unidentified exfiltration target shown.

Code executionLow risk

The system flags this as `prompt-only`, and the material is mainly workflow guidance. It does not describe starting local processes, running scripts, installing dependencies, or invoking system commands. Based on the provided material, there is no evident local code execution surface.

Data accessCaution

The skill is intended to automate Atlassian operations and, by design, can access user-authorized Atlassian resources (such as issues/projects, depending on the later tool schema and connection scope). The material does not claim local file access or extra data access beyond the Atlassian use case, but external services may process the business content sent to them.

Supply chainLow risk

The source is a GitHub open-source repository, the system marks it as `open-source`, and community adoption is very high (64.9k stars), all of which are strong risk-reducing signals. This appears to be a documentation-style skill included in an open skill collection; although license and maintenance status are not clearly stated, the current material shows no high-risk red flags such as closed-source logic, obvious abandonment, or suspicious injection content.

Recommendations

Review the Atlassian authorization scope before connecting, and prefer a least-privilege or test account.
Confirm your organization allows sending task content to Rube/Composio, and review their data handling and retention policies.
Inspect the actual schema returned by `RUBE_SEARCH_TOOLS` before execution to avoid using high-impact tools unintentionally.
Do not include unnecessary sensitive information in issue content or operation parameters.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "atlassian-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/atlassian-automation/SKILL.md
2. Save it as ~/.claude/skills/atlassian-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Atlassian Automation via Rube MCP

Automate Atlassian operations through Composio's Atlassian toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/atlassian

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Atlassian connection via RUBE_MANAGE_CONNECTIONS with toolkit atlassian
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit atlassian
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Atlassian operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Atlassian task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["atlassian"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Atlassian-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `atlassian`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate Front inbox conversations, contacts, and team workflows via Rube MCP.

ComposioGet→

$ loading_