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

agent tool_use skill risk: medium

Dovetail Automation via Rube MCP

Instructs the model to automate Dovetail operations through Composio's Dovetail toolkit using Rube MCP, including mandatory tool discovery with RUBE_SEARCH_TOOLS, connection manage…

  • External action: medium

SKILL 1 file

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

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

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

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Dovetail connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dovetail`
- 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 `dovetail`
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: "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_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 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](https://composio.dev)*

REQUIRED CONTEXT

  • Rube MCP connection
  • Dovetail toolkit connection status

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

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 dovetail
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new session IDs for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

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

SUCCESS CRITERIA

  • Always search first
  • Check connection status
  • Follow schema compliance
  • Reuse sessions correctly

FAILURE MODES

  • Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  • Fail to verify ACTIVE connection status
  • Omit memory parameter in RUBE_MULTI_EXECUTE_TOOL
  • Ignore pagination tokens

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Dovetail connection via RUBE_MANAGE_CONNECTIONS with toolkit dovetail
Ambiguities
  • Tool call examples use pseudo-syntax rather than exact JSON or function-call format
  • Session ID generation vs reuse rules are stated but not fully specified for edge cases

QUALITY

OVERALL
0.79
CLARITY
0.85
SPECIFICITY
0.78
REUSABILITY
0.72
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Replace pseudo-code tool calls with exact, copy-pasteable JSON schemas or function call examples
  • Add a minimal end-to-end example workflow for a concrete Dovetail task (e.g., "list projects")

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