bidsketch-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/bidsketch-automation --openclawBidsketch Automation via Rube MCP
Automate Bidsketch operations through Composio's Bidsketch toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/bidsketch
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bidsketch connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbidsketch - 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 toolkitbidsketch - 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: "Bidsketch 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 Bidsketch task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["bidsketch"]
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 Bidsketch-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit bidsketch |
| 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/bidsketch-automation/SKILL.mdView on GitHub Overview
This skill automates Bidsketch operations via Composio's toolkit using Rube MCP. It emphasizes discovering current tool schemas before running workflows, verifying an active Bidsketch connection, and executing tools with proper session and memory handling to keep automations resilient.
How This Skill Works
The automation starts by using RUBE_SEARCH_TOOLS to fetch tool slugs and input schemas, then uses RUBE_MANAGE_CONNECTIONS to ensure an ACTIVE bidsketch toolkit connection. Finally, RUBE_MULTI_EXECUTE_TOOL runs the selected tool with exact schema-compliant arguments and a memory payload, guided by the discovered execution plan and known pitfalls.
When to Use It
- Automate recurring Bidsketch tasks such as creating and sending proposals when a deal is ready.
- Always search for current tool schemas before running a workflow to adapt to changes.
- Run workflows in a single session and reuse the session ID to maintain context.
- Verify the Bidsketch connection is ACTIVE before executing any tools.
- Perform bulk or multi-tool operations using RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs.
Quick Start
- Step 1: Discover Available Tools RUBE_SEARCH_TOOLS with use_case set to your Bidsketch task.
- Step 2: Check Connection RUBE_MANAGE_CONNECTIONS for toolkit: bidsketch and confirm ACTIVE.
- Step 3: Execute Tools RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and memory: {}.
Best Practices
- Always search first with RUBE_SEARCH_TOOLS to get current tool schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the discovered tool schemas.
- 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
- Auto-create and send a Bidsketch proposal when a deal closes, using a discovered tool slug and inputs from the latest schema.
- Batch-process multiple bids from a template into individual proposals in a nightly run.
- Refresh the Bidsketch connection before starting a high-priority campaign workflow.
- Run a nightly automation to apply changes across open proposals using tools discovered at runtime.
- Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to ensure correct input mapping before modifying proposals.
