openweather-api-automation

通过 Rube MCP 自动执行 OpenWeather API 查询与天气数据流程编排。

来源

GitHub

更新于

2026-06-07

// 安全评估低风险

仅提示词，不执行代码
开源可审计

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "openweather-api-automation" 技能：
1. 下载 https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/openweather-api-automation/SKILL.md
2. 保存为 ~/.claude/skills/openweather-api-automation/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

查询城市实时天气

输入

先搜索可用工具及当前 schema，然后通过 Rube MCP 调用 OpenWeather API，查询上海的实时天气，并用中文返回温度、体感温度、湿度、风速和天气概况。

预期产出

返回结构化的上海实时天气信息摘要，包含关键气象指标。

获取未来天气预报

输入

先搜索工具与最新 schema，再通过 Rube MCP 调用 OpenWeather API，获取北京未来 5 天的天气预报，并整理成按日期分组的中文清单，标出最高温、最低温和降雨概率。

预期产出

输出未来 5 天按日期整理的天气预报，便于查看趋势。

批量拉取多城市天气

输入

先搜索当前可用工具和参数 schema，然后通过 Rube MCP 批量调用 OpenWeather API，获取东京、首尔、新加坡和悉尼的当前天气，最后输出对比表格，包含温度、湿度和天气状态。

预期产出

生成多城市天气对比结果，适合快速分析与汇报。

// 文档

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

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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit openweather_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_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`