home / skills / composiohq / awesome-claude-skills / anonyflow-automation

anonyflow-automation skill

safe

/anonyflow-automation

This skill automates Anonyflow tasks via Rube MCP, always discovering current tool schemas before execution to ensure accurate, up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill anonyflow-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: anonyflow-automation
description: "Automate Anonyflow tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Anonyflow Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/anonyflow](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `anonyflow`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Anonyflow tasks through Composio's Anonyflow toolkit using Rube MCP. It provides a clear pattern for discovering tools, validating connections, and executing workflows safely while adapting to changing schemas. The skill emphasizes always searching tools first and reusing session context for reliable automation.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and recommended execution plans. It then verifies an active Anonyflow connection via RUBE_MANAGE_CONNECTIONS. Finally it runs workflows with RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk runs), supplying schema-compliant arguments, a memory object, and a session_id.

When to use it

Automating Anonyflow operations programmatically from an agent or script.
Running multi-step Composio workflows that depend on dynamic tool schemas.
Orchestrating bulk or repeated tasks across Anonyflow with Rube MCP.
When you need robust session and connection handling for Claude-based agents.
Executing schema-driven tool chains where field names and types may change.

Best practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas.
Confirm toolkit connection status via RUBE_MANAGE_CONNECTIONS and follow the auth link if not ACTIVE.
Use exact field names and types returned by the search; do not hardcode arguments.
Include a memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls and reuse session_id within a workflow.
Handle pagination tokens and iterate until responses are complete for large listings.

Example use cases

Discovering and running an Anonyflow data ingestion tool with arguments returned by RUBE_SEARCH_TOOLS.
Connecting an agent to Anonyflow, completing auth, then executing a privacy-preserving export workflow.
Bulk-processing items via RUBE_REMOTE_WORKBENCH and run_composio_tool() for high-throughput jobs.
Orchestrating multi-tool flows where each step uses the previous step’s outputs stored in memory.

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; no API keys are required.

What if tool schemas change during a workflow?

Always call RUBE_SEARCH_TOOLS before executing tools and validate fields against the returned schema. Regenerate arguments if the schema differs.