Do I need API keys to use seismic-automation?

No API keys are required. You only need to add the MCP endpoint (https://rube.app/mcp) and ensure proper connectivity.

Why must I call RUBE_SEARCH_TOOLS before executing?

Tool schemas change frequently; searching first ensures you use current slugs and correct argument names.

What happens if the connection is not ACTIVE?

You should follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup, then re-check until the status shows ACTIVE before execution.

seismic-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Seismic Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/seismic

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Seismic operations through Composio's Seismic toolkit using Rube MCP. This workflow emphasizes fetching current tool schemas before execution to adapt to updates. It streamlines discovery, connection management, and tool execution for seismic tasks.

How This Skill Works

The skill uses RUBE_SEARCH_TOOLS to discover tool slugs and input schemas for seismic tasks, then uses RUBE_MANAGE_CONNECTIONS to ensure an active seismic connection, and finally runs tools with RUBE_MULTI_EXECUTE_TOOL, including a memory payload. Always include memory in execute calls and reuse session IDs within workflows.

When to Use It

When you need to automate repetitive seismic operations with dynamic tool schemas
When tool schemas may change and you must fetch current slugs before execution
When establishing a new seismic workflow: connect, discover, then execute
When performing bulk or batch seismic tasks via RUBE_REMOTE_WORKBENCH
When validating or auditing tool schemas with RUBE_GET_TOOL_SCHEMAS to ensure compatibility

Quick Start

Step 1: Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm available seismic tool schemas
Step 3: Discover tools, ensure ACTIVE connection via RUBE_MANAGE_CONNECTIONS, and execute a tool with RUBE_MULTI_EXECUTE_TOOL (include memory and session_id)

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas
Verify ACTIVE status via RUBE_MANAGE_CONNECTIONS before executing any tool
Use exact field names and types from the tool schemas; avoid hardcoding
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and handle pagination in search results

Example Use Cases

Discover seismic operations tool slugs and execute a target tool with arguments derived from the schema
Establish seismic connection, verify it is ACTIVE, then run a discovered tool slug with proper memory
Retrieve full tool schemas with RUBE_GET_TOOL_SCHEMAS to tailor arguments before run
Execute multiple seismic tasks in bulk using RUBE_REMOTE_WORKBENCH and run_composio_tool()
End-to-end workflow: search tools, manage connection, execute tool, and log results

Frequently Asked Questions

Add this skill to your agents