openweather-api-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/openweather-api-automation --openclawOpenweather 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
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Openweather API connection via
RUBE_MANAGE_CONNECTIONSwith toolkitopenweather_api - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitopenweather_api - 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: "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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/openweather-api-automation/SKILL.mdView on GitHub Overview
This skill automates Openweather API operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas via RUBE_SEARCH_TOOLS before executing any workflow and uses RUBE_MANAGE_CONNECTIONS and RUBE_MULTI_EXECUTE_TOOL to run tools.
How This Skill Works
You first discover available tools using RUBE_SEARCH_TOOLS with a use_case for Openweather API operations, then verify your Openweather connection via RUBE_MANAGE_CONNECTIONS, and finally execute a tool with RUBE_MULTI_EXECUTE_TOOL including memory and session_id. Tool schemas are dynamic, so always fetch them first to ensure correct slugs and arguments.
When to Use It
- When you need a specific Openweather operation and want to use the latest tool schemas.
- When implementing a new workflow against the Openweather toolkit and you must fetch tool slugs first.
- When establishing or rechecking the Openweather API connection via RUBE_MANAGE_CONNECTIONS.
- When chaining multiple Openweather tools in a single session, reusing session IDs.
- When handling paginated Openweather responses and tokens from tool outputs.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS with use_case: 'Openweather API operations' to retrieve current tool slugs.
- Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ['openweather_api'] and verify the session shows ACTIVE.
- Step 3: RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory: {}, and the active session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before tooling to get current tool slugs and schemas.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs for ongoing workflows and manage pagination tokens.
Example Use Cases
- Discover tools for Openweather API operations and run a current weather query using the returned slug.
- Fetch a 5-day forecast by selecting the relevant tool slug from search results.
- Establish a new openweather_api connection and verify ACTIVE status.
- Run a sequence of tools in a single session to build a weather report, reusing session_id.
- Handle paginated responses by continuing with tokens until complete.
