Agent skill

Tempest

by magnus919 in magnus919/agent-skills

Query hyper-local weather from a WeatherFlow Tempest station over its REST API and the hub's local UDP broadcast: current conditions, forecast, historical observations, and real-time decoded…

MITAuto-check passedBackend & APIs

Install Tempest

skills CLI
$ npx skills add magnus919/agent-skills --skill tempest -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install magnus919/agent-skills tempest --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tempest .claude/skills/tempest && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tempest
GitHub stars
115
Token cost
~3.3k tokens
SKILL.md length
1,226 words
Files
9 (incl. scripts, references)
Skills in repo
131
Repo updated
First seen
Licence
MIT

At a glance

Query hyper-local weather from a WeatherFlow Tempest station over its REST API and the hub's local UDP broadcast: current conditions, forecast, historical observations, and real-time decoded…

  • Works in 2 steps: Create a personal access token: sign in… → Export it
  • The user asks about weather
  • SKILL.md covers Setup, Essential Commands, UDP broadcasts from your hub… and Multi-step pipeline recipes, plus 7 more sections
  • Runs Python scripts from its folder; calls jq; needs TEMPEST_TOKEN

What it does

Tempest is an agent skill from magnus919/agent-skills. Query hyper-local weather from a WeatherFlow Tempest station over its REST API and the hub's local UDP broadcast: current conditions, forecast, historical observations, and real-time decoded datagrams (obsst, rapidwind, evtprecip, evtstrike, hubstatus). Use when the user asks about weather, temperature, rain, wind, humidity, or forecast data from their own Tempest/WeatherFlow station, or wants to parse the hub's UDP port 50222 broadcast. Do not use this skill for generic or city forecasts without a Tempest…

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts and reference files (for example `README.md`, `evals/evals.json` and `references/cli-worked-recipes.md`). Compatibility notes: Requires TEMPESTTOKEN env var for REST (create it in the Tempest web app under Settings - Data Authorizations), Python 3.8+, and requests. UDP listening needs…

It sits in Backend & APIs, covering REST APIs. The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.

When your agent uses it

  • The user asks about weather
  • Forecast data from their own Tempest/WeatherFlow station
  • Wants to parse the hubs UDP port 50222 broadcast
  • City forecasts without a Tempest station (public weather services serve those)

Example prompts

  • “/tempest”

Requirements

  • Python 3
  • A credential in TEMPEST_TOKEN
  • A credential in YOUR_TOKEN
  • Compatibility (from SKILL.md): Requires TEMPEST_TOKEN env var for REST (create it in the Tempest web app under Settings -> Data Authorizations), Python 3.8+, and `requests`. UDP listening needs a Tempest hub on the LAN and no token. `--help` and `--dry-run` work without credentials.

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Create a personal access token: sign in to the Tempest web app
  2. Export it

What it can do on your machine

Read from SKILL.md and the folder at commit 22b4723. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • TEMPEST_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires TEMPEST_TOKEN env var for REST (create it in the Tempest web app under Settings -> Data Authorizations), Python 3.8+, and `requests`. UDP listening needs a Tempest hub on the LAN and no token. `--help` and `--dry-run` work without credentials.

    From compatibility in the SKILL.md frontmatter.

Context cost

Tempest loads about 3.3k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 197 tokens; SKILL.md has 1,226 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~197
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~13k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from magnus919/agent-skills at commit 22b4723, republished under its MIT licence (© magnus919). 1,226 words, ~3,281 tokens.

