alfworld-receptacle-operator

This skill opens or closes a receptacle (like a fridge, cabinet, or microwave) to access its interior or secure it. It should be triggered when an object needs to be placed inside/retrieved from a closed container, or when an open container should be closed (e.g., for energy efficiency or task cleanliness). The skill decides the appropriate 'open' or 'close' action based on the receptacle's current state and the task context.

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 decision workflow with an error-recovery step. Its main weakness is progressive disclosure: it defers detail to a reference that is vaguely signaled and essentially empty.

Suggestions

Replace "see the reference documentation" with an explicit link to the real file, e.g. "See [state diagrams & edge cases](references/state_diagrams.md)".

Populate references/state_diagrams.md with the actual state diagrams and edge cases it promises, or remove the reference and inline the needed detail if the file will stay empty.

The trajectory example partly restates the Core Decision Logic; consider trimming it to only the steps that add new information.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean and well-targeted to the alfworld receptacle actions, with no padding explaining concepts Claude already knows; every section earns its place.	3 / 3
Actionability	It gives the exact executable command format ("Action: open {recep}" / "Action: close {recep}") and concrete copy-paste-ready examples ("Action: open fridge 1", "Action: close fridge 1", "Action: open microwave 1").	3 / 3
Workflow Clarity	The Core Decision Logic is a clearly sequenced state-check → choose-action → execute flow, and the Important Notes add an explicit error-recovery checkpoint (re-check on "Nothing happened"), which fits a simple skill scoring 3.	3 / 3
Progressive Disclosure	The body is well-sectioned, but the deferred detail ("see the reference documentation") is not clearly signaled with a path/link, and the referenced bundle file references/state_diagrams.md is only an empty stub with no actual state-diagram or edge-case content — so the reference is weak rather than a clean one-level pointer.	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 distinctive: it states concrete open/close actions, gives explicit trigger conditions, and carves out a clear niche. It avoids vague fluff and verbosity.

Dimension	Reasoning	Score
Specificity	It names concrete actions — "opens or closes a receptacle", "access its interior or secure it", and the final "open or close action" — alongside concrete receptacle examples (fridge, cabinet, microwave), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It explicitly answers both what ("opens or closes a receptacle... to access its interior or secure it") and when via an explicit trigger clause ("It should be triggered when..."), so it is not capped at 2 for a missing 'Use when' clause.	3 / 3
Trigger Term Quality	Natural trigger phrasings a user would say are present — "placed inside/retrieved from a closed container", "an open container should be closed", plus receptacle names — giving good coverage rather than jargon or generic terms.	3 / 3
Distinctiveness Conflict Risk	The receptacle open/close niche has distinct triggers and a defined boundary (the skill later notes take/put/cool are separate), making overlap with other skills unlikely.	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-receptacle-operator/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.