dovetail-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/dovetail-automation --openclawDovetail Automation via Rube MCP
Automate Dovetail operations through Composio's Dovetail toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/dovetail
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Dovetail connection via
RUBE_MANAGE_CONNECTIONSwith toolkitdovetail - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitdovetail - 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: "Dovetail 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 Dovetail task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["dovetail"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Dovetail-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit dovetail |
| 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/dovetail-automation/SKILL.mdView on GitHub Overview
Dovetail Automation via Rube MCP enables running Dovetail workflows through Composio’s toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution to ensure correct tool slugs and input structures. This approach keeps automation aligned with live schemas and supports reliable, repeatable Dovetail tasks.
How This Skill Works
Requires a connected Rube MCP (RUBE_SEARCH_TOOLS available) and an ACTIVE Dovetail connection (RUBE_MANAGE_CONNECTIONS with toolkit dovetail). The workflow starts by discovering tools, then checking the connection status, and finally executing a discovered tool via RUBE_MULTI_EXECUTE_TOOL with a memory payload and the session_id.
When to Use It
- Starting a new Dovetail workflow and requiring the latest tool schemas
- Ensuring a Dovetail connection is ACTIVE before running workflows
- Executing a discovered tool with the appropriate arguments
- Reusing a session across multiple Dovetail tasks
- Handling pagination by fetching all tool schemas and results
Quick Start
- Step 1: Verify Rube MCP is available by calling RUBE_SEARCH_TOOLS
- Step 2: Connect to Dovetail with RUBE_MANAGE_CONNECTIONS toolkits: ["dovetail"]
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, choose a tool_slug from the results, and execute with RUBE_MULTI_EXECUTE_TOOL using a session_id
Best Practices
- Always call RUBE_SEARCH_TOOLS before execution to fetch current tool slugs and schemas
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running workflows
- Use the exact field names and types from the search results
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs across related workflows and manage pagination
Example Use Cases
- Create a Dovetail task from a chat prompt using a discovered tool slug
- Update Dovetail records with external status updates by executing a mapped tool
- Run a batch of Dovetail analyses by sequentially calling discovered tools
- Bulk import tasks into Dovetail from an external CSV via a discovered tool
- Audit available Dovetail tools and refresh automation to schema changes