affinda-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/affinda-automation --openclawAffinda Automation via Rube MCP
Automate Affinda operations through Composio's Affinda toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/affinda
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Affinda connection via
RUBE_MANAGE_CONNECTIONSwith toolkitaffinda - 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 toolkitaffinda - 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: "Affinda 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 Affinda task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["affinda"]
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 Affinda-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit affinda |
| 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/affinda-automation/SKILL.mdView on GitHub Overview
Automates Affinda operations through Composio’s Affinda toolkit via Rube MCP. It requires an active Rube MCP connection and an Affinda connection, and it mandates calling RUBE_SEARCH_TOOLS first to fetch current tool schemas. The pattern emphasizes discovery, connection checks, and executing tools with schema-compliant arguments.
How This Skill Works
Technically, you first discover available tools with RUBE_SEARCH_TOOLS to retrieve tool slugs and input schemas. Then you verify the Affinda connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, you execute tools using RUBE_MULTI_EXECUTE_TOOL, passing a memory object and a session_id, and you should reuse sessions across a workflow.
When to Use It
- You need to run a specific Affinda operation after fetching the latest tool schemas.
- You must verify the Affinda connection is ACTIVE before executing any workflow.
- You want to ensure arguments match exact field names and types from tool schemas.
- You are orchestrating multiple tools in a single session and must include memory and a session_id.
- You need to handle tool discovery pagination and avoid hardcoding slugs.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds for Affinda.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["affinda"] and confirm the status is ACTIVE.
- Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, providing the memory object and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current schemas.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
- Use exact field names and types from the search results.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow; avoid generating new IDs for ongoing sessions.
Example Use Cases
- Discover the 'Affinda operations' tool, connect the Affinda toolkit, then run a parsing tool with proper arguments.
- Update a batch of Affinda extractions by discovering tools, ensuring an ACTIVE connection, and issuing multiple RUBE_MULTI_EXECUTE_TOOL calls.
- Handle a schema change by re-running RUBE_SEARCH_TOOLS to fetch new slugs before execution.
- Pass a session_id from Step 1 into Step 3 to maintain context across tools.
- Fetch all tools with pagination to ensure you have the latest available slugs.
