What do I need to use this skill?

A connected Rube MCP (RUBE_SEARCH_TOOLS available) and an ACTIVE Fireflies connection via RUBE_MANAGE_CONNECTIONS with toolkit 'fireflies'. Always run RUBE_SEARCH_TOOLS first.

Are API keys required?

No API keys are required. You only need to add the MCP endpoint (e.g., https://rube.app/mcp) in your client configuration.

How do I keep tool schemas up to date?

Always call RUBE_SEARCH_TOOLS before executing tools to fetch current schemas; do not hardcode tool slugs or arguments; handle pagination if needed.

fireflies-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Fireflies Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/fireflies

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Fireflies operations via Composio's Fireflies toolkit through Rube MCP. It always fetches current tool schemas with RUBE_SEARCH_TOOLS before running and requires an ACTIVE Fireflies connection. This makes automation reliable and up-to-date with the latest tool definitions.

How This Skill Works

It discovers available Fireflies tools via RUBE_SEARCH_TOOLS using a Fireflies use_case, then validates the connection with RUBE_MANAGE_CONNECTIONS and an active session. Finally, it executes tools with RUBE_MULTI_EXECUTE_TOOL, supplying the slug and schema-compliant arguments, memory, and session_id.

When to Use It

Discover and run a Fireflies operation after tool discovery
Ensure current tool schemas are fetched before execution
Verify an ACTIVE Fireflies connection prior to automation
Execute multiple Fireflies tools in a single workflow
Reuse session IDs within a workflow to optimize runs

Quick Start

Step 1: Run RUBE_SEARCH_TOOLS with use_case: 'Your Fireflies task' to view available tools
Step 2: Run RUBE_MANAGE_CONNECTIONS to ensure toolkit 'fireflies' is ACTIVE
Step 3: Run RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug, proper arguments, memory, and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and never hardcode tool slugs
Check connection status is ACTIVE before executing tools via RUBE_MANAGE_CONNECTIONS
Use exact field names and types from search results; follow the schema strictly
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones only for new workflows

Example Use Cases

Discover the Fireflies task slug for a meeting summary and execute it in a single workflow
Chaining Fireflies tools to generate a meeting recap and share notes automatically
Batch-run multiple Fireflies tasks for several meetings in one session
Update CRM or project docs with Fireflies notes by executing related tools in sequence
Resume an automation by reusing a session_id to continue after a pause

Frequently Asked Questions

Add this skill to your agents