rocketlane-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/rocketlane-automation --openclawFiles (1)
SKILL.md
2.9 KB
Rocketlane Automation via Rube MCP
Automate Rocketlane operations through Composio's Rocketlane toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/rocketlane
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Rocketlane connection via
RUBE_MANAGE_CONNECTIONSwith toolkitrocketlane - 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 toolkitrocketlane - 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: "Rocketlane 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 Rocketlane task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["rocketlane"]
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 Rocketlane-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit rocketlane |
| 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/rocketlane-automation/SKILL.mdView on GitHub Overview
Automate Rocketlane operations through Composio's Rocketlane toolkit using Rube MCP. The workflow emphasizes discovering current tool schemas first, establishing a Rocketlane connection, and safely executing tools with proper session and memory handling.
How This Skill Works
First verify MCP connectivity with RUBE_SEARCH_TOOLS to pull current tool schemas. Then establish or validate a Rocketlane connection via RUBE_MANAGE_CONNECTIONS. Finally, select a discovered tool slug and run it with RUBE_MULTI_EXECUTE_TOOL, providing exact arguments from the schema, a memory payload, and a session_id for continuity.
When to Use It
- Automate creating or updating Rocketlane records (e.g., projects or tasks) using the tool slugs returned by RUBE_SEARCH_TOOLS.
- Set up a new Rocketlane automation workflow and verify the connection is ACTIVE before execution.
- Perform bulk operations or batch updates by executing multiple tools in a single flow with memory tracking.
- React to schema changes by re-discovering tools with RUBE_SEARCH_TOOLS instead of hardcoding slugs.
- Reuse session IDs across steps in a multi-step Rocketlane workflow to maintain context.
Quick Start
- Step 1: Add the RUBE MCP endpoint (https://rube.app/mcp) as an MCP server in your client configuration and verify connectivity with RUBE_SEARCH_TOOLS.
- Step 2: Use RUBE_MANAGE_CONNECTIONS with toolkits: ["rocketlane"] to connect and confirm the status is ACTIVE.
- Step 3: From the discovered tools, choose a slug and execute it with RUBE_MULTI_EXECUTE_TOOL, passing the required arguments and memory ({}), along with a session_id.
Best Practices
- Always run RUBE_SEARCH_TOOLS before executing to get current tool schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE Rocketlane connection before any execution.
- Use exact field names and types from the search results; avoid hardcoding slugs or arguments.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and generate new ones only for new workflows.
Example Use Cases
- Discover the Rocketlane task to create a project, then run the tool slug with arguments sourced from an external template to auto-create a new Rocketlane project.
- Automatically set a task status to 'In Progress' when a milestone starts by executing the corresponding Rocketlane tool with the latest session data.
- Bulk import tasks from an external backlog by discovering a bulk-create tool and supplying a memory payload that tracks progress across batches.
- Fetch a project's current status via a search-discovered tool and post the result to a Slack channel or dashboard.
- Chain multiple Rocketlane tools in a single flow (e.g., create project, add tasks, assign owners) while reusing session IDs for continuity.
Frequently Asked Questions
Add this skill to your agents
