$ ~/registry/skill/composiohq-composio-skills-dailybot-automation

SKILL

dailybot-automation

Name: dailybot-automation
Author: Composio

Automate Dailybot check-ins, reminders, and team coordination via Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill appears to be an open-source prompt wrapper, but it is explicitly designed to route user actions through Rube MCP to a remote service for Dailybot operations, so the overall posture is caution rather than high risk. The materials do not show local high-privilege execution or direct code execution by the skill itself, but task handling and connection flows are delegated to external MCP/third-party services.

CredentialsCaution

The material says there are 'no API keys,' but it also requires an active Dailybot connection via `RUBE_MANAGE_CONNECTIONS` and an auth link flow; in practice this implies third-party account authorization/tokens, likely brokered by Rube/Composio. There is no explicit evidence of plaintext credential harvesting or abuse, but the credential-handling boundary is not fully transparent.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and relies on Composio/Dailybot-related services for tool discovery, connection management, and execution; user task content, session IDs, and tool arguments are therefore likely sent to those declared external endpoints. The egress targets appear aligned with the stated purpose, with no unrelated or suspicious destinations shown.

Code executionLow risk

The system flags this as `prompt-only`; the material does not describe the skill spawning local processes, running scripts, or invoking system commands. Its role is mainly to instruct use of external MCP tools rather than directly obtaining local code-execution privileges.

Data accessCaution

The skill itself does not claim direct local file read/write access, but when using Rube MCP to execute Dailybot tools it may access or modify the user's Dailybot workspace data, connection state, and related operation outputs. The apparent data scope matches the stated Dailybot automation purpose, with no sign of excessive local file or system permissions.

Supply chainLow risk

The source is an open GitHub repository with very high community adoption (about 64.9k stars), which is a strong risk-reducing signal. Although the license is unspecified and maintenance status is unknown, and the skill depends on the external Rube/Composio service chain, the provided materials show no clear supply-chain red flags such as closed-source delivery, opaque installers, or suspicious dependency fetching.

Recommendations

Before connecting to `https://rube.app/mcp`, verify what session content, tool arguments, and user data your client will send to that endpoint.
When authorizing Dailybot, prefer a least-privilege account and periodically review/revoke any Rube or Composio connection tokens.
Before production use, review Rube/Composio privacy, data retention, and audit logging practices.
Limit this skill to necessary Dailybot-related content and avoid including unrelated sensitive information in prompts or tool arguments.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "dailybot-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/dailybot-automation/SKILL.md
2. Save it as ~/.claude/skills/dailybot-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Botbaba tasks and connect them into multi-step workflows via Rube MCP.

ComposioGet→

$ loading_