CtrlK
BlogDocsLog inGet started
Tessl Logo

alfworld-temperature-regulator

Manages the temperature state of an object by placing it into an appropriate appliance (fridge for cooling, microwave for heating). Use when the task requires modifying an object's temperature property, such as "cool some bread" or "heat some food". Takes the object identifier, temperature-modifying receptacle, and final target receptacle as inputs, and outputs the object at the target location with its temperature state changed.

72

Quality

88%

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

77%

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

A well-organized, concise procedural skill with clear sequencing and validation, but it contains a real correctness inconsistency in its core temperature step and a broken `scripts/` reference that weaken actionability and navigation.

Suggestions

Fix the temperature-application step in section 2 to use `cool {obj} with {temperature_receptacle}` / `heat {obj} with {temperature_receptacle}` (matching the example and action_spec.md) instead of `put {object} in/on {temperature_receptacle}`, which only relocates without changing temperature.

Remove or fulfill the `scripts/` reference — either provide the deterministic scripts it promises or drop the '(see `scripts/`)' pointer so the skill does not reference a missing bundle.

Link to the existing `references/action_spec.md` so the exact action grammar (especially the `cool`/`heat`/`toggle` actions) is discoverable from the body.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it does not explain what a fridge or ALFWorld is, and every section (inputs, execution, errors, example) earns its place; the only mild padding is the full observation strings in the example, which double as validation feedback.

3 / 3

Actionability

It gives concrete executable commands and a worked example, but section 2 instructs `put {object} in/on {temperature_receptacle}` to apply temperature while the example (and `references/action_spec.md`) correctly use `cool {obj} with {recep}` / `heat {obj} with {recep}` — so the core step is inconsistent — and it points to a `scripts/` directory that does not exist.

2 / 3

Workflow Clarity

The multi-step process is clearly sequenced (locate -> take -> apply temperature -> deliver) with explicit validation checkpoints ('Always verify the state change after each action') and an error-recovery feedback loop (re-scan if the object is not at the expected location, consult troubleshooting on 'Nothing happened').

3 / 3

Progressive Disclosure

The body is well-sectioned and correctly signals the real `references/troubleshooting.md`, but it also references a non-existent `scripts/` directory and never links to the available `references/action_spec.md`, so navigation is only partially reliable.

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.

A strong, third-person description that concretely states capabilities, inputs, and outputs while providing an explicit natural-language trigger. It cleanly answers both what the skill does and when to use it with minimal padding.

DimensionReasoningScore

Specificity

Names concrete actions with a specific appliance mapping — 'placing it into an appropriate appliance (fridge for cooling, microwave for heating)' — and specifies exact inputs (object identifier, temperature receptacle, target receptacle) and output state.

3 / 3

Completeness

Explicitly answers both what ('Manages the temperature state of an object by placing it into an appropriate appliance') and when ('Use when the task requires modifying an object's temperature property'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes natural user phrasing such as "cool some bread" or "heat some food" alongside the general 'modifying an object's temperature property' trigger, giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (temperature regulation via appliance placement) with distinct triggers, making it unlikely to fire for unrelated skills.

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.