Do I need API keys to use Appcircle automation?

No. Add the Rube MCP endpoint (https://rube.app/mcp); no API keys are required.

How do I know a connection is ready?

Check RUBE_MANAGE_CONNECTIONS for the ACTIVE status before executing any tools.

Why call RUBE_SEARCH_TOOLS first?

Tool schemas change over time. Fetching current slugs and input schemas prevents broken runs and ensures compatibility.

appcircle-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/appcircle-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Appcircle Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/appcircle

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["appcircle"]
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 Appcircle-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `appcircle`
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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/appcircle-automation/SKILL.mdView on GitHub

Overview

Automate Appcircle operations through Composio's Appcircle toolkit via Rube MCP. Always search tools first to fetch current tool schemas and avoid stale slugs or arguments, then execute workflows.

How This Skill Works

Connect to Rube MCP and verify RUBE_SEARCH_TOOLS is available. Retrieve current Appcircle tool schemas with RUBE_SEARCH_TOOLS, then select a tool slug and execute it with RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments, a memory map, and a session_id. Ensure the connection status is ACTIVE before running workflows and reuse sessions when appropriate.

When to Use It

When you need to automate Appcircle operations without manual GUI steps
When tool schemas change and you must fetch the latest definitions before executing
When integrating Appcircle tasks into automated pipelines with consistent sessions
When validating or running multiple Appcircle tools in a single workflow
When diagnosing issues by re-running tools with known, schema-compliant inputs

Quick Start

Step 1: Add Rube MCP endpoint (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds
Step 2: Discover tools with RUBE_SEARCH_TOOLS using your Appcircle use_case and note the tool_slugs
Step 3: Execute a tool via RUBE_MULTI_EXECUTE_TOOL with the discovered slug, proper arguments, memory, and a session_id

Best Practices

Always run RUBE_SEARCH_TOOLS before any execution to get current tool slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the appcircle toolkit before executing tools
Use exact field names and types from the discovered tool schemas; avoid hardcoding
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs for related workflows and handle pagination tokens from tool searches

Example Use Cases

Nightly Appcircle deployment: discover tools with RUBE_SEARCH_TOOLS, then execute the deploy tool using a shared session
Update Appcircle configurations by fetching current schemas and applying changes via RUBE_MULTI_EXECUTE_TOOL
Batch health checks: run several Appcircle status tools in a single session for faster validation
Environment patch: reuse a session to apply multiple small changes across environments
On-demand remediation: connect, discover, then run a remediation tool with schema-validated inputs

Frequently Asked Questions

Add this skill to your agents