Download SKILL.mdSave it as .claude/skills/tempest/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
tempest
description
Query hyper-local weather from a WeatherFlow Tempest station over its REST API and the hub's local UDP broadcast: current conditions, forecast, historical observations, and real-time decoded datagrams (obs_st, rapid_wind, evt_precip, evt_strike, hub_status). Use when the user asks about weather, temperature, rain, wind, humidity, or forecast data from their own Tempest/WeatherFlow station, or wants to parse the hub's UDP port 50222 broadcast. Do not use this skill for generic or city forecasts without a Tempest station (public weather services serve those), for Shakespeare's play The Tempest or other literature questions, or for weather hardware from other vendors - the REST endpoints require a personal-use token and the UDP broadcast only exists on a Tempest hub's LAN.
compatibility
Requires TEMPEST_TOKEN env var for REST (create it in the Tempest web app under Settings -> Data Authorizations), Python 3.8+, and `requests`. UDP listening needs a Tempest hub on the LAN and no token. `--help` and `--dry-run` work without credentials.
license
MIT
metadata.tags
weather, tempest, weatherflow, forecast, station, udp, hyper-local
metadata.sources
https://apidocs.tempestwx.com/reference/quick-start, https://weatherflow.github.io/Tempest/api/udp/v171/

tempest — Hyper-local weather from your Tempest station

Drive a WeatherFlow Tempest station from the terminal. Two transports, both first-class: the documented REST API (swd.weatherflow.com/swd/rest, personal-use token) for conditions, forecast, and history — officially the primary data source — and the hub's unauthenticated UDP broadcast on port 50222 for real-time, lowest-latency readings on your LAN. The bundled CLI decodes the positional observation arrays and every UDP message family, keeps --json output metric-native, and converts units only for human display.

Setup

  1. Create a personal access token: sign in to the Tempest web app (tempestwx.com), then Settings → Data Authorizations → Create Token. (This is the documented non-graphical auth method; OAuth exists for web apps but is not what a CLI uses.)
  2. Export it:
bash
export TEMPEST_TOKEN="<YOUR_TOKEN>"

The token travels to the API as a query parameter (?token=...) per the official docs — the CLI handles this. If the env var is not set, the CLI falls back to reading TEMPEST_TOKEN= from ~/.tempest.env (handy for agent subprocesses that skip shell profiles). --help and --dry-run never need a token. UDP listening never needs one either — the hub broadcast is unauthenticated and LAN-only.

Essential Commands

stations — discover your stations and devices
bash
tempest stations                       # names, station ids, device types, serials
tempest stations --json | jq '.stations[] | {station_id, name,
  devices: [.devices[] | {device_id, device_type, serial_number}]}'

Every station response nests a devices array: device_type is ST (the Tempest all-in-one), AR/AIR, SK/SKY, or HB (the hub — it has no observations; always filter it out before querying observations). Run this first when you don't know your ids.

current — latest conditions
bash
tempest current                                       # human-readable, converted
tempest current --json                                # metric-native, jq-ready
tempest current --station-id 12799 --device-id 60526  # pin exact hardware

With one station it auto-selects and picks the best sensor (ST, then SKY/SK, then AIR/AR, skipping HB). Output .observation carries the decoded positional array as named fields with _unit companions.

forecast — current conditions + daily + hourly
bash
tempest forecast                       # current + 5-day daily + next 12 hours
tempest forecast --days 7 --json
tempest forecast --station-id 12799 --days 3

The better_forecast response nests daily/hourly under a forecast wrapper key, and it is unit-selectable (units_temp=c|f and friends, default metric) — the CLI reads the response's units before converting anything.

obs — historical observations
bash
tempest obs --device-id 60526 --days 1       # last UTC day (day_offset)
tempest obs --device-id 60526 --days 7
tempest obs --device-id 60526 --json

--days N maps to the API's day_offset (whole UTC days). The underlying endpoint also accepts time_start/time_end epoch ranges (one-minute resolution guaranteed up to 5 days) — use raw calls for those; see references/rest-api-and-auth.md.

UDP broadcasts from your hub (port 50222, listen-only)

bash
tempest udp listen                          # live stream until Ctrl-C
tempest udp listen --timeout 30             # auto-stop after 30s
tempest udp listen --timeout 60 --json      # one JSON object per datagram
tempest udp listen --show-all               # include hub_status/device_status

