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

agent tool_use skill risk: medium

Daffy Task Automation via Rube MCP

Instructs the model to automate Daffy operations through Composio's Daffy toolkit via Rube MCP by first searching tools, managing connections, and executing discovered tools follow…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["daffy"]
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 Daffy-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `daffy` |
| 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_SEARCH_TOOLS availability
  • active Daffy connection via RUBE_MANAGE_CONNECTIONS

OPTIONAL CONTEXT

  • existing session_id
  • specific Daffy use_case

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 daffy
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  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 session IDs for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • include workflow steps
  • always start with RUBE_SEARCH_TOOLS
  • list known pitfalls

SUCCESS CRITERIA

  • Always discover tools before executing
  • Verify connection is ACTIVE
  • Use schema-compliant arguments from search results

FAILURE MODES

  • Hardcoding tool slugs without searching first
  • Executing before confirming ACTIVE connection
  • Omitting the memory parameter in execute calls

EXAMPLES

Includes three example RUBE tool call blocks (SEARCH_TOOLS, MANAGE_CONNECTIONS, MULTI_EXECUTE_TOOL) plus a quick-reference table.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Daffy connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Example concrete Daffy tasks or workflows
  • Error handling procedures beyond listed pitfalls
Ambiguities
  • 'your specific Daffy task' placeholder is vague
  • No explicit success criteria or output format defined

QUALITY

OVERALL
0.55
CLARITY
0.85
SPECIFICITY
0.75
REUSABILITY
0.25
COMPLETENESS
0.65

IMPROVEMENT SUGGESTIONS

  • Replace 'your specific Daffy task' with a clear input parameter placeholder
  • Add a section for sample end-to-end task executions with expected outputs

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