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

wakatime-automation skill

safe

/wakatime-automation

This skill automates Wakatime tasks via Composio using Rube MCP, discovering tools first to obtain current schemas.

npx playbooks add skill composiohq/awesome-claude-skills --skill wakatime-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: wakatime-automation
description: "Automate Wakatime tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Wakatime Automation via Rube MCP

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

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

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `wakatime`
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: "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](https://composio.dev)*

Overview

This skill automates Wakatime operations using Composio's Wakatime toolkit via a Rube MCP endpoint. It orchestrates tool discovery, connection checks, and multi-step executions so you can run Wakatime actions reliably from agent workflows. Always search tools first to get current schemas before executing any tool calls.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover available Wakatime tool slugs and input schemas, RUBE_MANAGE_CONNECTIONS to verify or create an active Wakatime connection, and RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk tasks) to run the operations. It enforces schema compliance, session reuse, and includes memory in execution calls. The flow handles pagination and returns recommended execution plans from the toolkit.

When to use it

Automating time-tracking queries and updates across repositories or projects.
Bulk importing or exporting Wakatime data using Composio toolchains.
Embedding Wakatime actions into larger agent-driven developer workflows.
Running scheduled audits or daily summaries that require tool schema validation.
When you need consistent, repeatable remote execution without hardcoding tool details.

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and exact input schemas.
Verify connection status with RUBE_MANAGE_CONNECTIONS and confirm ACTIVE before executions.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse a session_id for steps in the same workflow; generate new sessions for distinct workflows.
Follow pagination tokens and call additional pages until results are complete.

Example use cases

Generate a weekly Wakatime productivity report by discovering report tools and executing them via RUBE_MULTI_EXECUTE_TOOL.
Bulk update project tags or metadata across multiple Wakatime entries using RUBE_REMOTE_WORKBENCH run_composio_tool().
Onboard a new developer: verify Wakatime connection, fetch available sync tools, and run initial sync.
Automate daily time-summary notifications by scheduling tool discovery, checking connection, and executing the summary tool.

FAQ

Do I need API keys to use Rube MCP?

No API keys are required for the MCP endpoint; add https://rube.app/mcp as an MCP server in your client configuration.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS before building arguments. Use the returned schema fields and types directly; never hardcode fields.