What prerequisites are required?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must respond, and there must be an ACTIVE Wakatime connection.

Should I always call RUBE_SEARCH_TOOLS first?

Yes. Tool schemas can change and you should not hardcode slugs or arguments.

How do I handle schema changes between runs?

Fetch updated schemas with RUBE_SEARCH_TOOLS before executing and use the provided slugs and field names exactly.

wakatime-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Wakatime Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/wakatime

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Wakatime operations through Composio's Wakatime toolkit via Rube MCP. It enforces discovering current tool schemas with RUBE_SEARCH_TOOLS first and requires an ACTIVE Wakatime connection via RUBE_MANAGE_CONNECTIONS.

How This Skill Works

You discover tool slugs and input schemas with RUBE_SEARCH_TOOLS, verify the Wakatime connection using RUBE_MANAGE_CONNECTIONS, then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id. Memory must be included even if empty.

When to Use It

Setting up a new Wakatime workflow by discovering tools and their schemas
Verifying and establishing an ACTIVE Wakatime connection before any run
Executing a Wakatime tool in a multi tool workflow with session management
Updating tool usage after Wakatime schema changes
Running bulk Wakatime operations via remote bench or batch tools

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config.
Step 2: Verify RUBE_SEARCH_TOOLS responds and establish a Wakatime connection with RUBE_MANAGE_CONNECTIONS (ensure ACTIVE).
Step 3: Discover tools with RUBE_SEARCH_TOOLS and run a tool via RUBE_MULTI_EXECUTE_TOOL using a session_id and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS before selecting tool slugs
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from the discovered schemas
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and handle pagination tokens in responses

Example Use Cases

Schedule daily Wakatime report: discover tools, connect, run a reporting tool, and store results
Project onboarding: initialize Wakatime tracking by discovering tools, connecting, then executing a setup tool
Bulk export: run multiple Wakatime tools in a batch using RUBE_MULTI_EXECUTE_TOOL and RUBE_REMOTE_WORKBENCH
Schema change adaptation: fetch updated tool schemas with RUBE_SEARCH_TOOLS and adjust tool slugs
Recovery workflow: check connection status, re-auth if needed, and re-run a failed tool with a new session

Frequently Asked Questions

Add this skill to your agents