What is dailybot-automation?

A method to automate Dailybot tasks through the Rube MCP toolkit in Composio, using live tool schemas.

Do I need to search tools first every time?

Yes. The skill requires querying RUBE_SEARCH_TOOLS to obtain current tool slugs and arguments before any execution.

What if the connection isn’t ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to activate the Dailybot toolkit and follow the provided auth flow until status is ACTIVE.

dailybot-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/dailybot-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Dailybot Automation via Rube MCP

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

Toolkit docs: 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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit dailybot
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: "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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/dailybot-automation/SKILL.mdView on GitHub

Overview

Automate Dailybot operations through Composio's Dailybot toolkit via Rube MCP. It emphasizes discovering current tool schemas before execution and validating an ACTIVE Dailybot connection. This keeps workflows aligned with evolving tool slugs and arguments.

How This Skill Works

Connect to Rube MCP by adding its endpoint, then run RUBE_SEARCH_TOOLS to fetch available Dailybot tools and their schemas. Validate the Dailybot connection with RUBE_MANAGE_CONNECTIONS, then execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id.

When to Use It

Starting a new Dailybot workflow when tool schemas may have changed and you need current slugs and arguments
Setting up or renewing the Dailybot connection to ensure ACTIVE status before automation
Coordinating multiple Dailybot tools in a single workflow with proper session continuity
Handling large or paginated tool listings to discover all available Dailybot capabilities
Reusing a session across related Dailybot workflows to maintain context

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Run RUBE_SEARCH_TOOLS with use_case: 'Dailybot operations' to fetch current tool slugs and schemas
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkits: ['dailybot'], then RUBE_MULTI_EXECUTE_TOOL using a discovered slug and memory

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to obtain current tool slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running any tool
Use exact field names and types from the search results for arguments
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs within a workflow; generate new ones only when starting a fresh process

Example Use Cases

Discover the Dailybot ‘standup’ tool slug and schedule a standup update via RUBE_MULTI_EXECUTE_TOOL
Fetch daily task list from Dailybot and mark completed items using discovered tool arguments
Run a sequence of Dailybot tools (reminder, status update) in one session with shared session_id
Paginate through tool results to assemble a full Dailybot automation plan before execution
Handle a failed execution by re-discovering tools and retrying with a new session_id

Frequently Asked Questions

Add this skill to your agents