alfworld-object-transporter

Picks up a target object from its current receptacle and moves it to a specified destination receptacle. Use when you have located an object and need to relocate it to complete a task (e.g., moving a laptop to a desk). Takes the object identifier, source receptacle, and destination receptacle as inputs and outputs the action sequence to take, transport, and place the object.

Quality

92%

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.

A tight, highly actionable body with a well-sequenced, validated workflow and a concrete worked example — conciseness, actionability, and workflow clarity all score top marks. Progressive disclosure drops to 2 because the body advertises a bundled script that is absent from the skill bundle.

Suggestions

Either create `scripts/transport_sequence.py` (the deterministic sequence generator the body advertises) or remove that bullet so the Bundled Resources section only references files that actually exist.

Consider moving the worked example into `references/troubleshooting.md` or a dedicated examples file to keep SKILL.md as a pure overview that links one level deep.

Dimension	Reasoning	Score
Conciseness	The body (~40 lines) is lean: a four-step workflow, an action-format list, a short error-recovery list, and one worked example, with no padding or explanation of concepts Claude already knows; every section earns its place, matching the 'lean and efficient' score-3 anchor.	3 / 3
Actionability	Concrete executable actions are given verbatim (`go to {receptacle}`, `take {object} from {receptacle}`, `put {object} in/on {receptacle}`) plus a complete worked example with real observations, making it copy-paste ready rather than pseudocode — the score-3 anchor.	3 / 3
Workflow Clarity	The Workflow section sequences navigate→take→navigate→place with explicit verify checkpoints after each action ("verify observation shows the target object", "verify 'You pick up'", "verify 'You put'") and a dedicated Error Recovery feedback section, satisfying the 'clear sequence with explicit validation steps and feedback loops' score-3 anchor.	3 / 3
Progressive Disclosure	Content is well-sectioned and references/troubleshooting.md is a real one-level-deep file, but the body's Bundled Resources claims `scripts/transport_sequence.py` which does not exist (no scripts/ directory), so the reference structure is only partially real and navigation is partly broken — the 'some structure but not clearly reliable' score-2 anchor rather than the clean score-3 case.	2 / 3
	Total	11 / 12 Passed

Description

92%

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, concise description: concrete actions, explicit inputs/outputs, and a clear 'Use when' trigger all in third person. The only soft spot is distinctiveness, where generic object/receptacle nouns without a domain marker leave some overlap risk with sibling skills.

Suggestions

Add a domain marker (e.g., "for AlfWorld text-game tasks") so it is unambiguously distinguishable from general object-manipulation skills.

Include a couple more natural trigger phrasings users might say (e.g., "put away", "deliver", "carry over") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes several concrete actions — "Picks up a target object from its current receptacle and moves it", "take, transport, and place the object" — and names the exact inputs (object identifier, source receptacle, destination receptacle) and output (action sequence), matching the 'lists multiple specific concrete actions' anchor rather than the partial score-2 example.	3 / 3
Completeness	It explicitly states both what ("Picks up... moves it to a specified destination receptacle") and when ("Use when you have located an object and need to relocate it to complete a task"), satisfying the score-3 anchor with an explicit 'Use when' clause rather than the implied-trigger score-2 case.	3 / 3
Trigger Term Quality	Natural user phrasing appears directly: "need to relocate it", "moving a laptop to a desk", "located an object" — good coverage of the terms a user would actually say, not jargon-only, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The AlfWorld receptacle-transport niche is fairly distinct, but the generic nouns "object" and "receptacle" with no domain tag could overlap with other object-manipulation or navigation skills; it lands at the 'somewhat specific but could still overlap' anchor rather than the clearly-conflict-free score-3 case.	2 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: zjunlp/SkillNet
Path: experiments/src/skills/alfworld/alfworld-object-transporter/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.