Do I need API keys to use proofly-automation?

No keys are required. Add the MCP server at https://rube.app/mcp and use RUBE_SEARCH_TOOLS to fetch current tool schemas.

How do I handle changes in tool schemas?

Always run RUBE_SEARCH_TOOLS before executing and base your arguments on the returned schemas; avoid hardcoding tool slugs or fields.

What should I include in memory and why?

Include the memory object in RUBE_MULTI_EXECUTE_TOOL to preserve state across steps; even if empty, it must be provided.

proofly-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Proofly Automation via Rube MCP

Automate Proofly operations through Composio's Proofly toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/proofly

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Proofly connection via RUBE_MANAGE_CONNECTIONS with toolkit proofly
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 proofly
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: "Proofly 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 Proofly task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["proofly"]
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 Proofly-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `proofly`
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/proofly-automation/SKILL.mdView on GitHub

Overview

Automate Proofly operations through Composio's Proofly toolkit via Rube MCP. Always search tools first for current schemas to stay in sync with updates and ensure reliable execution.

How This Skill Works

Discover available Proofly tools and input schemas with RUBE_SEARCH_TOOLS. Verify and establish an ACTIVE Proofly connection using RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including the memory parameter and a session_id, reusing sessions when appropriate.

When to Use It

You need to automate a recurring Proofly operation and want end-to-end orchestration from discovery to execution.
Tool schemas frequently update, requiring dynamic discovery rather than hardcoded slugs.
You manage multiple Proofly workflows across sessions and want consistent session handling.
You must verify an ACTIVE Proofly connection before running critical workflows.
You want to perform bulk or chained Proofly operations with memory persistence across steps.

Quick Start

Step 1: Verify Rube MCP is available by calling RUBE_SEARCH_TOOLS.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["proofly"] and check for ACTIVE.
Step 3: Execute the discovered tool with RUBE_MULTI_EXECUTE_TOOL, include memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get up-to-date tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid guessing.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens when fetching results.

Example Use Cases

Automate a weekly Proofly report by discovering the needed tool, executing the slug, and collecting results in a single session.
Adapt an automation when Proofly tool schemas change by re-running RUBE_SEARCH_TOOLS and updating only the required inputs.
Run a multi-step Proofly workflow for an quarterly audit: discovery, connect, then sequential tool executions with memory.
Before a critical task, verify ACTIVE connection to Proofly to prevent failures during automation.
Bulk multiple Proofly tasks using a batch approach and consolidate outputs via a shared session.

Frequently Asked Questions

Add this skill to your agents