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

SKILL

abstract-automation

Name: abstract-automation
Author: Composio

Automate Abstract workflows via Rube MCP using current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

Overall this is low risk to caution: it is a prompt-only open-source skill with no local secrets and no declared remote host in the materials, while the main exposure comes from invoking third-party Abstract tools through Rube MCP. No concrete high-risk red flags are evident.

CredentialsLow risk

The material explicitly states no API keys or environment variables are required; no credential collection, hardcoded secrets, or obvious credential misuse risk is shown.

Network egressCaution

No direct remote host is listed in the material, but it uses Rube MCP to reach external tools and Composio/Abstract capabilities, so normal functional network egress is expected.

Code executionCaution

This is a prompt-only skill and does not itself show local process spawning or arbitrary code execution; any execution comes from MCP tool calls, which is standard tool-level capability.

Data accessCaution

The description indicates Abstract-related operations, which may read or modify data in that service; no excessive access to local files or system resources beyond the stated function is shown.

Supply chainCaution

The source is GitHub, the repository is open source, and community stars are high, which lowers supply-chain risk; however, the license is undeclared, maintenance status is unknown, and it depends on the external Rube/Composio chain, so caution remains.

Recommendations

Enable it only when Abstract automation is needed, and minimize granted scope.
Verify the provenance and permission boundaries of the Rube/Composio connection before use.
Avoid passing unnecessary sensitive data into workflows.
If source and license details become public, re-check repository maintenance activity.

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

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Abstract Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/abstract

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Abstract connection via RUBE_MANAGE_CONNECTIONS with toolkit abstract
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 abstract
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: "Abstract 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 Abstract task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["abstract"]
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 Abstract-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `abstract`
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 Writer document and content workflows through Rube MCP efficiently.

ComposioGet→

$ loading_