live-weather-briefing-skill

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.

Quality

92%

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

Quality

Content

93%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.

A well-structured, concise body for a simple single-purpose skill: executable run command, clear required behaviors, useful gotchas, and source references. The only gap is that the multi-step pipeline is described narratively rather than as an explicit stepwise workflow with a validation checkpoint.

Suggestions

Render the pipeline as an explicit numbered sequence (geocode -> fetch current forecast -> render briefing) with a validation checkpoint so the workflow is scanable, mirroring the 'Required behavior' list.

Add a one-line 'Verify' note in the Run section indicating how to confirm the briefing contains the resolved location, observation time, and source URLs before presenting it.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: a copy-paste run command, a short numbered behavior list, three gotchas, and two reference URLs, with no padding or explanations of concepts Claude already knows.	5 / 5
Actionability	Provides a fully executable run command (`python3 scripts/run_pipeline.py --city "Sao Paulo, BR" --output briefing.md`) that is copy-paste ready, and the referenced script exists and is complete.	5 / 5
Workflow Clarity	The pipeline sequence is clear (geocode -> forecast -> show resolved location/observation time/sources) and the error case is handled ('stop with an error; do not invent conditions'), but the workflow is described narratively rather than as explicit numbered steps with a validation checkpoint.	4 / 5
Progressive Disclosure	A simple under-50-line single-purpose skill with well-organized sections (Run, Required behavior, Gotchas, References) and a referenced script bundle that exists; no need for deeper file references.	5 / 5
	Total	19 / 20 Passed

Description

91%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.

A strong description that clearly states the capability, provides natural trigger phrases, and explicitly scopes out adjacent use cases to avoid conflicts. It is concise without fluff and uses appropriate third-person voice.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Create a current, source-linked weather briefing', 'Resolve... through geocoding API', 'retrieve current conditions') and the specific APIs used, though it is a single-purpose skill so coverage is inherently narrow.	4 / 5
Completeness	Explicitly answers what ('Create a current, source-linked weather briefing... using the Open-Meteo geocoding and forecast APIs') and when ('Activate for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases ('what is the weather in Sao Paulo?', 'prepare a current weather briefing for Tokyo', 'get today's live conditions for New York') covering multiple synonymous phrasings users would actually say.	5 / 5
Distinctiveness Conflict Risk	Has a clear niche (live current weather for a named city) and an explicit exclusion list ('Do not use for travel booking, weather alerts, historical climatology, or safety-critical decisions') minimizing overlap with related skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: FrancyJGLisboa/agent-skills-platform
Path: .agents/skills/live-weather-briefing-skill/SKILL.md
Commit: 0c6900a

Reviewed: 4 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.