weather
Get current weather and forecasts via wttr.in or Open-Meteo. Use when: user asks about weather, temperature, or forecasts for any location. NOT for: historical weather data, severe weather alerts, or detailed meteorological analysis. No API key needed.
88
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the key criteria. It specifies concrete actions, includes natural trigger terms, has explicit 'Use when' and 'NOT for' clauses, and carves out a distinct niche. The inclusion of negative boundaries is a particularly strong feature that helps Claude avoid misapplying this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Get current weather and forecasts', names specific tools/APIs ('wttr.in or Open-Meteo'), and explicitly states 'No API key needed' which is a useful implementation detail. | 3 / 3 |
Completeness | Clearly answers both 'what' (get current weather and forecasts via wttr.in or Open-Meteo) and 'when' (explicit 'Use when' clause with triggers). Also includes a 'NOT for' clause that further clarifies boundaries, which is excellent for disambiguation. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'weather', 'temperature', 'forecasts', 'location'. These are exactly the terms a user would use when asking about weather conditions. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused on weather data retrieval with specific API sources. The 'NOT for' exclusions (historical data, severe alerts, meteorological analysis) further reduce conflict risk with any adjacent skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid, actionable weather skill with excellent executable examples covering current conditions, forecasts, and format options. The main weaknesses are mild verbosity in the trigger/exclusion sections and the missing Open-Meteo fallback mentioned in the skill description. Overall it's a well-structured reference that Claude can immediately use.
Suggestions
Trim the 'When to Use' section to a brief sentence rather than listing example user phrases—Claude can infer these from the skill description.
Add Open-Meteo as a fallback option (mentioned in the skill description but absent from the content), or remove it from the description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'When to Use' and 'When NOT to Use' sections are somewhat verbose and repeat information from the frontmatter description. The format codes reference and quick responses sections are useful but the overall content could be tightened—e.g., Claude doesn't need example user phrases like 'What's the weather?' as trigger examples. | 2 / 3 |
Actionability | Every section provides concrete, copy-paste-ready curl commands with clear parameter explanations. Format codes, unit options, and multiple query patterns are all directly executable. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (fetch weather via curl). The commands are unambiguous and self-contained—no multi-step destructive operations requiring validation checkpoints. The single-action nature makes the workflow perfectly clear. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's all inline in one file. The format codes table and quick responses could potentially be separated, though for a skill of this size (~80 lines of content) it's borderline acceptable. The description mentions Open-Meteo as an alternative but no reference or fallback instructions are provided. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 8 / 11 Passed | |
- Repository
- trpc-group/trpc-agent-go
- Commit
af8bd5f
- 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.