brex-staging-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/brex-staging-automation --openclawBrex Staging Automation via Rube MCP
Automate Brex Staging operations through Composio's Brex Staging toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/brex_staging
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Brex Staging connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbrex_staging - 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 toolkitbrex_staging - 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: "Brex Staging 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 Brex Staging task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["brex_staging"]
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 Brex Staging-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit brex_staging |
| 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/brex-staging-automation/SKILL.mdView on GitHub Overview
Automates Brex Staging tasks by using Composio's Brex Staging toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before every run and managing connections with RUBE_MANAGE_CONNECTIONS to ensure safe, up-to-date automation.
How This Skill Works
The workflow starts by discovering available Brex Staging tools with RUBE_SEARCH_TOOLS, then confirms an ACTIVE Brex Staging connection using RUBE_MANAGE_CONNECTIONS. Finally, it executes the selected tool(s) with RUBE_MULTI_EXECUTE_TOOL, passing in the exact arguments from the discovered schema and including a memory payload.
When to Use It
- When you need to automate a Brex Staging task with up-to-date tool schemas
- When setting up a new Brex Staging workflow or adding a task to an existing pipeline
- When debugging a failing Brex Staging task and validating tool inputs
- When performing batch or bulk Brex Staging operations in a single run
- When verifying connections and tool availability before execution
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
- Step 2: Run RUBE_SEARCH_TOOLS to load current Brex Staging tool schemas
- Step 3: Run your workflow: RUBE_MANAGE_CONNECTIONS (brex_staging) -> RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and memory
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
- Use exact field names and types from the discovered schemas
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow and avoid creating new ones for the same run
Example Use Cases
- Automate a weekly Brex Staging data refresh by discovering the latest tool and running it with a single session
- Orchestrate a release-ready Brex Staging checklist by chaining multiple discovered tools in one workflow
- Debug a failing task by re-searching tool schemas and correcting arguments to match the latest schema
- Perform bulk Brex Staging operations in one workflow using multiple tools discovered from RUBE_SEARCH_TOOLS
- Reestablish a Brex Staging connection when the status shows INACTIVE and retry execution
