WO

worksnaps-automation

Automates Worksnaps workflows using Rube MCP to manage project time and tasks.

Install

mkdir -p .claude/skills/worksnaps-automation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16227" && unzip -o skill.zip -d .claude/skills/worksnaps-automation && rm skill.zip

Installs to .claude/skills/worksnaps-automation

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Automate Worksnaps tasks via Rube MCP (Composio). Always search tools first for current schemas.
96 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Discover available Worksnaps tools
  • Manage Worksnaps connections
  • Execute Worksnaps operations
  • Perform bulk operations via remote workbench
  • Retrieve full tool schemas

How it works

The skill uses Rube MCP to interact with Composio's Worksnaps toolkit. It first discovers available tools and then executes them after verifying an active connection.

Inputs & outputs

You give it
Worksnaps task use case
You get back
Execution of Worksnaps operations

When to use worksnaps-automation

  • Automating time logs
  • Managing project time tracking
  • Retrieving Worksnaps report data

About this skill

Worksnaps Automation via Rube MCP

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

Toolkit docs: 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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Worksnaps-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit worksnaps
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

When not to use it

  • When the Worksnaps connection is not active
  • When exact field names and types from search results are not used

Prerequisites

Rube MCP must be connectedActive Worksnaps connection via RUBE_MANAGE_CONNECTIONSAlways call RUBE_SEARCH_TOOLS first

Limitations

  • Tool schemas can change, requiring `RUBE_SEARCH_TOOLS` before execution.
  • Connection status must be ACTIVE before executing tools.
  • The `memory` parameter must always be included in `RUBE_MULTI_EXECUTE_TOOL` calls.

How it compares

This skill automates the discovery and execution of Worksnaps tools, ensuring schema compliance and active connections, which differs from manually configuring API calls.

Compared to similar skills

worksnaps-automation side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
worksnaps-automation (this skill)05moNo flagsIntermediate
zapier-workflows118moReviewBeginner
connect-apps67moNo flagsBeginner
connect27moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry