What is recallai-automation?

It is a skill that automates Recallai tasks through the Rube MCP integration, requiring an active connection and up-to-date tool schemas.

Do I always need to search for tool schemas first?

Yes. RUBE_SEARCH_TOOLS fetches current tool slugs and input schemas, which can change and should not be hard-coded.

How should I handle memory and session management?

Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls and reuse session IDs within a workflow; generate new sessions for distinct workflows.

recallai-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Recallai Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/recallai

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Recallai operations through Composio's Rube MCP integration. This guide emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution to stay up to date, then connecting and running tools via Recallai.

How This Skill Works

You first discover available tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and input schemas. Then use RUBE_MANAGE_CONNECTIONS to ensure an ACTIVE recallai connection, and finally execute tools with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id. This pattern keeps tool definitions dynamic and protects against schema changes.

When to Use It

You need to run Recallai tasks automatically on a schedule or in response to events.
Tool schemas change and you want to fetch current slugs and args before running.
You want to validate and establish an ACTIVE Recallai connection prior to execution.
You need to chain or bulk-run multiple Recallai tools in a single workflow.
You must include memory and reuse session IDs to maintain context across steps.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds and then call RUBE_MANAGE_CONNECTIONS with toolkit recallai; complete any auth flow if prompted.
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with the proper memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs for a workflow; create new ones for new workflows and watch pagination.

Example Use Cases

Automate a weekly Recallai report by discovering the relevant tool, connecting, and executing with a memory object to preserve context.
Dynamically select a Recallai operation based on tool schemas returned by RUBE_SEARCH_TOOLS and execute with RUBE_MULTI_EXECUTE_TOOL.
Script validates ACTIVE connection via RUBE_MANAGE_CONNECTIONS before each run to prevent failures.
Chain multiple Recallai tools in a single session to complete a complex workflow with memory and session reuse.
Use RUBE_REMOTE_WORKBENCH or RUBE_GET_TOOL_SCHEMAS for bulk schema fetches and bulk tool execution.

Frequently Asked Questions

Add this skill to your agents