CtrlK
BlogDocsLog inGet started
Tessl Logo

alfworld-tool-locator

Searches for a specified tool or device (e.g., a desklamp, knife, or sponge) within the ALFWorld environment by checking relevant surfaces. Use when you need a tool to interact with another object as part of a task but the tool is not in your inventory or immediate vicinity. Takes a tool name as implicit input and navigates to likely storage spots (sidetables, shelves, countertops) until the tool is found.

67

Quality

80%

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

82%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.

A compact, actionable skill body with a clear sequenced workflow, executable ALFWorld commands, a worked example, and supporting reference files. The main gaps are an explicit inline pointer to the reference files and a validation checkpoint before tool use.

Suggestions

Add explicit inline links to the reference files (e.g., 'See [alfworld_actions.md](references/alfworld_actions.md) for the full action list') so progressive disclosure is clearly signaled.

Add a validation checkpoint before using a found tool (e.g., confirm the exact object name from the observation matches the target before issuing `take`/`use`) to strengthen the workflow's error recovery.

Tighten the Example slightly by trimming the redundant 'Result' line or folding it into the trace, improving token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, using compact workflow steps and an example without padding; only the Example trace and minor restating of action format keep it from the top anchor.

4 / 5

Actionability

Provides concrete, executable ALFWorld commands (`go to {receptacle}`, `take {tool} from {receptacle}`, `use {tool}`/`toggle {tool}`) plus a worked example trace that is copy-paste ready and covers the common case.

5 / 5

Workflow Clarity

The numbered workflow is clearly sequenced with prioritized locations and an explicit found/not-found/exhausted branch plus an Error Recovery section; it lacks a formal validation checkpoint before acting on a found tool, leaving a minor gap.

4 / 5

Progressive Disclosure

Well-organized sections (Workflow, Action Format, Error Recovery, Example) with two real one-level-deep reference files (alfworld_actions.md, tool_categories.md) supporting the body; references are not explicitly linked inline from SKILL.md, which is a minor signaling gap.

4 / 5

Total

17

/

20

Passed

Description

78%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 focused, well-scoped description that concretely states what it does and when to use it, with natural trigger terms and minimal conflict risk. It sits just below the top anchor only because action coverage and synonymous trigger phrasing could be marginally more complete.

DimensionReasoningScore

Specificity

Names the concrete actions 'checking relevant surfaces', 'navigates to likely storage spots', and lists example receptacles (sidetables, shelves, countertops), with minor coverage gaps (no explicit 'inspect/take' action stated).

4 / 5

Completeness

Clearly answers 'what' (searches surfaces for a tool) and 'when' via 'Use when you need a tool... but the tool is not in your inventory or immediate vicinity'; the 'when' is explicit and concrete but could be slightly tighter on the trigger phrasing.

4 / 5

Trigger Term Quality

Includes natural terms users would say (tool, device, desklamp, knife, sponge, inventory, vicinity) with good coverage, though it lacks common synonyms like 'find' or 'look for' phrasing beyond 'searches for'.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to ALFWorld tool/device location, naming the environment and specific tools, giving it a clear niche with minimal overlap risk against other skills.

5 / 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.