CtrlK
BlogDocsLog inGet started
Tessl Logo

alfworld-object-cooler

Cools a held object using an appropriate cooling appliance such as a fridge or freezer. Use when the task requires reducing the temperature of an object (e.g., "cool some pot", "chill the mug") and the agent is already holding the object. Performs the ALFWorld `cool` action and outputs the cooled object ready for subsequent placement or serving steps.

69

Quality

87%

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

85%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 an excellent lean, fully actionable instruction sheet with an unambiguous single-action workflow and a built-in failure feedback loop. Its one real structural defect is that the bundled references/action_semantics.md file is never mentioned, so its complementary details are unreachable through navigation.

Suggestions

Add a pointer to the bundled reference, e.g., under a 'Details' line: "For action semantics (receptacle state requirements, related actions), see [action_semantics.md](references/action_semantics.md)" — this would surface details like the fridge not needing to be open.

Deduplicate the Prerequisites section against Execution Flow step 1 'Verify State' by merging them into a single checklist.

Trim the 'Example from Trajectory' section to just the action and observation, since the state setup repeats the prerequisites.

DimensionReasoningScore

Conciseness

The ~25-line body is lean and assumes Claude's competence, with no explanation of known concepts, matching the 'efficient; minor instances of over-explanation that could be trimmed' anchor. It is not a 5 because the Prerequisites section ('Object in Hand', 'At Cooling Receptacle') is restated in Execution Flow step 1 'Verify State', and the Example from Trajectory largely repeats the execution flow.

4 / 5

Actionability

Guidance is fully executable: the exact command format `cool {obj} with {recep}`, a copy-paste example `cool pot 1 with fridge 1`, literal success/failure observation strings ("You cool the {obj} using the {recep}." / "Nothing happened"), and the next-step command `put {obj} in/on {recep}`. This matches the 'fully executable; copy-paste ready; specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

For this simple single-action skill the action is unambiguous, and the flow verify-state → execute → verify-outcome includes an explicit validation checkpoint with a feedback loop ("If the observation is 'Nothing happened'... check the prerequisites or try a different receptacle"). Per the simple-skill guideline this merits the top anchor; the operation is neither destructive nor batch.

5 / 5

Progressive Disclosure

The body itself is well-organized into clear sections, but the bundle contains references/action_semantics.md — which holds genuinely useful details (the receptacle need not be open, related actions such as `heat` and `take`) — and the body never references or links to it anywhere. Scoring against the actual bundle structure, this is an orphaned, undiscoverable reference, matching 'references present but not clearly signaled' rather than the 'references mostly clear' anchor above.

3 / 5

Total

17

/

20

Passed

Description

83%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.

A strong description that explicitly covers both what the skill does and when to use it, with concrete ALFWorld-specific actions and natural trigger phrases including synonyms. The main residual risks are minor overlap with sibling manipulation skills (heat/clean) and slightly incomplete synonym coverage.

Suggestions

Add one or two more natural trigger variations (e.g., "make it cold", "freeze") to broaden keyword coverage for the trigger_term_quality dimension.

Add a brief disambiguating clause (e.g., "not for heating or cleaning objects") to reduce overlap risk with sibling ALFWorld receptacle-action skills.

DimensionReasoningScore

Specificity

The description names several concrete actions — "Cools a held object using an appropriate cooling appliance", "Performs the ALFWorld `cool` action", "outputs the cooled object ready for subsequent placement or serving steps" — matching the 'several specific actions; minor gaps' anchor. It is not a 5 because the coverage is narrow and the cooling action is stated repetitively rather than comprehensively.

4 / 5

Completeness

It clearly answers both questions: what it does ("Performs the ALFWorld `cool` action" on a held object using a cooling appliance) and when to use it, via an explicit "Use when the task requires reducing the temperature of an object (e.g., 'cool some pot', 'chill the mug') and the agent is already holding the object" clause with concrete trigger phrases and a precondition. This matches the top anchor exactly.

5 / 5

Trigger Term Quality

It includes natural trigger phrases users would say — "cool some pot", "chill the mug", "fridge or freezer", "reducing the temperature" — giving good keyword coverage with synonyms (cool/chill). It falls short of 5 because common variations such as "make cold" or "freeze" are missing.

4 / 5

Distinctiveness Conflict Risk

The cooling-a-held-object niche is clear and the cool/chill triggers are distinct, but the skill shares the `{obj} with {recep}` action shape with closely related ALFWorld skills (heat, clean) and does not disambiguate against them. This fits 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict top anchor.

4 / 5

Total

17

/

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
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.