ritekit-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/ritekit-automation --openclawRitekit Automation via Rube MCP
Automate Ritekit operations through Composio's Ritekit toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/ritekit
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Ritekit connection via
RUBE_MANAGE_CONNECTIONSwith toolkitritekit - 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 toolkitritekit - 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: "Ritekit 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 Ritekit task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["ritekit"]
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 Ritekit-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit ritekit |
| 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/ritekit-automation/SKILL.mdView on GitHub Overview
Automates Ritekit operations through Composio's Ritekit toolkit using Rube MCP. It emphasizes discovering current tool schemas first with RUBE_SEARCH_TOOLS to stay in sync with changes and requires an ACTIVE Ritekit connection before workflows run.
How This Skill Works
The process starts by confirming RUBE_SEARCH_TOOLS is available to fetch current Ritekit tool slugs and input schemas. It then verifies the Ritekit connection via RUBE_MANAGE_CONNECTIONS and, once ACTIVE, executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the proper memory payload and session_id. This pattern ensures up-to-date schemas and safe, repeatable automation.
When to Use It
- When you need to automate a Ritekit operation and must use the latest tool schemas
- When you’re setting up a new Ritekit workflow and should validate the ACTIVE connection first
- When tool schemas change and you must fetch current slugs before execution
- When reusing a session for a multi-step Ritekit task within one workflow
- When performing bulk Ritekit actions or chaining multiple tools via RUBE_MULTI_EXECUTE_TOOL
Quick Start
- Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'ritekit' and ensure ACTIVE status
- Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then execute via RUBE_MULTI_EXECUTE_TOOL with a valid session_id
Best Practices
- Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and schemas
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
- Use exact field names and types from the search results; avoid hardcoding
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
- Reuse session IDs for a workflow; generate new ones for new workflows and watch for pagination
Example Use Cases
- Discover Ritekit tools and immediately run a chosen slug with required arguments in a single session
- Update an ongoing Ritekit automation after a tool schema change without manual edits
- Establish Ritekit connection, verify ACTIVE, then fetch analytics via a tool
- Execute multiple Ritekit tools in one session using RUBE_MULTI_EXECUTE_TOOL with preserved memory
- Execute batch Ritekit tasks through RUBE_REMOTE_WORKBENCH using run_composio_tool for bulk operations
