timekit-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/timekit-automation --openclawTimekit Automation via Rube MCP
Automate Timekit operations through Composio's Timekit toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/timekit
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Timekit connection via
RUBE_MANAGE_CONNECTIONSwith toolkittimekit - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkittimekit - 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: "Timekit 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 Timekit task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["timekit"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Timekit-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit timekit |
| 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/timekit-automation/SKILL.mdView on GitHub Overview
Timekit Automation via Rube MCP enables automated Timekit operations through Composio's Timekit toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing an ACTIVE connection, and executing tools using RUBE_MULTI_EXECUTE_TOOL within a structured workflow.
How This Skill Works
First, discover available tools with RUBE_SEARCH_TOOLS to get current tool schemas. Then verify the Timekit connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, execute the discovered tool using RUBE_MULTI_EXECUTE_TOOL with the required memory and the ongoing session_id.
When to Use It
- Automate recurring Timekit tasks within a Composio workflow
- Ensure youβre always using the latest tool schemas before execution
- Integrate Timekit actions into larger automation pipelines
- Validate and reuse an ACTIVE Timekit connection for reliability
- Perform bulk or chained Timekit operations via multi-execute
Quick Start
- Step 1: Add the Timekit Rube MCP server (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds
- Step 2: Manage the Timekit connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE
- Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using a session
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
- Use exact field names and types from the search results
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
- Reuse session IDs within a workflow and handle pagination tokens
Example Use Cases
- Automate event creation by discovering a Timekit tool slug and executing it with discovered arguments
- Connect to Timekit, verify ACTIVE status, then run an update event tool as part of a nightly run
- Bulk-create multiple Timekit events in a single workflow using RUBE_MULTI_EXECUTE_TOOL
- Navigate tool schema changes by re-fetching with RUBE_SEARCH_TOOLS before each run
- Chain Timekit operations (create, update, and close) within one session to maintain context