Requires being on the same LAN as the hub (routed connectivity is not enough — broadcasts don't cross routers). No token involved. The listener decodes every message family, dispatching on type before touching array positions:

FamilyPayload shapeDecoded fields
obs_st / obs_air / obs_skylist of report rows under obsnamed observation fields
rapid_windONE 3-element array under obwind_speed_mps, wind_direction
evt_precipONE array under evttimestamp (rain started)
evt_strikeONE array under evtdistance_km, energy
hub_status, device_statusnamed fields, no arrayuptime, rssi, seq, voltage, sensor_status

Multi-step pipeline recipes

Discover, then observe
bash
# Stage 1 -> stage 2: stations --json emits integer ids that current consumes
tempest stations --json | jq -r '.stations[].devices[]
  | select(.device_type == "ST") | .device_id' | head -1
tempest current --device-id <DEVICE_ID> --json
Rain watch: yesterday's total, then live rain events
bash
tempest obs --device-id 60526 --days 1 --json \
  | jq '{samples: (.observations | length),
         day_rain_mm: .observations[-1].local_day_rain_accumulation}'
tempest udp listen --timeout 600 --json | jq 'select(.type == "evt_precip")'

obs --json ends with decoded observations carrying local_day_rain_accumulation (mm, number); evt_precip datagrams decode to {type, serial_number, timestamp} — both stages emit typed fields the next stage can consume.

Unit-aware forecast slice
bash
tempest forecast --days 7 --json \
  | jq '{units_temp: .forecast.units.units_temp,
         highs_f: [.forecast.forecast.daily[] | .air_temp_high * 9 / 5 + 32],
         rain_hours: [.forecast.forecast.hourly[]
                      | select(.precip_probability > 30) | .local_hour]}'

The jq math here is safe only because it checks units_temp first — see gotcha 2.

JSON output and jq processing

--json output is metric-native — the raw wire units (m/s wind, mm rain, °C temperature, MB pressure) with _unit companion fields naming each. Convert at the consumption edge:

bash
tempest current --json | jq '{temp_c: .observation.air_temperature,
  temp_f: (.observation.air_temperature * 9 / 5 + 32),
  wind_mph: (.observation.wind_avg * 2.237),
  rain_in: (.observation.rain_accumulation / 25.4)}'

Global flags work in any position: tempest --json current --device-id 60526 and tempest current --device-id 60526 --json are identical. --quiet silences the progress logs (data on stdout, logs on stderr). --dry-run prints a plan object and exits 0 without touching the network.

Show full SKILL.md (670 more words)Show less

