Do I need API keys to use this skill?

No. Connect to the Rube MCP endpoint (https://rube.app/mcp); authentication is handled there, and you must call RUBE_SEARCH_TOOLS to obtain current schemas.

Can I reuse a session across multiple Missive tasks?

Yes. Reuse the session_id within a workflow to maintain context, and generate a new session_id for new workflows.

What if tool schemas change?

Always search for current schemas first with RUBE_SEARCH_TOOLS; do not hardcode slugs or field names, and adjust inputs to match the latest schema.

missive-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Missive Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/missive

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["missive"]
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 Missive-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `missive`
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/missive-automation/SKILL.mdView on GitHub

Overview

This skill automates Missive operations using Composio's Missive toolkit through Rube MCP. It emphasizes fetching current tool schemas with RUBE_SEARCH_TOOLS and managing connections via RUBE_MANAGE_CONNECTIONS before executing tools.

How This Skill Works

It begins by querying RUBE_SEARCH_TOOLS to retrieve available Missive tool slugs and input schemas. Next, it ensures the toolkit connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Finally, it executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL, supplying the required memory object and session_id per the discovered schema.

When to Use It

When starting a Missive automation, first discover available tools to understand supported actions.
When configuring a new Missive workflow, verify an ACTIVE connection before running any tool.
When you need to run a discovered tool with correct arguments, referencing the current input schema.
When reusing workflow context, maintain same session_id across related tasks.
When tool schemas may have changed, re-fetch schemas instead of hardcoding slugs or fields.

Quick Start

Step 1: Add the MCP server by configuring https://rube.app/mcp in your client.
Step 2: Verify RUBE_SEARCH_TOOLS responds and then call RUBE_MANAGE_CONNECTIONS with toolkit 'missive' to ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then execute with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and proper arguments (memory and session_id).

Best Practices

Always call RUBE_SEARCH_TOOLS before selecting a tool to ensure up-to-date schemas.
Check RUBE_MANAGE_CONNECTIONS reports ACTIVE status prior to execution.
Use exact field names and types from the discovered schema; avoid guessing.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and create new ones only for new workflows; monitor pagination in responses.

Example Use Cases

Discover Missive tools, connect with RUBE_MANAGE_CONNECTIONS, and execute a discovered send_message tool with recipient, subject, and body aligned to the latest schema.
Update a Missive's status by selecting the appropriate tool from RUBE_SEARCH_TOOLS results and supplying the status field per the schema.
Create a new Missive template by using the template tool discovered via RUBE_SEARCH_TOOLS and passing name, content, and metadata as defined.
Bulk update multiple Missives by invoking a bulk tool discovered from the search results and batching arguments per the schema.
Fetch current tool schemas with RUBE_GET_TOOL_SCHEMAS to validate fields before designing a workflow.

Frequently Asked Questions

Add this skill to your agents