CtrlK
BlogDocsLog inGet started
Tessl Logo

weather

Get current weather and forecasts (no API key required).

84

1.19x
Quality

78%

Does it follow best practices?

Impact

100%

1.19x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./apps/picooraclaw/cmd/picooraclaw/internal/onboard/workspace/skills/weather/SKILL.md
SKILL.md
Quality
Evals
Security

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 an exemplary lean, fully executable reference for a simple skill: copy-paste commands with outputs, dense format-code and tips sections, and a clearly labeled fallback service. The only notable gap is that the Open-Meteo fallback never shows how to actually find a city's coordinates.

Suggestions

Add a concrete one-liner for city-to-coordinate lookup, e.g. curl against Open-Meteo's geocoding API (https://geocoding-api.open-meteo.com/v1/search?name=London), to close the actionability gap in the fallback path.

DimensionReasoningScore

Conciseness

The body is lean and efficient: "Two free services, no API keys needed" followed by copy-paste commands, a one-line format-code reference ("%c condition · %t temp · %h humidity"), and a compact tips list — no padding and no explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.

5 / 5

Actionability

The wttr.in commands are fully executable with sample outputs ("curl -s \"wttr.in/London?format=3\" / # Output: London: ⛅️ +8°C"), but the fallback section's "Find coordinates for a city, then query" gives no concrete geocoding command, leaving a minor gap between anchor 4 and 5.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill (under 50 lines) whose primary action — one curl command — is unambiguous, with the Open-Meteo fallback clearly labeled and sequenced ("primary" vs "fallback, JSON"); no destructive or batch operations require validation checkpoints, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external reference files, and the content is organized into clearly labeled sections (wttr.in, Open-Meteo) with the one external pointer ("Docs: https://open-meteo.com/en/docs") clearly signaled, satisfying the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

65%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 is concise, concrete, and in third person with a genuinely useful differentiator ("no API key required"), but it lacks any explicit "when to use" guidance, which both caps completeness and weakens it as a trigger surface. Its keyword coverage is good for the domain though a few common synonyms are absent.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about the weather, a forecast, temperature, or conditions for a location."

Include common synonym terms such as "temperature", "weather report", or "conditions" to broaden natural trigger matching.

Optionally surface one more concrete capability (e.g. "as JSON for programmatic use") to lift specificity from 1-2 actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Get current weather and forecasts" names the domain and two concrete actions but stops there — it doesn't mention formats, locations, or the JSON fallback that the body actually supports, matching the 'names domain and 1-2 concrete actions' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

The "what" is clear (get current weather and forecasts), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"weather" and "forecasts" are the primary natural phrases a user would say, giving good keyword coverage; minor natural terms like "temperature", "weather report", or "conditions" are missing, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Get current weather and forecasts" occupies a clear niche with distinct trigger terms (weather, forecasts) and minimal realistic overlap with other skills.

5 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

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

13

/

16

Passed

Repository
oracle-devrel/oracle-ai-developer-hub
Reviewed

Table of Contents

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.