CtrlK
BlogDocsLog inGet started
Tessl Logo

alfworld-clean-object

Cleans a specified object using an appropriate cleaning receptacle (e.g., sinkbasin). Use when a task requires an object to be in a clean state (e.g., "clean potato", "wash apple") before proceeding. Navigates to the cleaning location, performs the clean action, and confirms the object is now clean.

69

Quality

84%

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.

Executable and clearly sequenced with explicit validation and error recovery, this is a high-quality instruction body. The main weakness is orphaned bundle files: the two reference files are never linked from SKILL.md and overlap with inlined content.

Suggestions

Link the bundle files from the body — e.g., under Error Recovery add 'See [troubleshooting.md](references/troubleshooting.md)' and reference trajectory_analysis.md where relevant — so the references are clearly signaled.

Move the bulk of Error Recovery detail into references/troubleshooting.md and keep only a one-line pointer in SKILL.md to reduce overlap with the inlined section.

Trim the Post-Condition section, which restates the 'Proceed' workflow step, to improve token efficiency.

DimensionReasoningScore

Conciseness

Mostly lean with concrete commands and a tight worked example, but the Post-Condition section and parts of Error Recovery slightly restate the Workflow steps and could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready commands (`go to sinkbasin 1`, `clean potato 1 with sinkbasin 1`) and a complete Thought/Action/Observation example covering the common case.

5 / 5

Workflow Clarity

A clearly sequenced three-step workflow with an explicit validation checkpoint ("verify observation confirms 'You clean the {object}'") and error-recovery feedback loops for "Nothing happened" and being away from the sinkbasin.

5 / 5

Progressive Disclosure

The body is sectioned well, but two bundle files exist (references/trajectory_analysis.md, references/troubleshooting.md) and are never linked from the body, while the inlined Error Recovery section overlaps the orphaned troubleshooting.md — references present but not signaled and content that should be separate is inline.

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 clearly conveys capability and trigger conditions with natural synonyms and concrete object examples. Minor gaps in precondition coverage and a few missing trigger variants keep specificity and trigger quality just below the top anchor.

DimensionReasoningScore

Specificity

Names several concrete actions — "Navigates to the cleaning location, performs the clean action, and confirms the object is now clean" — covering navigate/clean/verify, with minor gaps (e.g., the inventory-holding precondition is omitted).

4 / 5

Completeness

Explicitly states both what ("Cleans a specified object using an appropriate cleaning receptacle... Navigates... performs... confirms") and when ("Use when a task requires an object to be in a clean state... before proceeding") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases with synonyms ("clean potato", "wash apple") plus "clean state", giving good keyword coverage, though a few natural variants (rinse, scrub) are absent.

4 / 5

Distinctiveness Conflict Risk

The sinkbasin/cleaning-receptacle niche and "clean/wash" triggers are mostly distinct, with only minor overlap risk against related ALFWorld object-manipulation skills (heat, cool, slice).

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.

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.