$ ~/registry/skill/composiohq-composio-skills-stormglass-io-automation

SKILL

stormglass-io-automation

Name: stormglass-io-automation
Author: Composio

Automate Stormglass IO weather data queries and integrations 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 is an open-source, prompt-only skill that mainly guides use of Rube MCP/Composio Stormglass IO tooling, with no direct evidence of local code execution or built-in secret collection. Overall risk is low, but network egress and third-party account authorization still warrant attention.

CredentialsCaution

The material says there are no API keys, but it requires an ACTIVE `stormglass_io` connection via `RUBE_MANAGE_CONNECTIONS` and instructs the user to complete an auth link, implying third-party tokens/authorizations are likely handled by Rube/Composio. The skill itself does not appear to request local environment secrets, but normal account-authorization risk remains.

Network egressCaution

The README explicitly instructs adding the remote MCP server `https://rube.app/mcp` and performing actions through Composio's Stormglass IO toolkit; tool discovery, connection management, execution requests, and related task data may therefore be sent to that remote service. This egress is consistent with the stated function and appears to be normal remote-tool behavior, with no clear evidence of unrelated endpoints.

Code executionLow risk

Based on the provided material, this is a prompt-only documentation-style skill with no auditable local scripts, install commands, or instructions to spawn local processes. While it guides use of remote tool capabilities such as `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`, there is no direct evidence of local code-execution privileges being granted.

Data accessCaution

The material does not show local filesystem read/write behavior, but it is designed to perform actions through an authorized Stormglass IO connection and therefore can access data or resources in that third-party account. There is no visible request for local data access beyond the stated use case, but users should treat it as capable of operating on external business data.

Supply chainLow risk

The source is a public GitHub repository marked as open-source, with strong community adoption (~64.7k stars), which are meaningful risk-reducing signals. However, the repository appears to be a skill collection rather than a dedicated source repo for this single skill, and the license and maintenance status are not clearly stated, so upstream MCP/Composio documentation and implementation should still be reviewed before use.

Recommendations

Only add `https://rube.app/mcp` after confirming trust in Rube/Composio, and review their privacy and data-handling terms.
Use least-privilege authorization for the Stormglass IO connection and avoid granting unnecessary data scope or write access.
Before production use, test with a non-sensitive account to verify `RUBE_SEARCH_TOOLS`, the connection flow, and what data fields are actually sent out.
Log and periodically review third-party connection status, session ID handling, and the set of executable tools.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate API Sports queries and data workflows through Rube MCP.

ComposioGet→

$ loading_