What is Better Proposals Automation via Rube MCP?

It is a process to automate Better Proposals tasks using the Rube MCP toolkit from Composio, following a search-first approach to ensure current tool schemas.

Do I always need to search for tool schemas?

Yes. Tool schemas can change, so always call RUBE_SEARCH_TOOLS before executing any tool.

What if the connection isn't ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup and recheck until the status shows ACTIVE before running workflows.

better-proposals-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/better-proposals-automation --openclaw

Files (1)

SKILL.md

3.0 KB

Better Proposals Automation via Rube MCP

Automate Better Proposals operations through Composio's Better Proposals toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/better_proposals

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Better Proposals connection via RUBE_MANAGE_CONNECTIONS with toolkit better_proposals
Always call RUBE_SEARCH_TOOLS first 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_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit better_proposals
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: "Better Proposals 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 Better Proposals task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["better_proposals"]
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_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, 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 Better Proposals-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `better_proposals`
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/better-proposals-automation/SKILL.md

View on GitHub

Overview

Automates Better Proposals tasks using Composio's Rube MCP toolkit. It focuses on discovering current tool schemas, establishing an active connection, and executing discovered tools with memory and session control to keep workflows up-to-date and compliant.

How This Skill Works

The system queries RUBE_SEARCH_TOOLS to fetch current Better Proposals tool schemas, then uses RUBE_MANAGE_CONNECTIONS to verify and activate the toolkit connection. Finally, it executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the schema-compliant arguments, a memory object, and the active session.

When to Use It

When you need to automate repetitive Better Proposals tasks using up-to-date tool schemas.
Before running a workflow, to ensure tool schemas are current via RUBE_SEARCH_TOOLS.
When establishing or verifying a Better Proposals connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.
For multi-step proposal workflows requiring memory and session continuity (RUBE_MULTI_EXECUTE_TOOL).
When handling large results from tool discovery that may paginate; fetch using pagination tokens.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Better Proposals tool schemas.
Step 3: Manage the connection with RUBE_MANAGE_CONNECTIONS (toolkit: better_proposals) and execute the discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory and the current session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to pull current tool schemas.
Verify the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before execution.
Use exact field names and types from the search results; do not hardcode slugs or args.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and manage new ones for separate workflows.

Example Use Cases

Automate a proposal template update by discovering the relevant tool slug with RUBE_SEARCH_TOOLS and executing it via RUBE_MULTI_EXECUTE_TOOL.
Connect to the Better Proposals toolkit and ensure ACTIVE status before performing a bulk create/update operation.
Run a multi-step proposal approval flow that relies on memory to maintain context across steps.
Handle tool discovery pagination to list all available Better Proposals operations before choosing one.
Reuse a single session ID across consecutive proposal tasks to improve performance and consistency.

Frequently Asked Questions

Add this skill to your agents