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

SKILL

wakatime-automation

Name: wakatime-automation
Author: Composio

Automate WakaTime data queries, reporting, and workflow tasks via Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is essentially a prompt-style wrapper with a public source and strong community adoption. However, it relies on external Rube MCP and a Wakatime connection, so real usage routes operations and related data through third-party services, making it overall low-to-moderate risk with caution warranted.

CredentialsCaution

The material states the skill itself needs no API keys, but it requires activating a `wakatime` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth-link flow. This implies reliance on third-party managed credentials/tokens, with no clear details on storage, scopes, or revocation.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and performing Wakatime operations through Composio/Rube. This means task content, arguments, and results are likely sent to that third-party service before interacting with Wakatime. The endpoint is declared and relevant to the functionality, but data does leave to a third party.

Code executionLow risk

The system flags this as `prompt-only`, and the material does not describe local installers, shell execution, or host process control. It appears to be documentation/instructions for MCP tool usage rather than something with direct code-execution capability.

Data accessCaution

The skill itself does not declare direct local file access, but it accesses Wakatime account data through Rube MCP and supports bulk operations and paginated retrieval. The actual data scope depends on the authorized Wakatime connection, and the material does not specify least-privilege scopes or field boundaries.

Supply chainLow risk

The source is a GitHub open-source repository, the system marks it as `open-source`, and community adoption is high (~64.9k stars), all of which materially reduce risk. Although the license is unspecified, maintenance status is unknown, and the external Composio/Rube service cannot be fully audited from this material, there are no clear supply-chain red flags in the provided facts.

Recommendations

Enable it only if you trust `rube.app`/Composio, and review its privacy policy, log retention, and credential-handling model.
Use the least-privileged Wakatime account/authorization possible, and regularly review or revoke unused connections.
Do not submit unrelated sensitive content in tool arguments; assume inputs may be processed by a third-party service.
Validate accessible data scope and execution behavior with a non-production/test account before broader use.

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

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Wit AI workflows via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_