What is the first thing I should do when starting stormglass-io-automation?

Verify Rube MCP is connected and confirm RUBE_SEARCH_TOOLS responds to fetch current tool schemas before any execution.

How do I ensure the Stormglass IO connection is ready?

Use RUBE_MANAGE_CONNECTIONS with the stormglass_io toolkit and confirm the connection status is ACTIVE before running tools.

What if tool schemas change and I have hard-coded slugs?

Always re-run RUBE_SEARCH_TOOLS to get the latest slugs and schemas; do not hardcode values.

stormglass-io-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Stormglass IO Automation via Rube MCP

Automate Stormglass IO operations through Composio's Stormglass IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/stormglass_io

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["stormglass_io"]
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 Stormglass IO-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `stormglass_io`
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/stormglass-io-automation/SKILL.md

View on GitHub

Overview

Automates Stormglass IO operations through Composio's Stormglass IO toolkit using Rube MCP. It emphasizes discovering current tool schemas first to adapt to changes and ensures a validated ACTIVE connection before running workflows.

How This Skill Works

First, discover available Stormglass IO tools with RUBE_SEARCH_TOOLS. Then establish and verify an ACTIVE Stormglass IO connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, providing the required inputs and always including memory.

When to Use It

When starting a Stormglass IO workflow and tool schemas may have changed since last use
When establishing or re-validating a Stormglass IO connection
When selecting a tool slug to execute after discovery
Before running a workflow across multiple tools (session reuse)
When needing to bulk-run tasks or future expansions (RUBE_REMOTE_WORKBENCH)

Quick Start

Step 1: Ensure Rube MCP is connected and RUBE_SEARCH_TOOLS responds
Step 2: Manage the Stormglass IO connection with RUBE_MANAGE_CONNECTIONS and confirm ACTIVE
Step 3: Discover tools, pick one, and execute with RUBE_MULTI_EXECUTE_TOOL including memory

Best Practices

Always search for current tool schemas first using RUBE_SEARCH_TOOLS before any execution
Check that the Stormglass IO connection is ACTIVE via RUBE_MANAGE_CONNECTIONS prior to runs
Use exact field names and types from the tool search results, do not guess
Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and generate new ones only for new workflows

Example Use Cases

Discover Stormglass IO tools with RUBE_SEARCH_TOOLS, then execute a selected slug using RUBE_MULTI_EXECUTE_TOOL with required inputs
Establish a Stormglass IO connection with RUBE_MANAGE_CONNECTIONS and confirm ACTIVE before running any tasks
Run a precise tool slug from discovered results, ensuring input fields match the schema and memory is provided
Perform bulk Stormglass IO tasks via RUBE_REMOTE_WORKBENCH and the run_composio_tool() workflow
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs prior to execution

Frequently Asked Questions

Add this skill to your agents