detrack-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/detrack-automation --openclawDetrack Automation via Rube MCP
Automate Detrack operations through Composio's Detrack toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/detrack
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Detrack connection via
RUBE_MANAGE_CONNECTIONSwith toolkitdetrack - 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 toolkitdetrack - 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: "Detrack 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 Detrack task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["detrack"]
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 Detrack-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit detrack |
| 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/detrack-automation/SKILL.mdView on GitHub Overview
Automate Detrack operations through Composio's Detrack toolkit via Rube MCP. This approach keeps workflows up to date by fetching current tool schemas instead of hardcoding slugs or arguments. It requires a connected Rube MCP, an active Detrack link, and pre-checks using RUBE_SEARCH_TOOLS.
How This Skill Works
First, discover available Detrack tools with RUBE_SEARCH_TOOLS to get current slugs and schemas. Then verify the Detrack connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, schema-compliant arguments, memory, and a session_id from the discovery step.
When to Use It
- When you need to run a Detrack task using the latest tool schemas from RUBE_SEARCH_TOOLS.
- When you must confirm the Detrack connection is ACTIVE before workflows.
- When you want to reuse a session_id across a multi-step Detrack workflow to maintain context.
- When you want to perform a sequence or bulk Detrack operations with RUBE_MULTI_EXECUTE_TOOL and tools discovered via RUBE_SEARCH_TOOLS.
- When tool discovery returns multiple pages, use pagination flow to fetch all available tools.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client and verify connectivity with RUBE_SEARCH_TOOLS.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["detrack"] and confirm ACTIVE.
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then run RUBE_MULTI_EXECUTE_TOOL using the returned tool_slug, required arguments, memory, and the session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool slugs.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even when empty.
- Reuse session IDs within a workflow and generate new ones for new workflows.
Example Use Cases
- Auto-create a Detrack job from a form submission by discovering the tool and executing with correct schema.
- Update task statuses in Detrack based on external system events.
- Run bulk updates of multiple Detrack tasks via RUBE_REMOTE_WORKBENCH with run_composio_tool.
- Always fetch the latest tool schemas before integrating with Detrack in a live environment.
- Maintain context across steps by reusing a session_id when chaining Detrack tools.
