How do I ensure tool schemas are up-to-date?

Always call RUBE_SEARCH_TOOLS before executing to fetch current schemas.

What if the Spoki connection shows not ACTIVE?

Follow the auth link provided by the tool to complete setup and re-check ACTIVE.

Do I need to include memory in every execution?

Yes, memory must be included in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.

spoki-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Spoki Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/spoki

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Spoki operations through Composio's Spoki toolkit via Rube MCP. It streamlines discovering available Spoki tools, managing connections, and executing tool workflows with proper session handling. Always fetch current tool schemas before running to stay aligned with updates.

How This Skill Works

Workflows begin by discovering tools with RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Then use RUBE_MANAGE_CONNECTIONS to connect to the spoki toolkit and verify ACTIVE. Finally, execute tools with RUBE_MULTI_EXECUTE_TOOL, providing the discovered slug, arguments, memory, and session_id.

When to Use It

When you need to run a Spoki operation defined by the latest tool schema
When integrating Spoki tasks into a larger Composio workflow
When setting up a new Spoki connection or re-verifying an existing one
When you need to run multiple Spoki tools in a single session
When tool schemas may have changed and you must re-scan before execution

Quick Start

Step 1: RUBE_SEARCH_TOOLS to fetch current Spoki tool schemas (use_case: Spoki operations; session: generate_id: true)
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ["spoki"] and the produced session_id; verify status is ACTIVE
Step 3: RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug, the required arguments, memory: {} and the same session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before execution to fetch current tool schemas
Verify the Spoki connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before running
Use exact field names and types from the search results
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs for a workflow and generate new ones for new workflows

Example Use Cases

Discover a Spoki tool and execute it in a single session using the discovered tool_slug and arguments
Connect to Spoki via RUBE_MANAGE_CONNECTIONS and then run two tools sequentially in one session
Re-scan tool schemas after a Spoki task update and re-run the workflow with updated arguments
Validate that the Spoki connection is ACTIVE before triggering a tool execution
Bulk run multiple Spoki tasks through a remote bench workflow using the discovered tools

Frequently Asked Questions

Add this skill to your agents