fraudlabs-pro-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/fraudlabs-pro-automation --openclawFraudlabs Pro Automation via Rube MCP
Automate Fraudlabs Pro operations through Composio's Fraudlabs Pro toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/fraudlabs_pro
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Fraudlabs Pro connection via
RUBE_MANAGE_CONNECTIONSwith toolkitfraudlabs_pro - 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 toolkitfraudlabs_pro - 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: "Fraudlabs Pro 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 Fraudlabs Pro task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["fraudlabs_pro"]
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 Fraudlabs Pro-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit fraudlabs_pro |
| 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/fraudlabs-pro-automation/SKILL.mdView on GitHub Overview
Automate Fraudlabs Pro operations through Composio's Fraudlabs Pro toolkit via Rube MCP. This skill emphasizes discovering current tool schemas first and establishing a solid connection before running workflows. It helps maintain up-to-date integrations and reliable automation.
How This Skill Works
The workflow starts by calling RUBE_SEARCH_TOOLS to fetch current Fraudlabs Pro tool schemas. Next, RUBE_MANAGE_CONNECTIONS verifies or activates the fraudlabs_pro toolkit, and finally RUBE_MULTI_EXECUTE_TOOL runs the chosen tool with schema-compliant arguments, always including memory. Refer to the toolkit docs at composio.dev/toolkits/fraudlabs_pro for specifics.
When to Use It
- You need to automate Fraudlabs Pro checks for new orders or customer validations within a workflow.
- You are wiring up a new Fraudlabs Pro integration and must discover current tool schemas before automation.
- You want to run Fraudlabs Pro tasks in bulk or batch operations while reusing a session.
- You must verify the Fraudlabs Pro connection is ACTIVE before executing any tools.
- You want to handle tool schema changes without hardcoding slugs or arguments.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: "Fraudlabs Pro operations", known_fields: ""}] session: {generate_id: true}
- Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["fraudlabs_pro"] session_id: "your_session_id"
- Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results and memory: {} session_id: "your_session_id"
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas and avoid hardcoding slugs.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before running tools.
- Use exact field names and types from the discovered schemas in tool arguments.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and generate new ones for new workflows to ensure stability.
Example Use Cases
- Automate a sequence that screens a new order through Fraudlabs Pro by first fetching the latest tool schemas, then validating the connection, and finally executing the screening tool with required fields.
- Batch-process a queue of customer verifications by discovering tools, ensuring an ACTIVE connection, and running multiple tool slugs in a single session.
- Integrate Fraudlabs Pro checks into an order fulfillment pipeline, updating memory state between steps for auditability.
- Migrate an existing automation to use live tool schemas to prevent failures caused by deprecated tool slugs.
- Handle pagination in tool discovery responses and continue fetching until all relevant tools are retrieved.
