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

agent tool_use skill risk: medium

Chaser Automation via Rube MCP

The prompt instructs the model to automate Chaser operations through Composio's Chaser toolkit via Rube MCP by first calling RUBE_SEARCH_TOOLS, verifying connections with RUBE_MANA…

  • External action: medium

SKILL 1 file

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

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

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

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Chaser connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `chaser`
- 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 `chaser`
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: "Chaser 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 Chaser task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["chaser"]
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 Chaser-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `chaser` |
| 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 Chaser connection via RUBE_MANAGE_CONNECTIONS

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 `chaser`
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Always search first
  8. Check connection
  9. Use exact field names and types from the search results
  10. Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new ones for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Prerequisites, Setup, Tool Discovery, Core Workflow Pattern, Known Pitfalls, Quick Reference
Constraints
  • always search tools first
  • verify active connection before execution
  • reuse session IDs
  • include memory parameter

SUCCESS CRITERIA

  • Always search first for current tool schemas
  • Verify ACTIVE connection status before execution
  • Use schema-compliant arguments from search results

FAILURE MODES

  • Hardcoding tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  • Executing tools without ACTIVE connection status
  • Omitting the memory parameter in RUBE_MULTI_EXECUTE_TOOL

EXAMPLES

Includes formatted example calls for RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Chaser connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target user role or experience level
  • Concrete example task walkthrough
  • Error handling or retry strategy
Ambiguities
  • Placeholder "your specific Chaser task" is not replaced with examples
  • Does not specify desired output length or format for tool responses

QUALITY

OVERALL
0.80
CLARITY
0.85
SPECIFICITY
0.78
REUSABILITY
0.82
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Replace the generic use-case placeholder with 2-3 concrete Chaser task examples
  • Add a required output format section (e.g., JSON summary of executed steps and results)

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