weather-query
Answer weather queries with a fixed demo response.
67
58%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/claudecode/.claude/skills/weather-query/SKILL.mdQuality
Discovery
32%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 brief and identifies its domain (weather queries) and a key characteristic (fixed demo response), but it lacks explicit trigger guidance ('Use when...'), natural keyword variations, and detailed capability listing. It would benefit from more specificity about when to invoke it and what distinguishes it from a real weather skill.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about weather, forecasts, temperature, or current conditions.'
Include natural trigger term variations such as 'forecast', 'temperature', 'weather report', 'current weather', or 'climate'.
Clarify the scope and limitations, e.g., 'Returns a hardcoded demo weather response for testing purposes; does not fetch real data.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain ('weather queries') and a single action ('answer... with a fixed demo response'), but does not list multiple concrete actions or elaborate on capabilities. | 2 / 3 |
Completeness | It describes what the skill does but lacks any explicit 'Use when...' clause or trigger guidance, and per the rubric a missing 'Use when' clause caps completeness at 2. Additionally, the 'what' is minimal, so this falls to a 1. | 1 / 3 |
Trigger Term Quality | Includes 'weather queries' which is a natural keyword, but misses common variations like 'forecast', 'temperature', 'weather report', 'current weather', etc. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'fixed demo response' adds some distinctiveness, but 'weather queries' is broad enough that it could overlap with any real weather skill. The demo nature helps somewhat but isn't strongly distinctive. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an extremely simple, single-purpose skill that is concise and clear in its intent. Its main weakness is limited actionability — it only covers one hardcoded scenario (Shenzhen weather) with no guidance on how to handle other weather queries or edge cases. For what it aims to do, it is well-structured and token-efficient.
Suggestions
Clarify how to handle weather queries for cities other than Shenzhen (e.g., decline, say data unavailable, or also use demo data).
Add a brief example of expected input/output to make the skill more actionable (e.g., 'User: What's the weather in Shenzhen? → Response: The weather in Shenzhen is sunny, 25°C.').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean — only 3 short sentences plus the demo data. Every token serves a purpose with no unnecessary explanation. | 3 / 3 |
Actionability | The instruction is concrete (use fixed demo data for weather queries) but very narrow — it only covers one city with hardcoded data and provides no guidance on edge cases like other cities or follow-up questions. | 2 / 3 |
Workflow Clarity | This is a simple single-task skill with an unambiguous action: respond with fixed demo data when asked about weather. No multi-step process or destructive operations are involved, so the clarity is sufficient. | 3 / 3 |
Progressive Disclosure | The skill is under 50 lines and requires no external references. The content is well-organized with the data presented first and behavioral instructions following. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.