CtrlK
BlogDocsLog inGet started
Tessl Logo

alfworld-receptacle-preparer

This skill verifies and prepares a target receptacle for receiving an object. It is triggered before placing an item into a receptacle (e.g., a garbage can) to ensure the receptacle is accessible and suitable. The skill involves navigating to the receptacle, observing its state (e.g., open/closed, occupied), and performing any necessary preparatory actions like opening it, resulting in a ready-to-use target location.

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

92%

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, highly actionable, and has a well-sequenced workflow with validation and recovery steps. The only gap is that the existing action_primer.md reference is never linked from the body, weakening progressive disclosure.

Suggestions

Add an explicit pointer to the bundle, e.g. under Core Procedure or a References section: 'See references/action_primer.md for the full action list and placeholder conventions,' so the one-level-deep reference is clearly signaled.

Optionally move the per-action placeholder details (e.g. {obj}/{recep} replacement rules) to the reference rather than duplicating them inline.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it skips explaining what ALFWorld or receptacles are, and every section (Core Procedure, Key Principles, Example) earns its place without padding.

3 / 3

Actionability

It provides concrete, executable commands with exact placeholders (`go to {target_receptacle}`, `open {recep}`, `toggle {obj} {recep}`) plus a fully worked trajectory example, matching the 'fully executable; copy-paste ready' anchor.

3 / 3

Workflow Clarity

The Core Procedure is a clearly numbered sequence with an explicit 'Confirm' validation checkpoint and an error-recovery branch ('Nothing happened' → abort and re-plan), satisfying the anchor for a clear sequence with explicit validation and feedback loops.

3 / 3

Progressive Disclosure

A bundle reference file (references/action_primer.md) exists, but the body never signals or links to it — there is no 'See action_primer.md' pointer — so the reference is present yet not clearly signaled from the overview.

2 / 3

Total

11

/

12

Passed

Description

85%

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-differentiated, clearly stating both the capability and its trigger. Its main weakness is trigger term breadth, relying on somewhat formal phrasing rather than the fuller range of natural terms a user might use.

Suggestions

Broaden trigger terms to cover natural variations users might say, e.g. adding 'open, close, check, or prepare a container/receptacle before putting something in it' alongside the existing "put X in/on Y" phrasing.

Consider adding an explicit 'Use when...' clause to make the trigger guidance more conventional and machine-recognizable.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions: "navigating to the receptacle, observing its state (e.g., open/closed, occupied), and performing any necessary preparatory actions like opening it," matching the anchor for listing several specific actions.

3 / 3

Completeness

It explicitly answers both what ("verifies and prepares a target receptacle") and when ("It is triggered before placing an item into a receptacle"), and the explicit trigger guidance present here lifts it above the cap that applies only when such guidance is missing.

3 / 3

Trigger Term Quality

It includes relevant trigger phrasing like "put X in/on Y" and "placing an item into a receptacle," but the surrounding vocabulary ("receptacle," "receiving an object") is somewhat formal and misses several natural variations a user might say, fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche (preparing a receptacle before placing into it) with distinct triggers, and even distinguishes it from a separate search task, making overlap with other skills unlikely.

3 / 3

Total

11

/

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.