What is required to start automating Sitespeakai with this skill?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must be available, and there must be an ACTIVE Sitespeakai connection via RUBE_MANAGE_CONNECTIONS using the sitespeakai toolkit.

How do I keep tool schemas current?

Always call RUBE_SEARCH_TOOLS before running workflows to obtain the latest tool slugs, input schemas, and execution plans; never hardcode slugs.

Do I have to pass memory for every tool execution?

Yes. Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}), to maintain state across tools.

sitespeakai-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Sitespeakai Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/sitespeakai

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["sitespeakai"]
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 Sitespeakai-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `sitespeakai`
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/sitespeakai-automation/SKILL.md

View on GitHub

Overview

Automate Sitespeakai operations through Composio's Sitespeakai toolkit via Rube MCP. This skill emphasizes discovering tool schemas first using RUBE_SEARCH_TOOLS and managing a Sitespeakai connection with RUBE_MANAGE_CONNECTIONS to drive automated workflows.

How This Skill Works

Connect Rube MCP to the Sitespeakai toolkit and always surface available tools with RUBE_SEARCH_TOOLS before any run. Use RUBE_MANAGE_CONNECTIONS to ensure an ACTIVE connection, then execute discovered tools with RUBE_MULTI_EXECUTE_TOOL, passing the required arguments and a memory object. This pattern keeps tool schemas current and workflows reproducible.

When to Use It

When starting a Sitespeakai task, always search for current tool schemas first.
When establishing or reusing an active Sitespeakai connection via RUBE_MANAGE_CONNECTIONS.
When executing tools, ensure arguments match the discovered schema exactly and include a memory object.
When handling multiple tools or complex workflows, leverage pagination and session handling to iterate results.
When performing bulk operations, use RUBE_REMOTE_WORKBENCH and run_composio_tool for batch tasks.

Quick Start

Step 1: Configure Rube MCP by adding https://rube.app/mcp as an MCP server in your client; no API keys needed.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Sitespeakai tool schemas and available slugs.
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkit: 'sitespeakai', then execute a discovered tool via RUBE_MULTI_EXECUTE_TOOL, including memory and schema-compliant arguments.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas.
Verify the connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before tool execution.
Use exact field names and types from the discovered tool schemas.
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 Sitespeakai operation and execute a single tool with schema-compliant arguments.
Establish a Sitespeakai connection, then chain multiple tools in a session to complete a workflow.
Perform bulk operations using RUBE_REMOTE_WORKBENCH and run_composio_tool for batch tasks.
Handle paginated tool results by looping RUBE_SEARCH_TOOLS until all tokens are fetched.
Create a new workflow with a fresh session_id for a separate run.

Frequently Asked Questions

Add this skill to your agents