360 Secure SkillHub
360 安全技能中心

wttr.in

该 Skill 借助 OOMOL 的 oo CLI 调用 wttr_in 连接器，执行 get_weather 动作，从 wttr.in 获取当前天气与预报的 JSON 数据。使用前需安装并登录 oo CLI，凭证由 OOMOL 服务端注入；输入输出字段以实时查询的连接器 schema 为准。

oomol
oomol
热度 21.86
最近更新 2026-09-15 12:04:48
分类：生活依赖：第三方 API / 代码执行应用场景：旅行

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-wttr-in
Metadata
name
oo-wttr-in
description
wttr.in (wttr.in). Use this skill for ANY wttr.in request — searching and reading data. Whenever a task involves wttr.in, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"wttr.in","author":"OOMOL","version":"1.0.2","services":["wttr_in"],"icon":"https://static.oomol.com/logo/third-party/wttr_in.png"}

wttr.in

Operate wttr.in through your OOMOL-connected account. This skill calls the wttr_in connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

wttr.in needs no account connection. Assume the oo CLI is installed and signed in. Do not run oo auth login proactively — just run the action. Fall back to First-time setup only when a command actually fails.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "wttr_in" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "wttr_in" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • get_weather — Get current weather and forecast from wttr.in as JSON.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change wttr.in state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources