home / skills / composiohq / awesome-claude-skills / openweather-api-automation

openweather-api-automation skill

safe

This skill automates Openweather API tasks via Composio Rube MCP, enabling tool discovery, connection management, and workflow execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill openweather-api-automation

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

Files (1)

SKILL.md

3.0 KB

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

# Openweather API Automation via Rube MCP

Automate Openweather API operations through Composio's Openweather API toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/openweather_api](https://composio.dev/toolkits/openweather_api)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["openweather_api"]
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 Openweather API-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `openweather_api` |
| 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 Openweather API operations through Rube MCP using Composio's openweather_api toolkit. It provides a repeatable pattern to discover available tools, validate connections, and execute API calls safely. The skill emphasizes always searching tools first to retrieve current schemas and execution plans. It is designed for reliable, schema-compliant automation of weather data tasks.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and recommended plans for the requested Openweather use case. It then verifies or establishes an active connection via RUBE_MANAGE_CONNECTIONS for the openweather_api toolkit. Once tools and connection status are confirmed, it runs RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs) with schema-compliant arguments and an explicit memory object. The workflow reuses session IDs for continuity and handles pagination tokens when responses span multiple pages.

When to use it

Automate recurring weather data pulls for dashboards or analytics.
Fetch current weather, forecasts, or historical data programmatically.
Integrate Openweather responses into downstream pipelines or alerts.
Run bulk or scheduled queries over many locations using remote workbench.
When tool schemas may change frequently and you need schema-first execution.

Best practices

Always call RUBE_SEARCH_TOOLS first to discover current tool slugs and exact input schemas.
Check RUBE_MANAGE_CONNECTIONS and confirm the openweather_api connection is ACTIVE before executing tools.
Pass an explicit memory parameter (even empty) to RUBE_MULTI_EXECUTE_TOOL calls.
Reuse session_id across related steps; generate a new session for distinct workflows.
Respect schema field names and types exactly and handle pagination tokens in responses.

Example use cases

Daily job that collects 7-day forecasts for a list of cities and stores results in a database.
On-demand fetch of current weather and alerts for a specified geofence and trigger downstream notifications.
Bulk historical weather export using RUBE_REMOTE_WORKBENCH to feed a climate analytics pipeline.
Ad-hoc testing: discover available Openweather tools and validate example payloads before building integrations.
Monitor API tool changes by periodically running RUBE_SEARCH_TOOLS and alerting on schema drift.

FAQ

Do I need an API key to use Rube MCP with this toolkit?

No API key is required to connect Rube MCP as an MCP server; however, the openweather_api connection may require authentication steps surfaced by RUBE_MANAGE_CONNECTIONS.

What if a tool slug or schema changes mid-workflow?

Always call RUBE_SEARCH_TOOLS at the start of each workflow or new step. If schemas change, update arguments to match the returned schema and restart the execution with a proper session_id.