alfworld-locate-target-object

Navigates to a suspected location and identifies a target object. Use when your goal requires finding a specific object (e.g., "potato", "plate") and its location is not immediately known. Moves to a relevant receptacle (like a fridge or cabinet), checks its contents, and outputs the object's location or confirms its absence.

Quality

81%

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

63%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 body teaches a clear, well-sequenced locate-and-inspect procedure with a concrete worked example, but it is padded with redundant restatements of the same workflow across four sections. Its biggest structural flaw is that the one bundle file, references/action_primer.md, is orphaned — never linked from the body — so its edge-case guidance is effectively unreachable.

Suggestions

Merge the Core Workflow, Instructions, and Key Principles sections into a single Thought/Action template; the current three renditions of the same five steps cost tokens without adding information.

Add an explicit reference to the existing bundle file, e.g. under a 'Details' section: "For observation patterns (including `Nothing happened.`) and object/receptacle identifier notation, see [action_primer.md](references/action_primer.md)".

Operationalize the not-found branch: specify how to choose the next most likely receptacle and when to stop searching, rather than just stating "I must consider the next most likely location".

Dimension	Reasoning	Score
Conciseness	The Purpose section restates the description, the Instructions Thought/Action walkthrough re-derives the same five Core Workflow steps, and Key Principles repeats rules already embedded in the workflow ("Sequential Access", "Visual Confirmation") — mostly efficient but with several sections that could be cut or merged, matching the anchor 3 example rather than the 'minor instances' of anchor 4.	3 / 5
Actionability	Concrete action formats (`go to <suspected_receptacle>`, `open <suspected_receptacle>`) and a complete worked example with realistic observations give mostly executable guidance; minor gaps remain because edge cases like the `Nothing happened.` observation and identifier notation live only in references/action_primer.md, which the body never cites.	4 / 5
Workflow Clarity	A clear five-step sequence with an explicit found/not-found branch and a not-found retry path in Next Steps; no destructive or batch operation applies, so no validation cap. It falls short of anchor 5 because the recovery step "I must consider the next most likely location" is asserted but never operationalized into a checkable step.	4 / 5
Progressive Disclosure	The bundle contains references/action_primer.md with genuinely useful detail (observation patterns, identifier notation), but the body never references or links it — a reference that exists yet is entirely unsignaled. Against the actual bundle structure this matches anchor 3 ('references present but not clearly signaled'), not anchor 4 where references are at least visible.	3 / 5
	Total	14 / 20 Passed

Description

88%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 states concrete capabilities in third person and pairs them with an explicit, well-phrased 'Use when...' trigger clause including realistic examples. The only weaknesses are missing common synonyms ('locate', 'search') and the absence of an explicit domain name, which leave slight room on trigger coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain and a full chain of concrete actions — "Navigates to a suspected location", "Moves to a relevant receptacle (like a fridge or cabinet), checks its contents, and outputs the object's location or confirms its absence" — giving comprehensive coverage of the skill's behavior with no meaningful gap, matching the top anchor.	5 / 5
Completeness	It explicitly answers both questions: what ("Moves to a relevant receptacle... checks its contents, and outputs the object's location or confirms its absence") and when ("Use when your goal requires finding a specific object (e.g., "potato", "plate") and its location is not immediately known"), with concrete trigger phrases — the top anchor.	5 / 5
Trigger Term Quality	Natural phrases like "finding a specific object" and concrete terms "potato", "plate", "fridge", "cabinet" would be said by a user needing this skill, but common synonyms such as "locate" or "search for" are absent, placing it between the 'some relevant keywords' and 'comprehensive coverage' anchors.	4 / 5
Distinctiveness Conflict Risk	The household-receptacle examples carve out a distinct niche, but the description never names the ALFWorld/embodied-agent domain, leaving minor overlap risk with generic object-finding skills; this fits 'mostly distinct; minor overlap risk' rather than the fully-distinct anchor.	4 / 5
	Total	18 / 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-locate-target-object/SKILL.md
Commit: 358ec82

Reviewed: 8 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.