What is required to start automating Happy Scribe tasks?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must be available, and an ACTIVE Happy Scribe connection must be established via RUBE_MANAGE_CONNECTIONS.

Do I need API keys or credentials?

No API keys are needed; you only need to add the MCP server endpoint in your client configuration.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS before executing tools to get current slugs and field names; avoid hardcoding and update workflows as schemas evolve.

happy-scribe-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Happy Scribe Automation via Rube MCP

Automate Happy Scribe operations through Composio's Happy Scribe toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/happy_scribe

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["happy_scribe"]
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 Happy Scribe-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `happy_scribe`
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/happy-scribe-automation/SKILL.md

View on GitHub

Overview

This skill automates Happy Scribe operations through Composio's Happy Scribe toolkit via Rube MCP. It emphasizes discovering tool schemas first and ensuring an active connection before executing workflows.

How This Skill Works

You start by verifying RUBE_SEARCH_TOOLS to obtain current tool schemas. Then establish and confirm an ACTIVE connection to the Happy Scribe toolkit with RUBE_MANAGE_CONNECTIONS, and finally execute discovered tools using RUBE_MULTI_EXECUTE_TOOL with the correct tool slug and arguments derived from the schema.

When to Use It

Transcribing a new audio file using a tool slug discovered with RUBE_SEARCH_TOOLS.
Batch-processing multiple recordings in a single workflow after confirming schemas.
Integrating Happy Scribe tasks into an automated pipeline with real-time schema updates.
Verifying and reusing an existing session for a multi-step transcription workflow.
Exploring tool capabilities and handling pagination to discover all available tools before automation.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm current tool schemas.
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit happiness_scribe and ensure ACTIVE before running workflows.

Best Practices

Always search tools first before executing any workflow to get current tool slugs and schemas.
Check that the Happy Scribe connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools.
Use the exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and refresh or generate new ones for new workflows; handle pagination when discovering tools.

Example Use Cases

Automate a batch transcription for a podcast series by discovering the appropriate Happy Scribe tool via RUBE_SEARCH_TOOLS and executing it with RUBE_MULTI_EXECUTE_TOOL.
Connect a new Happy Scribe account with RUBE_MANAGE_CONNECTIONS and run a single transcription once the connection status is ACTIVE.
Process several episodes in one run by reusing the same session across multiple tool executions.
Perform bulk transcription operations using RUBE_REMOTE_WORKBENCH to run multiple composio tools in parallel.
Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate fields before wiring a new automation workflow.

Frequently Asked Questions

Add this skill to your agents