severe-weather

Use when conditions include storms, flooding, heat waves, or other hazards.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./examples/agent/src/mastra/agents/weather-fs/skills/severe-weather/SKILL.md

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is exceptionally lean and well-structured, with a single clearly signaled reference that exists in the bundle and an unambiguous single-step workflow.

Dimension	Reasoning	Score
Conciseness	Two lean sentences with no concept padding or over-explanation; assumes Claude's competence and every token earns its place, matching anchor 5.	5 / 5
Actionability	'lead with a one-line safety note before the forecast' and 'Consult references/thresholds.md' give concrete, directive guidance, but the content of the safety note is left unspecified, leaving a minor gap below fully copy-paste-ready.	4 / 5
Workflow Clarity	A simple single-purpose skill with an unambiguous sequence (safety note then forecast); no destructive/batch operation applies, so the cap-3 rule does not bind and the simple-skill exception supports a 5.	5 / 5
Progressive Disclosure	The body is a clear overview that signals a single, verified one-level-deep reference (references/thresholds.md exists) with no inlined bulk content or nested references, matching anchor 5.	5 / 5
	Total	19 / 20 Passed

Description

42%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has a strong, explicit trigger clause and decent natural hazard keywords, but it omits any statement of what the skill actually does, leaving the 'what' half of completeness unaddressed.

Suggestions

Add a concrete 'what' clause, e.g. 'Generates weather forecasts with a leading safety note' before the 'Use when' trigger.

Expand trigger keywords to cover common synonyms such as hurricanes, tornadoes, blizzards, and extreme heat/cold.

State the skill's output more explicitly so it is distinguishable from a plain weather forecast skill.

Dimension	Reasoning	Score
Specificity	Names the hazard-weather domain and lists several trigger conditions ('storms, flooding, heat waves, or other hazards') but states no concrete actions the skill performs, matching anchor 2 ('Names the domain but actions are minimal or generic').	2 / 5
Completeness	An explicit 'Use when...' clause answers 'when' clearly, but there is no statement of what the skill does, fitting anchor 2 ('only "when" is present without "what"').	2 / 5
Trigger Term Quality	'storms, flooding, heat waves, or other hazards' are natural user phrasings, giving good keyword coverage, though common synonyms (hurricane, blizzard, tornado, extreme heat/cold) are missing.	4 / 5
Distinctiveness Conflict Risk	The severe-weather niche with specific hazard triggers is mostly distinct with only minor overlap risk with a generic weather skill; 'or other hazards' adds slight breadth that keeps it just below a 5.	4 / 5
	Total	12 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: mastra-ai/mastra
Path: examples/agent/src/mastra/agents/weather-fs/skills/severe-weather/SKILL.md
Commit: 3b0d190

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.