home / skills / composiohq / awesome-claude-skills / beeminder-automation

beeminder-automation skill

safe

/beeminder-automation

This skill automates Beeminder tasks via Composio using Rube MCP, ensuring up-to-date tool schemas and active connections.

npx playbooks add skill composiohq/awesome-claude-skills --skill beeminder-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: beeminder-automation
description: "Automate Beeminder tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Beeminder Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/beeminder](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `beeminder`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Beeminder tasks by orchestrating Composio’s Beeminder toolkit through a Rube MCP connection. It guides tool discovery, connection checks, and schema-compliant execution to run safe, repeatable Beeminder workflows. Designed for programmatic automation of datapoints, goals, and bulk operations.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to discover available tool slugs and exact input schemas for the requested Beeminder use case. It then verifies an active Beeminder connection via RUBE_MANAGE_CONNECTIONS and executes actions with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH, always passing schema-compliant arguments and a memory object. It enforces session reuse, pagination handling, and connection validation before performing operations.

When to use it

Automate adding or updating Beeminder datapoints from external sources
Create or modify Beeminder goals programmatically
Run bulk Beeminder operations or scheduled workflows
Integrate Beeminder actions into broader Claude/Composio automation
When you need reliable schema-aware execution to avoid malformed calls

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the beeminder toolkit before executing tools
Pass an explicit memory object (even empty) with RUBE_MULTI_EXECUTE_TOOL
Reuse a session_id for related workflow steps; generate a new session_id for separate workflows
Respect exact field names and types from the returned schemas and handle pagination tokens

Example use cases

Add daily step counts to a Beeminder goal from a fitness tracker using the discovered datapoint tool
Bulk-update deadlines or targets across multiple Beeminder goals via RUBE_REMOTE_WORKBENCH
Create an automated workflow that checks connection, queries tool schema, and submits formatted datapoints
Integrate a habit-tracking agent that writes validated datapoints to Beeminder on schedule

FAQ

Do I need API keys to use Rube MCP?

No API keys are required if you add https://rube.app/mcp as an MCP server; the client configuration endpoint is sufficient.

What if a tool schema changes mid-workflow?

Always call RUBE_SEARCH_TOOLS before each run or before critical steps; check returned schemas and adjust arguments to match exact field names and types.