Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Beeminder Automation via Rube MCP

agent tool_use skill risk: medium

Beeminder Automation via Rube MCP

Instructs on automating Beeminder operations through Composio's Beeminder toolkit via Rube MCP, including prerequisites, setup steps, tool discovery with RUBE_SEARCH_TOOLS, connect…

  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: beeminder-automation
description: "Automate Beeminder tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# 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)*

REQUIRED CONTEXT

  • Rube MCP connection
  • Beeminder toolkit connection status

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Always discover available tools before executing workflows
  4. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  5. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  6. Use exact field names and types from the search results
  7. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls even if empty
  8. Reuse session IDs within a workflow
  9. Generate new session IDs for new workflows
  10. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
unknown

EXAMPLES

Includes multiple example calls to RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL with sample arguments and session handling.

CAVEATS

Dependencies
  • Rube MCP connection
  • Active Beeminder connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Concrete example of a full end-to-end workflow with sample tool slugs and arguments
  • Definition or link for RUBE_REMOTE_WORKBENCH and RUBE_GET_TOOL_SCHEMAS
Ambiguities
  • Unclear what 'generate_id: true' produces or how session IDs are created/managed in practice.

QUALITY

OVERALL
0.80
CLARITY
0.85
SPECIFICITY
0.82
REUSABILITY
0.75
COMPLETENESS
0.78

IMPROVEMENT SUGGESTIONS

  • Add one worked example under Core Workflow Pattern showing actual tool slugs and argument values returned from search.
  • Replace generic placeholders like 'your specific Beeminder task' with 2-3 realistic use-case examples.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT