alfworld-open-receptacle

This skill opens a closed receptacle to access its contents. It should be triggered when an agent needs to interact with items inside a closed container (e.g., fridge, microwave, drawer). The skill takes a receptacle identifier as input, performs the open action, and outputs the observation of the interior, enabling subsequent item retrieval or placement.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./experiments/src/skills/alfworld/alfworld-open-receptacle/SKILL.md

Quality

Content

71%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 content is concise, actionable, and clearly sequenced for a simple single-action skill, with concrete commands and failure signals. Its weaknesses are the un-signaled reference bundle file and an empty 'Example from Trajectory' section that leaves a worked example missing.

Suggestions

Link the existing bundle file from the body (e.g., 'See [common_receptacles.md](references/common_receptacles.md) for receptacle types and states') so the reference is clearly signaled.

Fill the empty 'Example from Trajectory' section with a short concrete observation/action/observation trace, or remove the header if no example is needed.

Add an explicit retry feedback loop after the failure case (e.g., on 'Nothing happened', re-check identifier spelling and closed state, then retry) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding over concepts Claude already knows (e.g., 'Use `go to {recep}`', 'Use `open {recep}`'), but the dangling empty 'Example from Trajectory' section and mildly explanatory Input Format sentence keep it just below the fully-lean anchor.	4 / 5
Actionability	Concrete commands ('go to {recep}', 'open {recep}'), a specific input format with examples ('fridge 1', 'microwave 1'), and a concrete failure signal ('Nothing happened') provide mostly executable guidance; the empty Example section leaves a minor gap versus copy-paste-ready completeness.	4 / 5
Workflow Clarity	A clear 4-step sequence (verify state, navigate, open, process result) with a pre-check in step 1 and failure interpretation in Expected Outcomes gives clear sequencing with most checkpoints present; it stops short of an explicit validate-then-retry feedback loop, so it does not reach the 5 anchor.	4 / 5
Progressive Disclosure	Sections are well-organized, but the bundle file references/common_receptacles.md exists and is clearly relevant (receptacle list, opening mechanics, error recovery) yet is never linked or signaled from the body, and the 'Example from Trajectory' section is empty, matching 'references present but not clearly signaled'.	3 / 5
	Total	15 / 20 Passed

Description

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

The description is well-constructed, clearly stating both what the skill does and when to trigger it with concrete receptacle examples. Its main limitation is specificity, since it really describes a single action (open) plus I/O rather than a breadth of concrete capabilities.

Suggestions

Add 1-2 more concrete capability verbs (e.g., 'verifies closed state, navigates, opens, and returns interior contents') to lift specificity toward comprehensive coverage.

Broaden trigger-term coverage with a few more natural receptacle synonyms (e.g., 'cabinet', 'oven', 'cupboard') to reduce missing-keyword risk.

Dimension	Reasoning	Score
Specificity	Quotes 'opens a closed receptacle to access its contents' and 'performs the open action, and outputs the observation of the interior' name the domain and 1-2 concrete actions (open, observe), but coverage is essentially a single action framed with I/O rather than multiple specific actions, so it sits at the anchor for 'names domain and 1-2 concrete actions' and below the 'several specific actions' anchor.	3 / 5
Completeness	It explicitly answers 'what' ('opens a closed receptacle... performs the open action, and outputs the observation of the interior') and 'when' ('It should be triggered when an agent needs to interact with items inside a closed container (e.g., fridge, microwave, drawer)'), matching the anchor for clearly and explicitly answering both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Phrases like 'fridge, microwave, drawer', 'closed container', and 'receptacle' are natural terms with good coverage and an explicit trigger clause; a few common synonyms/receptacle types are missing, placing it just below the comprehensive-coverage anchor.	4 / 5
Distinctiveness Conflict Risk	The niche of opening closed receptacles with concrete examples (fridge, microwave, drawer) is mostly distinct with only minor overlap risk against sibling receptacle-interaction skills, fitting just below the clear-niche/minimal-conflict anchor.	4 / 5
	Total	16 / 20 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-open-receptacle/SKILL.md
Commit: 076c6df

Reviewed: 6 days 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.