Known Gotchas

  1. Observations are positional arrays, not objects. Raw obs rows have no field names; meaning comes from the index (obs_st: 0 epoch, 2 wind avg m/s, 4 wind direction, 6 pressure MB, 7 temperature °C, 12 rain mm, 16 battery V, 17 report interval). Reading index 6 as temperature gives you a plausible-looking wrong number — decode with the CLI or the layout tables in references/observation-layouts-and-units.md.
  2. /better_forecast is unit-selectable, not Celsius-locked. It defaults to metric but honors units_temp=f, units_wind=mph, units_pressure=inhg, units_precip=in. It reports what it used in response.units. Converting an already-Fahrenheit response doubles it (25.4 °C → 77.7 °F → 172 "°F"). Always read units before converting; the CLI does this for you.
  3. UDP message families differ structurally — dispatch on type first. obs families nest rows under obs; rapid_wind carries one array under ob; evt_precip/evt_strike carry one array under evt; hub_status/device_status carry named fields with no payload array. Iterating rapid_wind's ob element-wise is the classic TypeError; the bundled decode_message() shows the correct dispatch.
  4. UDP obs_st rows stop at index 17; REST rows run to 21. The four Nearcast/analysis fields (18–21) exist only in REST responses. Decoders must tolerate both lengths — the CLI emits None for missing tails.
  5. Pressure is MB (millibars), numerically hPa — not kPa. It is also station pressure (raw sensor). The Tempest app's "relative pressure" adds an elevation adjustment; don't compare raw station pressure against the app and conclude the sensor drifted.
  6. Forecast timestamps are epoch integers, never ISO strings. day_start_local, sunrise, sunset, hourly time are epoch seconds; hourly objects carry local_hour (0–23) and local_day (day of month). There is no local_time or time_string field — code expecting one silently falls back to its default branch.
  7. The forecast nests under a forecast wrapper key. data["daily"] is always empty; read data["forecast"]["daily"] and data["forecast"]["hourly"] (the CLI's --json preserves the full response, wrapper and all).
  8. Hubs (HB) have no observations. They only relay. Auto-selection skips them; if you call the API directly, filter device_type == "HB" out before hitting /observations/device/{id} (documented 404 otherwise).
  9. UDP is LAN-only and unauthenticated. Broadcasts don't cross routers and can't be token-gated — anyone on the network can read your station. WeatherFlow officially positions REST/WebSocket as primary and UDP as the off-grid/backup interface.
  10. obs_sky UDP day-rain is always null. Local-day rain accumulation (index 11) is null in UDP SKY broadcasts; REST supplies the real value. Don't build day-rain totals from UDP SKY rows.

When to use

  • The user owns or manages a WeatherFlow Tempest / Air / Sky station and asks about its readings, forecast, or history.
  • Parsing or integrating with the hub's local UDP broadcast (port 50222).
  • Rain/wind/lightning monitoring scripts, dashboards, or home-automation hooks fed from the station.

When not to use

  • Generic city forecasts or users without a station — every endpoint requires the user's own Tempest station and a personal-use token; use a public weather service instead.
  • Shakespeare's play The Tempest, or any literary/meteorological-theory question — this is a station-data CLI, not an encyclopedia.
  • Other vendors' hardware (Netatmo, Ecowitt, Davis, Ambient) — different APIs entirely; no endpoint here will accept their devices.
  • Commercial/network-wide data products — those need WeatherFlow's TempestONE agreements, not a personal token (see the remote developer policy).

Reference Files

FileRead when
references/rest-api-and-auth.mdWorking with REST endpoints directly: token auth, StationSet shapes, observation parameters, forecast units, error signatures
references/udp-broadcast-protocol.mdParsing raw UDP datagrams: port 50222 transport, every message family's layout, the type-dispatch rule
references/observation-layouts-and-units.mdDecoding positional observation arrays by index (obs_st/obs_air/obs_sky, UDP vs REST lengths) and unit conversion tables
references/cli-worked-recipes.mdCopy-paste multi-step CLI recipes with jq stages, dry-run plans, and expected error paths

Available Scripts

  • scripts/tempest — the CLI: stations, current, obs, forecast, udp listen; global --json, --dry-run, --quiet, --verbose accepted in any position; offline dry-run plans for every command.
  • scripts/test_tempest.py — offline suite: canned UDP datagram bytes fed to the decoder (no sockets), mocked REST transport, both pytest and unittest runners.

Prerequisites

  • Python 3.8+ with requests (the only dependency).
  • TEMPEST_TOKEN for REST commands (free, personal use; created in the Tempest web app). UDP listening needs no token, only line-of-sight to the hub's LAN.

© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (scripts, references) in tempest of magnus919/agent-skills.

  • SKILL.md
  • README.md
  • evals/evals.json
  • references/cli-worked-recipes.md
  • references/observation-layouts-and-units.md
  • references/rest-api-and-auth.md
  • references/udp-broadcast-protocol.md
  • scripts/tempest
  • scripts/test_tempest.py

Open the folder on GitHubat commit 22b4723

Compare with similar skills

Tempest next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tempest compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tempest this skillmagnus919/agent-skills115—~3.3kAutomated safety check: PassMIT
Paperclippaperclipai/paperclip99k—~9.6kAutomated safety check: PassMIT
Nodejs Backend Patternsever-works/ever-works16218 repos~4kAutomated safety check: PassAGPL-3.0
OpenAPI to MCP Servermcp-use/mcp-use11k—~5.2kAutomated safety check: PassApache-2.0
Use Yaakmountain-loop/yaak19k—~1.9kAutomated safety check: PassMIT
API DesignerJeffallan/claude-skills12k1 repos~2kAutomated safety check: PassMIT

Similar skills

  • Paperclip

    paperclipai/paperclip

    Interact with the Paperclip control plane API for task coordination and governance.

    99k GitHub stars~9.6k tokensUpdated today
    Backend & APIsAuto-check passed
  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    162 GitHub starsUsed in 18 repos~4k tokens
    Backend & APIsAuto-check passed
  • OpenAPI to MCP Server

    mcp-use/mcp-use

    Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.

    11k GitHub stars~5.2k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Use Yaak

    mountain-loop/yaak

    A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…

    19k GitHub stars~1.9k tokensUpdated 3 days ago
    Backend & APIsAuto-check passed
  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 1 repo~2k tokens
    Backend & APIsAuto-check passed
  • Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView.

    97k GitHub stars~1.2k tokensUpdated today
    Backend & APIsAuto-check: notes

More from magnus919/agent-skills

All 131 skills in this repo
  • Artifact Pyramids

    magnus919/agent-skills

    Organize durable agent research outputs as summaries, analysis, and evidence dossiers.

    115 GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Ascii City Engine

    magnus919/agent-skills

    Build portable, first-person colored ASCII city engines and small GIS-derived city packs.

    115 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Color Management

    magnus919/agent-skills

    Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.

    115 GitHub stars~2.6k tokensUpdated today
    Auto-check: notes
  • Data Scientist

    magnus919/agent-skills

    A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…

    115 GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • Docker Compose

    magnus919/agent-skills

    Use Docker Compose to define, run, debug, and harden multi-container applications.

    115 GitHub stars~2k tokensUpdated today
    Auto-check: notes
  • Fpga Development

    magnus919/agent-skills

    Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.

    115 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Tempest

What does Tempest do?

Query hyper-local weather from a WeatherFlow Tempest station over its REST API and the hub's local UDP broadcast: current conditions, forecast, historical observations, and real-time decoded…. Tempest is an agent skill from magnus919/agent-skills. Query hyper-local weather from a WeatherFlow Tempest station over its REST API and the hub's local UDP broadcast: current conditions, forecast, historical observations, and real-time decoded datagrams (obsst, rapidwind, evtprecip, evtstrike, hubstatus).

When should I use Tempest?

Tempest fits situations like: the user asks about weather; forecast data from their own Tempest/WeatherFlow station; wants to parse the hubs UDP port 50222 broadcast; city forecasts without a Tempest station (public weather services serve those).

How do I install Tempest in Claude Code?

Run `npx skills add magnus919/agent-skills --skill tempest -a claude-code`. Or copy the skill folder (tempest in magnus919/agent-skills) into .claude/skills/tempest in your project. Claude Code loads it when a task matches its description.

How do I install Tempest in Codex?

Run `npx skills add magnus919/agent-skills --skill tempest -a codex`. Or copy the skill folder (tempest in magnus919/agent-skills) into .agents/skills/tempest in your project. Codex loads it when a task matches its description.

Can I use Tempest in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/agent-skills --skill tempest -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tempest, .gemini/skills/tempest, .github/skills/tempest and .opencode/skills/tempest in your project.

What does Tempest need to run?

Going by SKILL.md and its folder, Tempest needs Python for the scripts in its folder, the command-line tools its instructions call (jq) and credentials named TEMPEST_TOKEN. Our summary lists: Python 3; A credential in TEMPEST_TOKEN; A credential in YOUR_TOKEN. Compatibility (from SKILL.md): Requires TEMPEST_TOKEN env var for REST (create it in the Tempest web app under Settings -> Data Authorizations), Python 3.8+, and `requests`. UDP listening needs a Tempest hub on the LAN and no token. `--help` and `--dry-run` work without credentials..

Does Tempest access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Tempest safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Tempest use?

Tempest is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tempest use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.

What are the alternatives to Tempest?

Skills that share tags, products or a category with Tempest: Paperclip (paperclipai/paperclip, 99k stars), Nodejs Backend Patterns (ever-works/ever-works, 162 stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars) and Use Yaak (mountain-loop/yaak, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tempest?

magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 115 GitHub stars. The repository holds 131 skills in this directory. The repository was last updated on October 10, 2026.

Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.