CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-object-locator

Searches for a specific target object across multiple rooms by systematically teleporting to likely locations and examining each room. Use this skill when you need to find an object whose exact location is unknown. Iterates through candidate rooms using teleport and look around, checks for the object, and continues until found, returning the object's location.

62

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./experiments/src/skills/scienceworld/scienceworld-object-locator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-organized, mostly lean instruction skill whose core defect is a broken bundle contract: it delegates room prioritization to a script that is absent and never surfaces the reference files that do exist. The search loop itself is clearly specified and the example is concrete, so the skill is usable if the prioritization gap is fixed.

Suggestions

Either add the referenced prioritize_rooms.py to the bundle (e.g., under scripts/) or remove the reference and inline an explicit default room priority list so 'Plan Search Order' is executable as written.

Link the existing reference files from the body (e.g., 'See [action_guide.md](references/action_guide.md) for action semantics and [example_trajectory_breakdown.md](references/example_trajectory_breakdown.md) for a worked trajectory') so they are discoverable rather than orphaned.

Trim the 'Notes & Best Practices' section of items that duplicate 'Core Process' and 'Key Actions' to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is efficient: it does not explain concepts Claude already knows, and the ScienceWorld-specific details (observation format, ambiguous object names) are genuinely additive. It is not a 5 because the 'Notes & Best Practices' section repeats guidance already given in 'Core Process' and 'Key Actions' (e.g., 'look around' after teleporting, using 'examine' for ambiguity).

4 / 5

Actionability

Concrete commands are given ('teleport to <ROOM_NAME>', 'look around', 'examine <OBJECT>') and the example is worked end-to-end, but key details are missing: step 2 says 'Use the provided prioritize_rooms.py script' yet no such script exists in the bundle, and the promised 'default priority list based on common object locations' is never provided. This incomplete-but-concrete state matches the score-3 anchor rather than the mostly-executable anchor at 4.

3 / 5

Workflow Clarity

The search loop is clearly sequenced with an explicit stop condition and a failure report ('If the object is not found after searching all candidate rooms, report this failure'), and identity-confirmation via 'examine' acts as a checkpoint. However, the 'Plan Search Order' step is unexecutable as written because it depends on a nonexistent script and an unstated default room list, leaving a material gap that the score-4 anchor's 'minor validation gaps' does not cover.

3 / 5

Progressive Disclosure

The body itself is short and well-sectioned, but judged against the actual bundle: the three files in references/ (action_guide.md, action_primer.md, example_trajectory_breakdown.md) are never referenced from the body, so relevant existing material is undiscoverable, while the one file the body does reference (prioritize_rooms.py) does not exist. This fits 'some structure but could be better organized; references present but not clearly signaled' rather than the good-structure anchor at 4.

3 / 5

Total

13

/

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: concrete, third-person, with an explicit 'Use this skill when...' trigger and a clearly defined output. Minor room for improvement in trigger synonyms and naming the target environment, but well above the midpoint on every dimension.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Searches for a specific target object across multiple rooms', 'systematically teleporting to likely locations and examining each room', 'checks for the object, and continues until found, returning the object's location' — comprehensively covering the skill's capabilities in third-person voice, matching the score-5 anchor. It is not a 4 because coverage is complete rather than having minor gaps.

5 / 5

Completeness

It explicitly answers both what ('Searches for a specific target object across multiple rooms... examining each room... returning the object's location') and when ('Use this skill when you need to find an object whose exact location is unknown') with a concrete trigger phrase, matching the score-5 anchor exactly. The 'when' clause is explicit and specific, so it is not a 4.

5 / 5

Trigger Term Quality

Natural phrases like 'find an object', 'exact location is unknown', 'teleport', and 'look around' are terms a user of this environment would actually say, giving good keyword coverage. It is not a 5 because common synonyms such as 'locate', 'where is', or 'search for' are missing; it is clearly above the 'some relevant keywords but missing common variations' anchor at 3.

4 / 5

Distinctiveness Conflict Risk

The 'teleporting to likely locations' and 'multiple rooms' language carves out a clear niche that is unlikely to trigger general document- or code-handling skills. It is not a 5 because the description never names the ScienceWorld environment, leaving minor overlap risk with other virtual-environment navigation skills; it is well above the broad-overlap anchors at 2-3.

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