ravenseotools-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/ravenseotools-automation --openclawRavenseotools Automation via Rube MCP
Automate Ravenseotools operations through Composio's Ravenseotools toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/ravenseotools
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Ravenseotools connection via
RUBE_MANAGE_CONNECTIONSwith toolkitravenseotools - 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 toolkitravenseotools - 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: "Ravenseotools 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 Ravenseotools task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["ravenseotools"]
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 Ravenseotools-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit ravenseotools |
| 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/ravenseotools-automation/SKILL.mdView on GitHub Overview
Automate Ravenseotools operations through Composio's Ravenseotools toolkit via Rube MCP. This skill emphasizes discovering current tool schemas before execution and requires an active Ravenseotools connection to run workflows. Following these steps helps adapt to schema changes and reduces errors.
How This Skill Works
The workflow starts by discovering available Ravenseotools tasks with RUBE_SEARCH_TOOLS to fetch current tool schemas. It then verifies an ACTIVE connection via RUBE_MANAGE_CONNECTIONS and finally executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and a memory payload. Commands rely on exact fields from the search results to ensure schema compliance and reliable execution.
When to Use It
- When you need to automate Ravenseotools workflows end-to-end via MCP
- When tool schemas change and you must re-discover before execution
- When you must verify the Ravenseotools connection is ACTIVE before running
- When orchestrating multi-tool runs in a single session
- When performing bulk or remote operations with run_composio_tool
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["ravenseotools"] and ensure the connection is ACTIVE
- Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current schemas
- Verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
- Use exact field names and types from the search results; do not hardcode slugs
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls (empty object if no data)
- Reuse session IDs within a workflow and generate new ones for new workflows
Example Use Cases
- Discover Ravenseotools tools for a given use case and pick a slug
- Establish a Rube MCP connection to Ravenseotools and confirm ACTIVE
- Execute a discovered tool slug with the proper arguments
- Perform a bulk operation via RUBE_REMOTE_WORKBENCH using run_composio_tool
- Handle pagination tokens while fetching tool schemas during discovery
