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

agent tool_use skill risk: medium

Dailybot Automation via Rube MCP

Instructs the model to automate Dailybot operations through Composio's Dailybot toolkit via Rube MCP by first calling RUBE_SEARCH_TOOLS, then RUBE_MANAGE_CONNECTIONS to verify an A…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

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

### Step 2: Check Connection

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

OPTIONAL CONTEXT

  • specific Dailybot task use case
  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

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 dailybot
  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. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  9. Reuse session IDs within a workflow
  10. Generate new session IDs for new workflows
  11. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • verify connection status before execution
  • reuse session IDs within workflows

SUCCESS CRITERIA

  • Always search first before executing
  • Verify ACTIVE connection status
  • Use exact field names from search results
  • Include memory parameter on every execute call
  • Reuse session IDs within a workflow

FAILURE MODES

  • Hardcoding tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  • Executing tools before connection shows ACTIVE
  • Using non-compliant field names or types
  • Omitting the memory parameter
  • Failing to handle pagination

EXAMPLES

Includes multiple example RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS and RUBE_MULTI_EXECUTE_TOOL calls with sample arguments and session handling.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Dailybot connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target client or environment (e.g., specific MCP host or IDE).
  • Error handling or fallback behavior when tools return unexpected schemas.
Ambiguities
  • Placeholder text like "your specific Dailybot task" and "TOOL_SLUG_FROM_SEARCH" left for user substitution without explicit replacement guidance.
  • Session ID handling described inconsistently between generate_id and reuse patterns.

QUALITY

OVERALL
0.79
CLARITY
0.85
SPECIFICITY
0.78
REUSABILITY
0.72
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Replace inline placeholders with explicit [BRACKETS] or {{mustache}} style and add a short "Variables" section listing them.
  • Add one concrete end-to-end example call sequence with realistic values to illustrate the full pattern.

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