Community recipe · Tool workflows

Assemble a location-specific severe-weather visual brief

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Preparing a location-specific weather brief requires bringing current conditions, severe outlooks and relevant model imagery together without losing geographic context.

Agent job

Check weather conditions and severe outlooks and retrieve explicitly requested model fields for a bounded location.

Expected output

A geographically focused image set for a weather brief.

Where this framing comes from

Core problem: Editorial purpose framing
Agent job: Editorial purpose framing
Expected output: Editorial purpose framing
Relevant job roles: Editorial purpose framing
Benefit type: Editorial purpose framing

Editorial framing and outcome limits

Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Case-specific decision guidance · untested

Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

A researcher preparing a weather brief may gather imagery with different geographic bounds, issue times and forecast periods. Displaying the images together can suggest agreement even when they describe different places or moments.
A labelled image manifest could make those differences visible before a human interprets the brief. The proposed aid would organize requested evidence, while current official warnings and operational decisions remain separate checks.

Why an agent / simpler alternative

Useful judgment: Match requested fields to a bounded location and detect incompatible image timestamps or extents.
Simpler alternative: Use an official forecast page when only a straightforward local outlook is needed.
Unsuitable when: The output would substitute for emergency instructions or expert severe-weather interpretation.

Proposed inputs

Name
Brief specification
Owner
Brief owner
Minimum scope
Location bounds, relevant period and explicitly requested model fields
Quality check
Confirm coordinates, local time and requested image scope.
Name
Weather evidence metadata
Owner
Approved source owner
Minimum scope
Conditions, outlook and image issue/valid times
Quality check
Check geographic coverage and source timestamps.

Access and setup — proposed or unknown

Proposed minimum: Read-only approved weather sources; synthetic metadata check before image retrieval.
Compatibility unknowns: Unknown: exact runtime, regional tool coverage, image availability and data freshness.
External actions requiring approval: Expanding requested imagery, distributing the brief or initiating operational notifications.

Expected deliverable and review checks

Proposed artifact: Bounded image set with field labels, issue/valid times and geographic coverage notes.
Critical checks: All imagery matches the requested location and period.
Forecast imagery is distinguishable from observed conditions and official outlooks.
Missing output evidence: No live weather retrieval or visual-brief validation occurs in this overlay.

Failure signals and proposed responses

Signal
Images share an issue time but have different valid times.
Why it matters
A viewer could infer a single weather state from incompatible frames.
Proposed response
Separate them and label each period explicitly.
Signal
The location falls outside the selected tool’s coverage.
Why it matters
The image set may omit or misrepresent the area.
Proposed response
Stop retrieval and verify an approved geographically appropriate source.

Effort and cost — unknown

Setup work: Define geographic bounds and requested fields.
Ongoing review: Check timestamps, coverage and interpretation with a qualified reviewer.
Unknowns: Unknown: image costs, retrieval limits and expert-review effort.

First check — proposed, unexecuted

Status: proposed_unexecuted
Synthetic fixture: Invented image metadata includes two valid periods and one map that excludes the requested location.
Acceptance checks: Mismatched periods are labelled separately.
Out-of-area imagery is rejected.
Stop conditions: Urgent safety advice or unsupported meteorological interpretation is required.

Limits

Editorial evidence-assembly check; no weather condition or forecast accuracy is established.

Tasks: General workflows

Useful for: Researcher Operations manager

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.

Hermes AgentIndependent testing: No

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://github.com/FahrenheitResearch/hermes-weather-plugin/blob/main/skill.md ↗

Attributed to: FahrenheitResearch

Community recipe

Original action type: tool_action
What the source supports: Directs Hermes to check weather conditions and severe outlook, then retrieve requested model fields as a geographically bounded image set for a weather brief.
Source outcome limits: This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Evidence attribution caveat: This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description: Skill restricts image calls to explicit requests and routes international locations to the global-weather tool.
Named tools: Hermes Agent, NWS, SPC, Open-Meteo, rusbie, metrust
Model or version: Unknown
Publication date: Unknown
Source last checked: 2026-10-14
Demonstrated in Canada: Unknown
Canadian availability: Unknown
Proposed Canadian adaptation: Proposed only: use global data for Canadian locations and cross-check authoritative Canadian warnings; do not transfer US radar/alert coverage claims to Canada.
Recommended approval boundaries: Human checks source time, model coverage and uncertainty; safety-critical travel or emergency decisions stay with people and official authorities.