$ ~/registry/skill/composiohq-composio-skills-beeminder-automation

SKILL

beeminder-automation

Name: beeminder-automation
Author: Composio

Automate Beeminder tasks and goal updates through Rube MCP workflows.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is essentially an open-source prompt/workflow guide with strong community adoption, so overall risk is low. The main caution is that it relies on external Rube MCP and a Beeminder connection, which routes actions and related account data through third-party services.

CredentialsCaution

The material says 'No API keys needed,' but it requires an ACTIVE `beeminder` connection via `RUBE_MANAGE_CONNECTIONS` and a returned auth link. This implies Beeminder authorization tokens or sessions are handled by Rube/Composio; while no local plaintext secret is requested, there is still the normal need to verify third-party credential handling and granted scopes.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio's Beeminder toolkit for search, connection management, and tool execution. Task descriptions, tool arguments, session IDs, and related Beeminder operation data are therefore likely sent to Rube/Composio and then involve Beeminder. No unrelated or hidden exfiltration endpoint is stated, so this is a standard external-service caution.

Code executionLow risk

This material is classified as `prompt-only`, and it mainly provides workflow instructions. It does not claim to spawn local processes, run shell/scripts, install dependencies, or access system-level capabilities. Although it mentions `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH` for remote tool execution, there is no stated local code-execution permission.

Data accessCaution

Based on the description, its access scope is mainly the connected Beeminder account resources plus parameters, state, and possible paginated results passed through the MCP session. There is no stated access to the local filesystem, databases, or broad system resources. The caution is that a third party can process account operations and related data, but no overbroad access beyond the stated purpose is evident.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (64.7k stars), which materially lowers supply-chain risk; the material is also a skill description rather than an executable installer. Caveats are that the license is undeclared, maintenance status is unknown, and the server-side Rube/Composio implementation is not fully auditable from this material, but that alone does not justify a high-risk rating.

Recommendations

Only connect to `https://rube.app/mcp` when needed, and review Rube/Composio and Beeminder privacy, data retention, and OAuth scope details first.
Apply least privilege when authorizing Beeminder, and regularly review and revoke unused third-party connections.
Do not include sensitive information unrelated to the Beeminder task in tool queries, arguments, or sessions.
Prefer pinned, trusted repository versions and monitor ongoing maintenance and changes in both the skill repo and the Rube/Composio service.

Audited by: gpt-5.4 · 2026-06-16

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "beeminder-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/beeminder-automation/SKILL.md
2. Save it as ~/.claude/skills/beeminder-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Habitica task creation, updates, and lookups through Rube MCP.

ComposioGet→

$ loading_