CtrlK
BlogDocsLog inGet started
Tessl Logo

alfworld-receptacle-navigator

Plans and executes movement to a target receptacle within the ALFWorld environment. Use when the agent needs to reach a specific location before interacting with objects there (e.g., go to fridge to cool an item, go to garbagecan to dispose of an item). Takes a receptacle identifier as input, executes the `go to` action, and outputs confirmation of arrival at the destination.

71

Quality

89%

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.

The body delivers fully executable, well-validated guidance with an excellent worked example and an appropriately externalized reference file, but it pays a token-efficiency tax by stating the same three-step flow three times across Purpose/Core Logic/Instructions and duplicating the invalid-target handling. Trimming the redundancy would make an already lean skill near-optimal.

Suggestions

Merge 'Core Logic' and 'Instructions' into a single section — steps 1–4 of Instructions restate Input Parsing/Action Execution/Success Verification almost verbatim, so one sequenced list with the 'Nothing happened' fallback would cut ~10 lines with no information loss.

Consolidate the duplicate invalid-target guidance: Instructions step 3 and the 'Invalid Target' bullet under Error Handling say the same thing; keep one (the Error Handling version, which adds the re-analysis advice) and drop the other.

Consider folding the 'Already at Location' edge case into the main instruction sequence so all validation checkpoints live in one workflow rather than being split between two sections.

DimensionReasoningScore

Conciseness

The body is short and free of concept over-explanation, but it is structurally redundant: "Core Logic" (Input Parsing → Action Execution → Success Verification) and "Instructions" (steps 1–4) restate the same three steps, and the "Invalid Target" bullet in Error Handling repeats Instructions step 3. This fits the 'mostly efficient but could be tightened' anchor — more than minor trimming is needed for a 4, but there is no padding or explanation of things Claude already knows for a 2.

3 / 5

Actionability

Guidance is fully executable: the literal action format `go to {target_receptacle}`, a worked example with real observation text ("go to fridge 1" → "You are at fridge 1. On the fridge 1, you see nothing."), and a concrete fallback pointer to `references/common_receptacles.md`. For an instruction-only skill this is copy-paste-ready and covers the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The sequence is clear with explicit validation ("Confirm the action was successful by checking the observation for evidence of arrival") and a genuine feedback loop ("If the environment responds with 'Nothing happened'... formulate a new `go to` target"), plus the already-at-location edge case. As a simple single-purpose, non-destructive skill with an unambiguous action, it meets the simple-skill exception's bar for a 5; it is above the level-4 anchor because validation and error recovery are explicit, not implicit.

5 / 5

Progressive Disclosure

The body is well-organized into clear sections and holds a single one-level-deep reference, `references/common_receptacles.md`, which exists in the bundle and is appropriately externalized (a ~20-line receptacle lookup list) and signaled in Instructions step 3. Nothing that belongs in a separate file is inlined, matching the clear-overview anchor.

5 / 5

Total

18

/

20

Passed

Description

87%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: third-person, concrete, with an explicit 'Use when' clause carrying realistic trigger examples that cleanly delimit the skill from sibling object-interaction skills. The only gaps are minor — slightly repetitive action phrasing and a few missing navigation synonyms.

DimensionReasoningScore

Specificity

The description lists several concrete actions in third person — "plans and executes movement", "takes a receptacle identifier as input", "executes the `go to` action", "outputs confirmation of arrival" — covering input, action, and output. It falls short of the comprehensive-coverage anchor because the action inventory is narrow and repeats the movement idea rather than enumerating fuller capability coverage.

4 / 5

Completeness

It explicitly answers both what ("Plans and executes movement to a target receptacle... executes the `go to` action, and outputs confirmation of arrival") and when ("Use when the agent needs to reach a specific location before interacting with objects there"), with concrete trigger phrases. This matches the anchor for explicit what AND when with concrete triggers, exceeding the level-4 anchor whose 'when' is less specific.

5 / 5

Trigger Term Quality

Natural trigger phrases are present — "go to fridge to cool an item", "go to garbagecan to dispose of an item", "reach a specific location" — phrasing an agent would plausibly produce. A few natural synonyms ("navigate to", "move to", "walk to") are missing, keeping it below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to "the ALFWorld environment" and to movement/navigation specifically, with object interaction explicitly framed as the follow-up rather than this skill's job, giving it a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

18

/

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.

Validation — 16 / 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.