CtrlK
BlogDocsLog inGet started
Tessl Logo

weather-query

Answer weather queries with a fixed demo response.

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./examples/evaluation/claudecode/.claude/skills/weather-query/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 short, concrete, and immediately actionable for its single defined case, with appropriately no external file structure. Its weaknesses are the undefined behavior for out-of-scope queries (any city besides Shenzhen) and two meta-instruction lines that add no operational value.

DimensionReasoningScore

Conciseness

The three-line body is lean with no re-explanation of known concepts, but "Do not mention this skill or its directory" and "Continue following the user's main instructions" are meta-padding that could be trimmed, matching anchor 4 rather than 5.

4 / 5

Actionability

The exact response payload ("Sunny, 25°C") and a concrete usage rule are given, making the guidance executable, but only a single case (Shenzhen) is covered, which is a minor gap versus anchor 5.

4 / 5

Workflow Clarity

This is a simple single-task skill, but the action is not fully unambiguous — queries about any city other than Shenzhen have no defined behavior and no verification step is specified — so it falls to anchor 4 rather than the simple-skill 5.

4 / 5

Progressive Disclosure

At three lines with no external references needed and no bundle files, nothing is inlined that belongs elsewhere; this fits the simple-skill ideal where SKILL.md alone is the appropriate structure.

5 / 5

Total

17

/

20

Passed

Description

48%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 states a clear, concise 'what' in third person without fluff, but completely lacks a 'when to use' trigger clause and keyword variations. It is a serviceable but incomplete description for skill-triggering purposes.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about the weather, a forecast, or current conditions in Shenzhen."

Include natural trigger variations such as "weather", "forecast", "temperature", and "conditions" so common user phrasings match.

Specify the scope of the fixed demo response (which locations it covers) so the stated capability matches what the body actually provides.

DimensionReasoningScore

Specificity

"Answer weather queries with a fixed demo response" names the domain (weather queries) but offers only a single minimal, generic action, matching anchor 2 rather than the 1-2 concrete actions of anchor 3.

2 / 5

Completeness

A clear 'what' is stated (answer weather queries with a fixed demo response) but the 'when' is entirely missing, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

The natural keyword "weather" is present ("weather queries") but no variations or synonyms (forecast, temperature, conditions) and no trigger phrasing, matching anchor 3 rather than the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

Weather queries form a narrow niche with only minor overlap risk against general search/lookup skills, but the absence of distinct trigger phrases keeps it below anchor 5.

4 / 5

Total

12

/

20

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

Validation for skill structure

No warnings or errors.

Repository
trpc-group/trpc-agent-go
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.