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

worksnaps-automation skill

safe

/worksnaps-automation

This skill automates Worksnaps tasks via Composio's MCP, ensuring real-time tool discovery and validated connections before execution.

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

# Worksnaps Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["worksnaps"]
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 Worksnaps-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `worksnaps` |
| 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 Worksnaps tasks through Composio's Worksnaps toolkit using the Rube MCP integration. It provides a safe, repeatable pattern for discovering current tool schemas, validating connections, and executing Worksnaps operations programmatically. Follow the search-first approach to avoid schema drift and ensure reliable automation.

How this skill works

The skill always calls RUBE_SEARCH_TOOLS first to retrieve available tool slugs, input schemas, execution plans, and pagination tokens. It then verifies the Worksnaps connection via RUBE_MANAGE_CONNECTIONS and runs one or more tools with RUBE_MULTI_EXECUTE_TOOL (including an explicit memory object and a session_id). For bulk or advanced flows, it supports RUBE_REMOTE_WORKBENCH and schema lookups via RUBE_GET_TOOL_SCHEMAS.

When to use it

Automating time-tracking, timesheet, or project updates in Worksnaps
Running repeated Worksnaps operations where tool schemas may change
Building integrations that must validate active Worksnaps connections first
Orchestrating multi-step workflows that reuse session state
Performing bulk updates or remote runs using Composio tooling

Best practices

Always call RUBE_SEARCH_TOOLS first and use the returned schema fields exactly
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the worksnaps toolkit before executing tools
Include a memory object (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session_id for related operations; generate new sessions for new workflows
Handle pagination tokens when searching or listing resources to avoid incomplete results

Example use cases

Query available Worksnaps tools, then create or update timesheets using discovered tool schema fields
Validate and reauthenticate a Worksnaps connection when connection status is not ACTIVE
Batch-run time adjustments across multiple projects via RUBE_REMOTE_WORKBENCH and run_composio_tool()
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before building dynamic UI or API payloads

FAQ

Do I need API keys to use Rube MCP?

No API keys are required—add the MCP server endpoint to your client and use the Rube MCP endpoints.

What if tool schemas change after I built a workflow?

Always call RUBE_SEARCH_TOOLS at runtime to get the current schemas and adjust your arguments accordingly; never hardcode fields or tool slugs.