home / skills / composiohq / awesome-claude-skills / weathermap-automation

weathermap-automation skill

safe

/weathermap-automation

This skill automates Weathermap tasks via Rube MCP, always discovering current tool schemas before execution to ensure accurate, up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill weathermap-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: weathermap-automation
description: "Automate Weathermap tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Weathermap Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/weathermap](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `weathermap`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Weathermap tasks using Composio’s Weathermap toolkit via a Rube MCP connection. It coordinates tool discovery, connection checks, and multi-tool execution so you can run reliable, schema-compliant operations. Always search available tools first to pick the correct schemas and avoid hardcoded arguments.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover current tool slugs and input schemas, then verifies an active Weathermap connection via RUBE_MANAGE_CONNECTIONS. It executes tasks through RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs) while passing an explicit memory object and reusing session IDs. The flow includes pagination handling and schema validation to prevent runtime errors.

When to use it

Automate map generation or updates in Weathermap at scale
Run scheduled or bulk Weathermap operations through Composio tools
Integrate Weathermap actions into broader agent workflows that require reliable tool discovery
Perform multi-step sequences that need session reuse and memory persistence
When tool schemas may change frequently and you must avoid hardcoded inputs

Best practices

Always call RUBE_SEARCH_TOOLS at the start of any workflow to fetch current schemas and recommended execution plans
Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools
Use exact field names and types returned by tool discovery—do not guess or map fields manually
Include a memory parameter (even an empty {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs within a single workflow; generate new sessions for distinct workflows
Check responses for pagination tokens and iterate until you’ve fetched all pages

Example use cases

Discover and run a Weathermap tool to generate a live weather overlay for a dashboard
Batch-update multiple Weathermap layers using RUBE_MULTI_EXECUTE_TOOL with schema-compliant arguments
Run a remote workbench job to perform bulk export or data ingestion across maps
Build an agent that conditionally calls Weathermap tools after validating connection and available schemas
Schedule recurring map refreshes where each run reuses the same session and memory object

FAQ

What must I do before executing any tool?

Always run RUBE_SEARCH_TOOLS to get up-to-date tool slugs and schemas, then confirm the Weathermap connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.

Do I need API keys to use Rube MCP?

No API keys are required—add the MCP endpoint (https://rube.app/mcp) to your client configuration and use the Rube MCP endpoints.

What if a tool schema changes mid-workflow?

Detect schema changes by re-running RUBE_SEARCH_TOOLS. Avoid hardcoded slugs/args and validate incoming schemas before invoking tools.