What is the first action to take?

Always run RUBE_SEARCH_TOOLS to fetch current tool schemas before any execution.

How do I ensure the Dialmycalls connection is ready?

Run RUBE_MANAGE_CONNECTIONS with toolkit 'dialmycalls' and confirm the status is ACTIVE.

What should I include in memory for tool execution?

Include a memory object in RUBE_MULTI_EXECUTE_TOOL even if empty to preserve state.

dialmycalls-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Dialmycalls Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/dialmycalls

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["dialmycalls"]
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 Dialmycalls-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `dialmycalls`
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/dialmycalls-automation/SKILL.md

View on GitHub

Overview

Automate Dialmycalls operations through Composio's Dialmycalls toolkit via Rube MCP. This skill coordinates discovery of current tool schemas, verifies an ACTIVE connection, and executes tools using the RUBE_MULTI_EXECUTE_TOOL flow. It ensures you always work with up-to-date schemas to prevent breakages.

How This Skill Works

The workflow starts with RUBE_SEARCH_TOOLS to fetch available Dialmycalls tool slugs and schemas, then verifies an ACTIVE Dialmycalls connection with RUBE_MANAGE_CONNECTIONS. Finally, tools are executed with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a memory payload, ensuring schema compliance.

When to Use It

When you need to perform a Dialmycalls task but tool schemas may change, so you always fetch current schemas first.
When establishing or verifying a Dialmycalls connection via Rube MCP before workflows.
When you have a multi-step workflow: search tools, check connection, then execute.
When handling pagination or multiple results from tool discovery.
When you want to bulk-operate or run remote bench tasks using run_composio_tool.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with queries: [{use_case: "Dialmycalls operations"}] and session: {generate_id: true}.
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ["dialmycalls"] and session_id: <your_session_id>, then ensure status is ACTIVE.
Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, proper arguments, memory: {}, and session_id: <your_session_id>.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tool.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
Use exact field names and types from search results; avoid hardcoding slugs.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs for a single workflow and fetch new ones for new workflows; monitor pagination tokens.

Example Use Cases

Set up and run a Dialmycalls campaign by discovering the latest tool slugs and executing the dialout tool via RUBE_MULTI_EXECUTE_TOOL.
Perform follow-ups in bulk by confirming connection and using multiple tools discovered with RUBE_SEARCH_TOOLS.
Verify ACTIVE connection for a Dialmycalls toolkit before any workflow to avoid failures.
Handle pagination in tool discovery results and keep memory payload consistent.
Use RUBE_REMOTE_WORKBENCH to run a batch of composio tools for a Dialmycalls workflow.

Frequently Asked Questions

Add this skill to your agents