How do I install the Oo Wttr In skill?

Run npx skillmds@latest add oomol-lab/oo-wttr-in in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Oo Wttr In safe to use?

SkillMD's automated safety review verdict for this skill is WARNING. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: WARNING. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Oo Wttr In?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Oo Wttr In free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Oo Wttr In?

oomol-lab (@oomol-lab) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Oo Wttr In by oomol-lab — Agent Skill

Name: Oo Wttr In
Author: oomol-lab

File contents

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

wttr.in homepage: https://wttr.in/

---name: oo-wttr-indescription: 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.---# wttr.inOperate **wttr.in** through your OOMOL-connected account. This skill calls the `wttr_in` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.## Running an actionwttr.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](#first-time-setup) only when a command actually fails.**1. Inspect the contract** to get the authoritative input/output schema before building a payload:```bashoo connector schema "wttr_in" --action "<action_name>"```**2. Run the action** with a JSON payload that matches the input schema:```bashoo 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 setupThese 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>): ```bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux ``` ```powershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell ```- **Not signed in / authentication error** — sign in to your OOMOL account once: ```bash oo auth login ```- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.## Resources- wttr.in homepage: https://wttr.in/

Frequently asked questions

Oo Wttr In