Skip to content

FrancyJGLisboa/agent-skills-platform / .agents/skills/live-weather-briefing-skill

live-weather-briefing-skill

Verified

Create a current, source-linked weather briefing for a named city using the Open-Meteo geocoding and forecast APIs. Activate for requests such as "what is the weather in Sao Paulo?", "prepare a current weather briefing for Tokyo", or "get today's live conditions for New York". Do not use for travel booking, weather alerts, historical climatology, or safety-critical decisions.

/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

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall