What is securitytrails-automation?

A Composio skill that automates Securitytrails operations via Rube MCP, guiding tool discovery, connection management, and tool execution.

Do I need API keys to use this skill?

No API keys are required—just configure the Rube MCP endpoint and ensure the Securitytrails connection is active.

How do I handle changing tool schemas?

Always run RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas, then proceed with execution using the latest definitions.

securitytrails-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Securitytrails Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/securitytrails

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["securitytrails"]
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 Securitytrails-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `securitytrails`
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/securitytrails-automation/SKILL.md

View on GitHub

Overview

Automates Securitytrails operations using Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas before execution and ensuring an active Securitytrails connection.

How This Skill Works

The workflow starts by discovering available tools with RUBE_SEARCH_TOOLS to pull current slugs and input schemas. It then verifies the Securitytrails connection via RUBE_MANAGE_CONNECTIONS and finally executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and proper arguments.

When to Use It

When you need to run a Securitytrails operation without manual UI interaction
When tool schemas change and you must fetch current slugs and arguments
To automate repetitive Securitytrails tasks within a defined workflow
When onboarding or provisioning a new Securitytrails integration via Rube MCP
When orchestrating multi-step tasks that require session reuse and memory across steps

Quick Start

Step 1: Verify Rube MCP is connected and RUBE_SEARCH_TOOLS responds
Step 2: Use RUBE_MANAGE_CONNECTIONS with toolkit 'securitytrails' to ensure ACTIVE status
Step 3: Discover a tool with RUBE_SEARCH_TOOLS and execute it with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and arguments

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas and avoid hardcoded slugs
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the discovered tool schemas
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

Automate a daily Securitytrails domain status check by discovering the appropriate tool slug and executing it in a single session
Create a bulk domain risk assessment workflow that discovers multiple tools and runs them sequentially using RUBE_MULTI_EXECUTE_TOOL
Onboard a new Securitytrails integration by establishing a connection and running a setup workflow
Handle schema changes gracefully by always re-searching tools before each run to fetch current slugs
Debug a failed run by inspecting tool schemas with RUBE_GET_TOOL_SCHEMAS and updating arguments accordingly

Frequently Asked Questions

Add this skill to your agents