$ ~/registry/skill/composiohq-composio-skills-algolia-automation

SKILL

algolia-automation

Name: algolia-automation
Author: Composio

Automate Algolia search and index management tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill itself is an open-source prompt-style instruction set with no direct built-in secret requirement or explicit local code/file access, so its baseline risk is low. However, it explicitly depends on remote Rube MCP/Composio services and can connect to an Algolia account to perform actions, so external service interaction and third-party account authorization require attention.

CredentialsCaution

The material says 'No API keys needed,' but the workflow still requires an ACTIVE Algolia connection via `RUBE_MANAGE_CONNECTIONS` and an auth link flow. This means credentials are not absent; they are delegated/managed through a third-party connection flow. Third-party access to the Algolia account should be reviewed for scope and connection handling.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and references Composio docs and an auth flow. When performing Algolia operations, task arguments, session data, and potentially business data will transit through Rube/Composio and related connection services. The endpoint is declared, so this is standard external connectivity, but data should be assumed to leave the local environment.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description. It contains no local install script, shell commands, dependency execution steps, or stated ability to directly spawn local processes or run arbitrary code; its main function is to guide use of remote MCP tools.

Data accessCaution

The material does not claim local filesystem read/write access, but through remote tools it can automate operations against Algolia resources, including bulk actions and session reuse. That implies access to and modification of authorized Algolia indexes/configuration data. No request for local data access beyond the stated purpose is evident.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (64.7k stars), both of which materially lower risk; the skill content itself is auditable. Caveats are that the repository license is unspecified, maintenance status is unknown, and actual execution depends on external Rube/Composio services whose server-side implementation is outside this material.

Recommendations

Before connecting Algolia, verify the exact scopes requested by Rube/Composio and prefer least-privilege or test accounts.
Avoid sending highly sensitive queries, customer data, or production bulk changes through this flow until validated on non-production data.
Confirm that `https://rube.app/mcp` and any auth redirect domains belong to the expected service provider, and review their privacy/data handling policies.
Regularly review and revoke third-party connections, sessions, and integration grants that are no longer needed.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "algolia-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/algolia-automation/SKILL.md
2. Save it as ~/.claude/skills/algolia-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Algolia 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_CONNECTIONS with toolkit algolia
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 algolia
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_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 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

Automate Moz SEO tasks via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_