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

SKILL

exa-automation

Name: exa-automation
Author: Composio

Automate Exa search tasks and workflows through Rube MCP efficiently.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is essentially a prompt-style workflow guide and does not itself declare local code execution, file access, or direct secret requirements. Its main security consideration is reliance on remote Rube MCP/Composio and an Exa connection, so attention should focus on external service boundaries and what data may be sent during actual tool execution.

CredentialsCaution

The material states the skill itself requires no keys, but it requires establishing an Exa connection via RUBE_MANAGE_CONNECTIONS and completing setup through a returned auth link. This implies credentials are likely handled by an external MCP/integration service, so token scope and session handling are not visible at the skill layer and should be reviewed.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint https://rube.app/mcp and using Composio's Exa toolkit for remote tool discovery, connection checks, and tool execution. Workflow inputs, query parameters, and potentially business data may be sent to these declared external services as part of normal operation.

Code executionLow risk

Based on the provided material, this is a prompt-only skill that mainly instructs use of existing MCP tools. It does not declare starting local processes, running scripts, or requesting additional system privileges. Any execution capability comes from external MCP tools rather than the skill itself.

Data accessCaution

The material does not declare direct access to local files or databases, but it does direct users to send task parameters to remote MCP tools and may retain workflow context in session/memory. You should therefore assume Exa-related input data is processed by external services, though no excessive local data permissions are explicitly requested.

Supply chainLow risk

The source is an open GitHub repository with very high community adoption (~64.9k stars), which materially lowers supply-chain risk. The visible skill content is mainly documentation/prompt template material and is therefore relatively auditable. Remaining caveats are the missing license declaration and unknown maintenance status, which merit follow-up review.

Recommendations

Review the privacy, retention, and logging policies for rube.app/mcp, Composio, and Exa before connecting.
Inspect OAuth/token scopes during Exa connection setup and grant only the minimum permissions required.
Avoid placing unnecessary sensitive data in RUBE_SEARCH_TOOLS or RUBE_MULTI_EXECUTE_TOOL arguments.
Validate in a controlled test environment which remote tools are actually invoked and what fields are transmitted.

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 "exa-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/exa-automation/SKILL.md
2. Save it as ~/.claude/skills/exa-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Exa Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/exa

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["exa"]
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 Exa-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `exa`
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 Algolia search and index management tasks through Rube MCP.

ComposioGet→

$ loading_