What prerequisites are required to use this skill?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must be available, and there must be an active Deepgram connection with the toolkit 'deepgram'. Always call RUBE_SEARCH_TOOLS first.

Why should I search tools before executing any workflow?

Tool schemas change over time. Searching tools ensures you use current slugs and input fields rather than hardcoding values.

How do I verify readiness before running a workflow?

Confirm the Deepgram connection is ACTIVE via RUBE_MANAGE_CONNECTIONS, obtain a session_id, and ensure memory is provided for RUBE_MULTI_EXECUTE_TOOL.

deepgram-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Deepgram Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/deepgram

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Deepgram operations using Composio's Deepgram toolkit through Rube MCP. It emphasizes discovering current tool schemas before running workflows to adapt to schema changes and avoid hardcoding slugs.

How This Skill Works

The skill uses Rube MCP to (1) discover available Deepgram tools via RUBE_SEARCH_TOOLS, (2) verify the Deepgram connection with RUBE_MANAGE_CONNECTIONS, and (3) execute chosen tools with RUBE_MULTI_EXECUTE_TOOL. It relies on live input schemas from tool discovery and requires a memory payload and session_id for each workflow.

When to Use It

When starting a new Deepgram automation and you need the latest available tools.
When verifying that the Deepgram connection is ACTIVE before running workflows.
When orchestrating a multi-step Deepgram task by chaining discovered tools in a session.
When performing bulk/deepgram operations using RUBE_REMOTE_WORKBENCH.
When tool schemas change and you must refresh slugs and inputs from current schemas.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and ensure RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["deepgram"] and confirm the session shows ACTIVE.
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug and memory + session_id payload.

Best Practices

Always search tools first to get current schemas.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from search results; avoid guessing.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new IDs for new workflows.

Example Use Cases

Create a new transcription batch by discovering tools, verifying the Deepgram connection, and executing the chosen tool with a session_id.
Choreograph a multi-step Deepgram task by chaining discovered tool slugs in a single session.
Update an ongoing pipeline by reusing the current session_id and executing subsequent tools.
Run a bulk Deepgram operation via RUBE_REMOTE_WORKBENCH using run_composio_tool.
When tool schemas change, refresh via RUBE_SEARCH_TOOLS and re-run with the latest input schemas.

Frequently Asked Questions

Add this skill to your agents