algolia-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/algolia-automation --openclawAlgolia Automation via Rube MCP
Automate Algolia operations through Composio's Algolia toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/algolia
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Algolia connection via
RUBE_MANAGE_CONNECTIONSwith toolkitalgolia - 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 toolkitalgolia - 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: "Algolia 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 Algolia task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["algolia"]
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 Algolia-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit algolia |
| 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/algolia-automation/SKILL.mdView on GitHub Overview
This skill automates Algolia operations through Composio's Algolia toolkit using Rube MCP. It emphasizes discovering up-to-date tool schemas with RUBE_SEARCH_TOOLS before execution and managing Algolia connections to ensure workflows run smoothly.
How This Skill Works
The workflow starts by discovering available Algolia tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and schemas. Next, it checks or establishes an active Algolia connection via RUBE_MANAGE_CONNECTIONS. Finally, it executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory object and a session_id, while reusing sessions when appropriate.
When to Use It
- You need to perform an Algolia operation after discovering available tools and their schemas.
- You must connect or verify an active Algolia connection before running any workflows.
- You want to execute a discovered tool with the correct arguments and a session context.
- You need to fetch the latest tool schemas or handle pagination when listing tools.
- You plan to perform bulk Algolia tasks using RUBE_REMOTE_WORKBENCH or other bulk execution paths.
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 connect with RUBE_MANAGE_CONNECTIONS (toolkit: algolia).
- Step 3: Run RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug and memory object.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool slugs and schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the tool search results.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and generate new ones for new workflows.
Example Use Cases
- Discover tools for Algolia operations with RUBE_SEARCH_TOOLS and then run a specific tool slug to reindex an index.
- Establish an Algolia connection via RUBE_MANAGE_CONNECTIONS, confirm ACTIVE, then execute a discovery-based operation.
- Execute a discovered tool with arguments sourced from the tool schemas and a given session_id.
- Use RUBE_REMOTE_WORKBENCH to perform bulk Algolia tasks via run_composio_tool().
- Retrieve the full tool schemas with RUBE_GET_TOOL_SCHEMAS to keep tool choices up to date.
