codereadr-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/codereadr-automation --openclawCodereadr Automation via Rube MCP
Automate Codereadr operations through Composio's Codereadr toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/codereadr
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Codereadr connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcodereadr - 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 toolkitcodereadr - 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: "Codereadr 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 Codereadr task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["codereadr"]
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 Codereadr-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit codereadr |
| 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/codereadr-automation/SKILL.mdView on GitHub Overview
Automate Codereadr operations through Composio's Codereadr toolkit via Rube MCP. The workflow relies on discovering current tool schemas before running any task and requires an active Codereadr connection. This approach prevents hardcoding slugs or arguments and keeps tooling in sync with updates.
How This Skill Works
First, fetch available Codereadr tools with RUBE_SEARCH_TOOLS to obtain up-to-date tool slugs and input schemas. Then verify the Codereadr connection using RUBE_MANAGE_CONNECTIONS and ensure the session is ACTIVE. Finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, exact arguments, and an explicit memory object.
When to Use It
- When you need to automate a Codereadr operation without hardcoding tool slugs or arguments.
- When you have an active Codereadr connection and want to run a workflow end-to-end.
- When tool schemas may change and you must fetch current schemas before each run.
- When performing batch or bulk executions across multiple Codereadr tasks.
- When reusing or sharing a workflow session across steps to improve speed and consistency.
Quick Start
- Step 1: Verify Rube MCP is available (RUBE_SEARCH_TOOLS responds).
- Step 2: Connect to Codereadr (RUBE_MANAGE_CONNECTIONS with toolkits ['codereadr'] and ensure ACTIVE).
- Step 3: Execute a tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, proper arguments, memory, and session_id.
Best Practices
- Always search tools first to get current slugs and input schemas.
- Before executing, verify RUBE_MANAGE_CONNECTIONS shows ACTIVE.
- Use exact field names and types from the tool's search results.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and re-open a new session for new runs.
Example Use Cases
- Automate a Codereadr data extraction task across a batch of documents.
- Run a series of Codereadr validations using discovered tool slugs.
- Flow a Codereadr update by connecting, discovering tools, and executing with memory.
- Batch-run multiple Codereadr operations and collect results in a session.
- Refresh tool schemas via RUBE_SEARCH_TOOLS when schema changes are detected.
