How do I ensure I’m using current tool schemas?

Always call RUBE_SEARCH_TOOLS first; do not hardcode tool slugs or arguments.

What if the Beeminder connection isn’t ACTIVE?

Use RUBE_MANAGE_CONNECTIONS with toolkit beeminder and follow the returned auth link until the status is ACTIVE.

Is a memory object required in multi-tool execution?

Yes, include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.

Can I reuse session IDs across workflows?

Yes, reuse within a single workflow for continuity; generate new IDs for new workflows.

Where can I learn more about these toolkits?

Refer to the toolkit docs: https://composio.dev/toolkits/beeminder and Beeminder integration notes.

beeminder-automation

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

Files (1)

SKILL.md

2.9 KB

Beeminder Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/beeminder

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Beeminder operations using Composio's Beeminder toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before any workflow and requires an ACTIVE Beeminder connection. This enables repeatable, schema-compliant Beeminder automation.

How This Skill Works

You first discover available Beeminder tools with RUBE_SEARCH_TOOLS, then verify the active Beeminder connection with RUBE_MANAGE_CONNECTIONS, and finally execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id for continuity.

When to Use It

When setting up a new Beeminder automation workflow.
When tool schemas may have changed and you need current slugs and args.
Before executing any Beeminder task to ensure the connection is ACTIVE.
When reusing a session across multiple steps in a workflow.
For bulk Beeminder operations using RUBE_REMOTE_WORKBENCH.

Quick Start

Step 1: Discover tools with RUBE_SEARCH_TOOLS to fetch current Beeminder tool schemas.
Step 2: Check/add the Beeminder connection with RUBE_MANAGE_CONNECTIONS and ensure ACTIVE.
Step 3: Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the discovered tool schemas.
Include a memory object in all RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow; generate new IDs for new workflows.

Example Use Cases

Set up a weekly Beeminder goal update workflow by discovering tools, connecting, and updating the goal with new data.
React to new data by discovering Beeminder tools, ensuring an ACTIVE connection, then updating a data point via a tool.
Run multiple Beeminder operations in a single session using bulk execution (RUBE_REMOTE_WORKBENCH).
Debug a Beeminder workflow by re-discovering tool schemas to confirm current arguments before modification.
Execute a multi-step Beeminder automation that reuses a session_id for continuity across steps.

Frequently Asked Questions

Add this skill to your agents