Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Codereadr Automation via Rube MCP

agent tool_use skill risk: medium

Codereadr Automation via Rube MCP

Provides instructions for automating Codereadr operations through Composio's Codereadr toolkit using Rube MCP, including prerequisites, setup steps, tool discovery with RUBE_SEARCH…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: codereadr-automation
description: "Automate Codereadr tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Codereadr Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/codereadr](https://composio.dev/toolkits/codereadr)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Codereadr connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `codereadr`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `codereadr`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_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 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](https://composio.dev)*

REQUIRED CONTEXT

  • Rube MCP connection
  • active Codereadr toolkit connection

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit codereadr
  5. If connection is not ACTIVE, follow the returned auth link to complete setup
  6. Confirm connection status shows ACTIVE before running any workflows
  7. Always discover available tools before executing workflows
  8. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  9. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  10. Use exact field names and types from the search results
  11. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  12. Reuse session IDs within a workflow
  13. Generate new session IDs for new workflows
  14. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • include setup prerequisites
  • list known pitfalls
  • provide quick reference table

SUCCESS CRITERIA

  • RUBE_SEARCH_TOOLS responds
  • connection status shows ACTIVE
  • use schema-compliant arguments from search results

FAILURE MODES

  • Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  • Execute tools before connection is ACTIVE
  • Omit memory parameter from RUBE_MULTI_EXECUTE_TOOL
  • Fail to reuse session IDs within a workflow

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Codereadr connection via RUBE_MANAGE_CONNECTIONS with toolkit codereadr
Missing context
  • Specific Codereadr task description to insert into use_case

QUALITY

OVERALL
0.83
CLARITY
0.88
SPECIFICITY
0.90
REUSABILITY
0.78
COMPLETENESS
0.82

IMPROVEMENT SUGGESTIONS

  • Replace inline examples with explicit {{placeholders}} for task, session_id, and tool arguments to improve template reusability
  • Add a minimal success criteria section (e.g., 'Connection status = ACTIVE and tool execution returns 200')

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT