weather-query
Answer weather queries with a fixed demo response.
53
58%
Does it follow best practices?
Impact
—
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 the domain (weather) and a basic action (answering with a demo response), but it lacks explicit trigger guidance ('Use when...'), natural keyword variations, and multiple concrete actions. It would benefit from expanded trigger terms and a clear 'when to use' clause to help Claude select it appropriately.
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', and 'conditions'.
Clarify the scope and limitations more concretely, e.g., 'Returns a hardcoded demo weather response for testing purposes; does not fetch real-time 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 'weather queries' and 'fixed demo response' provides some specificity, but 'weather queries' alone could overlap with any weather-related skill; the 'demo' qualifier helps somewhat but is not 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 minimal demo skill that is concise and clear for its narrow purpose. Its main weakness is limited actionability — it only handles one hardcoded city/response with no guidance on edge cases (e.g., user asks about a different city). The brevity is appropriate given the trivial scope.
Suggestions
Add guidance on how to respond when the user asks about a city other than Shenzhen (e.g., 'For any other location, state that only Shenzhen demo data is available').
Consider providing an example exchange (user query → expected response) to make the expected output format fully concrete.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean — only 4 lines, every token serves a purpose. No unnecessary explanation of what weather is or how demos work. | 3 / 3 |
Actionability | The fixed demo data is concrete and the instruction to use it is clear, but the skill is extremely narrow — it only covers one city with one hardcoded response, and provides no guidance on how to handle queries about other locations or edge cases. | 2 / 3 |
Workflow Clarity | This is a simple single-task skill: when asked about weather, return the fixed demo data. The single action is unambiguous and no multi-step process or validation is needed. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is appropriately self-contained and well-organized in a few short lines. | 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
b22744d
- 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.