alfworld-object-state-modifier

Uses an appliance to change the state of an object (cooling, heating, or cleaning). Use when the task requires altering an object's temperature or cleanliness using a specific device (e.g., cooling with a fridge, heating with a microwave, cleaning with a sinkbasin). Takes the object, target state, and appliance as inputs and executes the corresponding modifier action.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

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, actionable, and has a clear workflow with validation checkpoints and error recovery. Its main weakness is progressive disclosure: an existing reference file is orphaned (never linked from the body) and partially inconsistent with it.

Suggestions

Link references/appliance_interaction_guide.md from the body (e.g., a '## Appliance-specific protocols' line pointing to it) so the bundle is discoverable rather than orphaned.

Reconcile the fridge-opening contradiction: the body instructs 'open fridge 1' before cooling, but the reference states the fridge need not be open — pick one guidance and align both files.

Either inline the appliance-specific prerequisites from the reference into the body's Action Mapping, or move the body's error-recovery detail into the reference to avoid duplicating troubleshooting content across two locations.

Dimension	Reasoning	Score
Conciseness	The body is lean (~35 lines) with no padding or explanations of concepts Claude already knows; each section (workflow, mapping, recovery, example) earns its place and assumes competence.	3 / 3
Actionability	Provides concrete executable commands (`go to fridge 1`, `open {appliance}`, `cool tomato 1 with fridge 1`), a state-to-action mapping table, and a fully worked example with real observations — copy-paste ready.	3 / 3
Workflow Clarity	The numbered workflow includes explicit verify checkpoints ('verify it opens,' 'verify observation confirms the change') plus an error-recovery feedback loop for 'Nothing happened,' matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	A bundle file exists (references/appliance_interaction_guide.md) but is never linked or signaled from the body, and it contains appliance-specific protocols that duplicate/contradict the body (e.g., the body says to open the fridge before cooling while the reference says it is unnecessary), so references are present but not clearly integrated.	2 / 3
	Total	11 / 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 specific, complete, and well-triggered, naming concrete actions and devices with an explicit 'Use when' clause. It is clearly distinct from other skills and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Enumerates concrete actions (cooling, heating, cleaning) and explicit inputs (object, target state, appliance), matching the multiple-specific-actions anchor rather than the partial-coverage anchor below.	3 / 3
Completeness	Explicitly states what it does (change an object's state via an appliance) and when to use it ('Use when the task requires altering an object's temperature or cleanliness'), satisfying both halves with an explicit trigger clause.	3 / 3
Trigger Term Quality	Natural user-facing terms appear throughout ('cool,' 'heat,' 'clean,' 'fridge,' 'microwave,' 'sinkbasin') with device-specific examples, giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow (appliance-based object-state modification) with device-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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
Path: experiments/src/skills/alfworld/alfworld-object-state-modifier/SKILL.md
Commit: 7bb9a48

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.