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

desktime-automation skill

safe

/desktime-automation

This skill automates Desktime tasks through Rube MCP, enabling seamless tool discovery, connection checks, and automated execution using current schemas.

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

# Desktime Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/desktime](https://composio.dev/toolkits/desktime)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["desktime"]
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 Desktime-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `desktime` |
| 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 Desktime operations through Composio's Desktime toolkit using Rube MCP. It orchestrates tool discovery, connection management, and multi-step executions so workflows run reliably. The design emphasizes always searching for current tool schemas and verifying connection status before execution.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to retrieve available tool slugs, input schemas, recommended plans, and pagination tokens. It then checks or initiates the Desktime connection via RUBE_MANAGE_CONNECTIONS and confirms an ACTIVE status. Finally it runs actions using RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs), always supplying schema-compliant arguments, a memory object, and a consistent session_id.

When to use it

Automate user time tracking, project summaries, or reporting in Desktime
Perform bulk updates or batch exports from Desktime via Composio tools
Integrate Desktime operations into multi-step agent workflows that require external toolkit calls
Run scheduled or on-demand Desktime maintenance tasks with reliable connection checks

Best practices

Always call RUBE_SEARCH_TOOLS first — tool schemas and slugs can change
Verify toolkit connection with RUBE_MANAGE_CONNECTIONS and ensure status is ACTIVE before executing tools
Use exact field names and types returned by the search results to avoid schema errors
Include a memory object (even if empty) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session_id for a single workflow and generate a new session for separate workflows
Handle pagination tokens when searching tools or fetching lists to ensure full results

Example use cases

Discover Desktime endpoints and input schemas, then run a single time-entry creation via RUBE_MULTI_EXECUTE_TOOL
Check connection status and trigger a bulk export of projects or reports using RUBE_REMOTE_WORKBENCH
Automate onboarding: create user accounts in Desktime and assign projects with a multi-step session
Schedule nightly audit: search tools, confirm connection, and run schema-compliant report exports

FAQ

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration and use the Rube MCP endpoints.

What if RUBE_SEARCH_TOOLS returns different schemas later?

Always re-run RUBE_SEARCH_TOOLS before executing tools. Do not hardcode slugs or argument structures; adapt to the returned schema and recommended execution plan.