live-weather-briefing-skill

live-weather-briefing-skill is a skill for Claude Code from FrancyJGLisboa/agent-skill-creator. It costs 85 tokens per session (594 once invoked), scanned A, original, MIT.

A skill for producing a current, source-linked weather briefing for one named city. It uses Open-Meteo to find the city and retrieve modelled current conditions.

In plain words
What is it for?
Use it to get the current temperature, apparent temperature, wind speed, weather code, and retrieval time for a city.
Why use it?
It avoids guessing when a city name is ambiguous or conditions have changed. The briefing includes the resolved place, observation time, and source URLs.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents).

Part of the live-weather-briefing-skill plugin — 1 skill shipped together

Good fit Use it to get the current temperature, apparent temperature, wind speed, weather code, and retrieval time for a city.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/francyjglisboa/agent-skill-creator/live-weather-briefing-skill
About the project

Agent Skills Platform turns documented work and supporting evidence into tested, installable skills for coding agents. Teams use it to review, publish, maintain, and safely reuse agent workflows, with the catalogue entries serving as skills and plugins built for that ecosystem.

FrancyJGLisboa/agent-skill-creator · 2,378 stars · on GitHub · francyjglisboa.github.io

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add FrancyJGLisboa/agent-skill-creator --skill live-weather-briefing-skill
Clone the repo
git clone --depth 1 https://github.com/FrancyJGLisboa/agent-skill-creator

Made for: Claude Code.

Or install live-weather-briefing-skill, the plugin that ships this one along with the rest of its 1 skill.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for live-weather-briefing-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/francyjglisboa/agent-skill-creator/live-weather-briefing-skill/github.svg)](https://agentmods.dev/skills/francyjglisboa/agent-skill-creator/live-weather-briefing-skill)
Your own site
<a href="https://agentmods.dev/skills/francyjglisboa/agent-skill-creator/live-weather-briefing-skill"><img src="https://agentmods.dev/badge/skills/francyjglisboa/agent-skill-creator/live-weather-briefing-skill/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for live-weather-briefing-skill

Your own site · 80×15
<a href="https://agentmods.dev/skills/francyjglisboa/agent-skill-creator/live-weather-briefing-skill"><img src="https://agentmods.dev/badge/skills/francyjglisboa/agent-skill-creator/live-weather-briefing-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 594 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Data Exfiltration · line 22
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00085 $0.00594
Opus 5 $0.00043 $0.00297
Sonnet 5 $0.00017 $0.00119
Haiku 4.5 $0.00009 $0.00059

Measured 12d ago against content hash b8b70752fa6a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

live-weather-briefing-skill scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

The scan reads SKILL.md. This mod also ships 10 executable files (install.ps1, scripts/dependency_health.py, scripts/evolve.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/live-weather-briefing-skill/SKILL.md · 65 lines

What it actually says

/live-weather-briefing-skill

Create a current weather briefing for one city. Resolve the city through Open-Meteo's geocoding API, then retrieve current conditions from its forecast API. Always show the resolved location, observation time, and source URLs.

Run

python3 scripts/run_pipeline.py --city "Sao Paulo, BR" --output briefing.md

The command makes two live, read-only API requests and writes a Markdown briefing. It never books travel, sends alerts, or changes external data.

Required behavior

  1. Use the first exact geocoding result and show its country and coordinates.
  2. Retrieve current temperature, apparent temperature, wind speed, weather code, and observation time.
  3. State that weather is advisory and include the source URLs.
  4. If a city cannot be resolved or an API response is incomplete, stop with an error; do not invent conditions.

Gotchas

  • Current conditions are model data, not a safety alert. Check local official warnings before decisions involving risk.
  • A city name can be ambiguous. Include a country or region in the request when the city is not unique.
  • Conditions change after retrieval; the briefing's observation time identifies the freshness of this result.

References

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 65 lines · 85 tokens per session scan A b8b70752fa6a

Subscribe to this mod's changes

live-weather-briefing-skill is a skill published in the GitHub repository FrancyJGLisboa/agent-skill-creator (2,378 stars, last pushed 8d ago), licensed MIT. It adds 85 tokens to every session and 594 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.