supportivekoala-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/supportivekoala-automation --openclawSupportivekoala Automation via Rube MCP
Automate Supportivekoala operations through Composio's Supportivekoala toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/supportivekoala
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Supportivekoala connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsupportivekoala - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitsupportivekoala - 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: "Supportivekoala 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 Supportivekoala task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["supportivekoala"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Supportivekoala-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit supportivekoala |
| 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/supportivekoala-automation/SKILL.mdView on GitHub Overview
Automate Supportivekoala operations through Composio's Supportivekoala toolkit via Rube MCP. It enforces discovering current tool schemas first and validating an ACTIVE connection before running tools, reducing errors and keeping workflows aligned with the latest definitions.
How This Skill Works
You discover available tools with RUBE_SEARCH_TOOLS, then verify your Supportivekoala connection with RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, always including memory and the correct session. Tools must be invoked using the exact input schemas returned by the discovery step.
When to Use It
- Starting a new Supportivekoala workflow that requires a discovered tool slug
- When tool schemas may have changed and you must fetch current slugs
- When you need to validate an ACTIVE connection before execution
- When reusing a session_id across multiple steps in a workflow
- When performing a batch or bulk execution with RUBE_REMOTE_WORKBENCH
Quick Start
- Step 1: Verify RUBE_SEARCH_TOOLS is available and discover tools.
- Step 2: Connect the toolkit with RUBE_MANAGE_CONNECTIONS and confirm ACTIVE status.
- Step 3: Execute the discovered tool with RUBE_MULTI_EXECUTE_TOOL, including a memory object, and reuse or create a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas
- Ensure RUBE_MANAGE_CONNECTIONS reports ACTIVE before any execution
- Use exact field names and types from the search results
- Always include memory in RUBE_MULTI_EXECUTE_TOOL, even if empty
- Reuse session IDs within a workflow or generate new ones for separate runs
Example Use Cases
- Discover available Supportivekoala tools with RUBE_SEARCH_TOOLS, then execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using the required input schema.
- Set up and verify an ACTIVE connection using RUBE_MANAGE_CONNECTIONS before running any workflows.
- Reuse a session_id across steps to maintain context in a Supportivekoala automation.
- If tool schemas change, re-run RUBE_SEARCH_TOOLS to obtain updated slugs and arguments.
- Inspect full tool schemas via RUBE_GET_TOOL_SCHEMAS when integrating a new tool.
