CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-temperature-measurer

This skill uses a thermometer on a substance to measure its temperature. It should be triggered when the agent needs to determine the temperature of a material (e.g., lead) to assess if it has reached a specific melting point or threshold. The skill requires a thermometer in inventory and a target substance, outputting the measured temperature in degrees Celsius, which is key for scientific measurement tasks.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and highly actionable with concrete commands and exact observation strings, but workflow clarity lacks an inline validation checkpoint and progressive disclosure suffers from a dangling script reference and an unlinked reference file.

Suggestions

Inline a validation/feedback step in the Core Workflow (e.g., after measuring, verify the reading matches the expected state; if 'use thermometer' fails, run 'look at [container]' to confirm the substance's current name before retrying).

Resolve the bundled-script reference: either add scripts/measure_melting_point.py or remove the dangling 'Bundled Logic' mention and instead point to the existing references/action_guide.md with a clear link such as 'See [action_guide.md](references/action_guide.md)'.

Surface references/action_guide.md from the body (e.g., 'For the full action catalogue and troubleshooting, see references/action_guide.md') so the one-level-deep material is clearly signaled.

DimensionReasoningScore

Conciseness

Lean and efficient — no explanation of concepts Claude already knows, and each line (workflow steps, key actions, notes) earns its place. Not a 2 because there is no padded or unnecessary explanation.

3 / 3

Actionability

Provides fully concrete commands such as 'use thermometer in inventory on [substance]' and 'activate [heating device]', plus the exact observation phrasing 'the thermometer measures a temperature of X degrees celsius' and actionable troubleshooting. Not a 2 because guidance is specific and executable, not pseudocode.

3 / 3

Workflow Clarity

A clear 5-step sequence is present, but the measurement step lacks an explicit validation checkpoint and the only error-recovery hint ('If use thermometer fails, check ...') is buried in Notes rather than the workflow. Missing feedback loops cap it at 2; it is not a 1 because the sequence is concrete and ordered.

2 / 3

Progressive Disclosure

Sections are organized, but the body references a bundled script 'measure_melting_point.py' that has no corresponding scripts/ file and never links to the existing references/action_guide.md, so references are unsignaled/partly dangling. Not a 1 because there is real structure, but not a 3 because navigation is not cleanly signaled.

2 / 3

Total

10

/

12

Passed

Description

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.

The description is strong: concrete capabilities, natural trigger terms, explicit 'what' and 'when', and a distinctive niche that minimizes conflict risk. All four dimensions land at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'uses a thermometer on a substance to measure its temperature', 'requires a thermometer in inventory and a target substance, outputting the measured temperature in degrees Celsius' — rather than vague language. It is not a 2 because the actions are specific and comprehensive, not merely a named domain.

3 / 3

Completeness

Explicitly answers both 'what' ('uses a thermometer on a substance to measure its temperature ... outputting the measured temperature in degrees Celsius') and 'when' ('It should be triggered when the agent needs to determine the temperature of a material').

3 / 3

Trigger Term Quality

Includes natural terms a user would say — 'measure its temperature', 'temperature of a material (e.g., lead)', 'melting point or threshold', 'degrees Celsius'. Good coverage rather than only 'some relevant keywords'.

3 / 3

Distinctiveness Conflict Risk

A clear narrow niche — thermometric measurement of a substance against a melting-point threshold, requiring inventory thermometer — unlikely to overlap with unrelated skills. It is not a 2 because the triggers are specific and unambiguous.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zjunlp/SkillNet
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.