What is Anonyflow automation via Rube MCP?

A workflow pattern that automates Anonyflow tasks by discovering tools, managing the Anonyflow connection, and executing tools through Rube MCP.

Do I need to know tool slugs ahead of time?

No. Always fetch tool slugs and input schemas with RUBE_SEARCH_TOOLS before you execute any tool.

How do I keep tool schemas current?

Always call RUBE_SEARCH_TOOLS before execution to get the latest slugs and schemas; avoid hardcoding and handle pagination if present.

anonyflow-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Anonyflow Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/anonyflow

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Anonyflow operations through Composio's Anonyflow toolkit via Rube MCP. It orchestrates discovery, connection management, and execution using current tool schemas to keep workflows reliable.

How This Skill Works

The skill first fetches the latest Anonyflow tool schemas with RUBE_SEARCH_TOOLS, then verifies an ACTIVE connection via RUBE_MANAGE_CONNECTIONS for the 'anonyflow' toolkit, and finally runs selected tools through RUBE_MULTI_EXECUTE_TOOL using the discovered arguments and a memory payload in a shared session.

When to Use It

When you need to automate Anonyflow tasks and require up-to-date tool schemas from the center
When establishing a new Anonyflow integration or after tooling schemas change
When you want to discover available Anonyflow tools before running workflows
When executing one or more tools within a single session to preserve context
When handling large results and needing pagination tokens during discovery

Quick Start

Step 1: Add the MCP server url (https://rube.app/mcp) to your client config and verify connectivity with RUBE_SEARCH_TOOLS
Step 2: Run RUBE_MANAGE_CONNECTIONS for the 'anonyflow' toolkit and ensure the connection status is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using the returned memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results; avoid hardcoding
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and handle pagination tokens during discovery

Example Use Cases

Automate a provisioning task by discovering Anonyflow tools, establishing an ACTIVE connection, and executing a single sluggable tool with a prepared payload
Run a batch of Anonyflow operations in one session by discovering tools, then executing multiple tools with a shared memory object
Adapt to schema changes by re-running RUBE_SEARCH_TOOLS before updating a workflow's tool invocations
Validate a new Anonyflow workflow by fetching schemas with RUBE_GET_TOOL_SCHEMAS and executing a test tool
Bulk process multiple Anonyflow tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool() in a single batch

Frequently Asked Questions

Add this skill to your agents