How do I start using rafflys-automation?

Follow the Quick Start steps to connect, discover tools, and execute tools; ensure RUBE_SEARCH_TOOLS returns tool slugs and input schemas.

No. Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server; no API keys required.

What if tool schemas change?

Always run RUBE_SEARCH_TOOLS before executing; update slugs and arguments according to the latest schemas.

rafflys-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Rafflys Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/rafflys

Prerequisites

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

Step 2: Check Connection

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

Overview

rafflys-automation automates Rafflys operations using Composio's Rafflys toolkit via Rube MCP. It enforces discovering current tool schemas before each run to adapt to changes and avoid hard-coded slugs. This creates repeatable Rafflys workflows that connect, discover tools, and execute tasks reliably.

How This Skill Works

You first fetch up-to-date tool slugs and input schemas with RUBE_SEARCH_TOOLS. Next, verify an ACTIVE Rafflys connection using RUBE_MANAGE_CONNECTIONS and execute the chosen tool through RUBE_MULTI_EXECUTE_TOOL, supplying the correct arguments and a memory object. Throughout the workflow, reuse session IDs where appropriate and always include memory in multi-execute calls.

When to Use It

When you need end-to-end Rafflys automation from discovery to execution
When tool schemas change and you must fetch current slugs before running
When setting up a new Rafflys workflow and establishing a connection
When batching multiple Rafflys tasks in a single session for efficiency
When you want repeatable Rafflys operations with consistent session management

Quick Start

Step 1: Ensure Rube MCP is connected and run RUBE_SEARCH_TOOLS to fetch current Rafflys tool schemas
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["rafflys"] and confirm the status is ACTIVE
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, providing memory and a valid session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas
Check that 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 generate new ones for new workflows

Example Use Cases

Automate a daily Rafflys data synchronization by discovering tools and executing a set of tasks in a single session
Onboard a Rafflys integration by connecting, discovering tools, and running an initial workflow
Batch-run multiple Rafflys operations, such as creation, updates, and status checks, in one go
Update an existing Rafflys automation when tool schemas change by re-discovering tools
Migrate ad-hoc Rafflys tasks from manual steps into a repeatable automated script

Frequently Asked Questions

Add this skill to your agents