Do I always have to call RUBE_SEARCH_TOOLS first?

Yes. It fetches current tool schemas and prevents hardcoding slugs that may change.

How do I ensure the Weathermap connection is ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to check status; if not ACTIVE, follow the provided auth link to complete setup.

What should memory contain in RUBE_MULTI_EXECUTE_TOOL calls?

Memory can be an empty object {} but must be included in every execute call; it preserves state across steps.

weathermap-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Weathermap Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/weathermap

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Weathermap operations through Composio's Rube MCP toolkit. Always search for current tool schemas with RUBE_SEARCH_TOOLS before running any workflow to ensure compatibility with updated tools.

How This Skill Works

The skill uses RUBE_SEARCH_TOOLS to discover available Weathermap tools, then RUBE_MANAGE_CONNECTIONS to verify an active Weathermap connection, and finally RUBE_MULTI_EXECUTE_TOOL to run the chosen tool with schema-compliant arguments. If the connection is not ACTIVE, follow the emitted auth link to complete setup, and always include a memory object for each execute call while reusing a session ID across steps.

When to Use It

When starting a Weathermap automation and you need the latest tool schemas before choosing a tool slug.
When connecting to the Weathermap toolkit for the first time and you must verify or activate the connection.
When selecting and executing a tool based on live results from RUBE_SEARCH_TOOLS with proper arguments.
When performing multi-step Weathermap workflows that benefit from session reuse across steps.
When tool schemas or responses paginate and you need to fetch all results reliably.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_SEARCH_TOOLS with use_case set to Weathermap operations to discover available tools and schemas.
Step 3: Execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, provide schema-compliant arguments, include memory: {}, and reuse a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination if present.

Example Use Cases

Discover available Weathermap tools with RUBE_SEARCH_TOOLS and choose a tool slug to run.
Connect to the Weathermap toolkit via RUBE_MANAGE_CONNECTIONS and verify ACTIVE before any execution.
Execute a discovered tool slug using RUBE_MULTI_EXECUTE_TOOL with validated arguments and memory.
Reuse a single session_id across a sequence of Weathermap tasks to maintain context.
Perform a bulk operation after tool discovery using RUBE_REMOTE_WORKBENCH or run_composio_tool().

Frequently Asked Questions

Add this skill to your agents