Do I need API keys to use spondyr-automation?

No. You simply add the Rube MCP endpoint (e.g., https://rube.app/mcp) as an MCP server in your client configuration.

Why do I have to call RUBE_SEARCH_TOOLS first?

Tool schemas change over time. Always querying for current tool slugs and input schemas prevents broken integrations.

What ensures a successful run?

Ensure the Spondyr connection is ACTIVE via RUBE_MANAGE_CONNECTIONS and include a memory payload in every RUBE_MULTI_EXECUTE_TOOL call; reuse session IDs within a workflow.

spondyr-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Spondyr Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/spondyr

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["spondyr"]
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 Spondyr-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `spondyr`
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/spondyr-automation/SKILL.mdView on GitHub

Overview

Automate Spondyr operations by connecting to Composio's Spondyr toolkit through Rube MCP. It emphasizes discovering current tool schemas before execution to avoid broken integrations. Useful for streamlining repetitive Spondyr workflows and reducing manual setup.

How This Skill Works

First, discover available tools with RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Then verify and establish an ACTIVE connection using RUBE_MANAGE_CONNECTIONS with the spondyr toolkit, and finally execute tools with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and the current session_id. Always include memory and reuse sessions per workflow.

When to Use It

When automating routine Spondyr operations and need current tool schemas
When starting a new workflow and tool slugs are unknown
When validating an ACTIVE connection before execution
When performing multi-step executions that require session continuity
When tool schemas evolve or you need to handle pagination during discovery

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to verify available Spondyr tools and schemas.
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit 'spondyr' and start your workflow using RUBE_MULTI_EXECUTE_TOOL.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Discover tools for a Spondyr task, then execute a tool slug with proper arguments.
Set up and verify an ACTIVE Spondyr connection before running a workflow.
Run a multi-tool operation using RUBE_MULTI_EXECUTE_TOOL with session_id.
Handle tool schema changes by re-running RUBE_SEARCH_TOOLS instead of hardcoding slugs.
Process paginated tool results until all tools are discovered.

Frequently Asked Questions

Add this skill to your agents