CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-room-explorer

Performs an initial survey of a room to identify all visible objects, containers, devices, and their states using the 'look around' action. Use this skill when you first enter a new location, need to refresh your understanding of the environment, or must identify available resources before planning a sequence of actions. Returns a detailed observation that serves as foundational context for subsequent tasks.

69

Quality

87%

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.

A tight, actionable single-purpose skill: the core action is unambiguous, the example is concrete, and the parse checklist makes the output immediately usable. Its main weakness is navigation — the bundled references/action_primer.md is orphaned, never referenced from the body, leaving related action guidance undiscoverable from the overview.

Suggestions

In 'Integration with Other Skills', add a one-line link to the bundled reference, e.g. 'See [action_primer.md](references/action_primer.md) for the full list of follow-up actions (pick up, connect, activate, teleport) and a standard task sequencing pattern.'

Merge the 'Purpose' section into the description or the top of the instructions to remove the restated rationale and save tokens.

Optionally note in 'Output Processing' or the Example that exits and pre-existing connections are part of the returned observation, so downstream skills can rely on it.

DimensionReasoningScore

Conciseness

The body is lean and assumes agent competence — no explanation of what an environment or observation is — with every section carrying operational content. Minor trimming is possible: the "Purpose" section ("Use this skill to establish a foundational understanding... It is the critical first step...") restates the frontmatter description, and "This is the only action required for this skill" could be folded into the Core Action line, which keeps it at anchor 4 rather than 5.

4 / 5

Actionability

The guidance is fully executable for an instruction-only skill: an exact command ("Execute the `look around` action"), a concrete parse checklist (Room Name, Objects, Object States, Connections, Exits), and a worked example with real action commands (`teleport to kitchen`, `look around`) plus its parsed inventory. This matches anchor 5's copy-paste-ready commands covering the common case.

5 / 5

Workflow Clarity

This is a simple single-action skill and the action is unambiguous ("Execute the `look around` action. This is the only action required"), with a clear post-action output-processing sequence and explicit integration guidance plus a boundary note directing detailed object inspection to `examine OBJ`/`look at OBJ`. Per the simple-skill exception the single action is unambiguous, and no destructive or batch operations exist that would require validation checkpoints, so it merits 5.

5 / 5

Progressive Disclosure

The body is well organized into short sections, but the bundle contains references/action_primer.md (a listing of related actions and a sequencing pattern) that the SKILL.md body never mentions or links — the "Integration with Other Skills" section even discusses follow-up actions like `pick up` and `connect` without pointing to the primer where they are documented. Per the guideline to score against the actual bundle structure, this is a reference present but not clearly signaled (anchor 3); it is not anchor 4, where references are 'mostly clear'.

3 / 5

Total

17

/

20

Passed

Description

83%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: it states a concrete capability, an explicit multi-condition 'Use when' clause, and a clear output, all in third person without padding. Trigger coverage is good though not exhaustive of natural synonyms, and the distinctiveness from object-examination skills is implied rather than explicit.

DimensionReasoningScore

Specificity

The description names a concrete action ("survey of a room to identify all visible objects, containers, devices, and their states using the 'look around' action") plus a concrete output ("Returns a detailed observation"), giving specific capability coverage with only minor gaps (e.g., no mention of exits/connections it also surfaces in the body). It exceeds anchor 3 (only 1-2 actions, not comprehensive) because the identified targets and output are enumerated, but falls short of anchor 5's fully comprehensive multi-action list.

4 / 5

Completeness

It explicitly answers both: what ("Performs an initial survey of a room to identify all visible objects... Returns a detailed observation") and when ("Use this skill when you first enter a new location, need to refresh your understanding... or must identify available resources"), with concrete trigger phrases. This matches the anchor-5 example structure of capability statement plus explicit multi-condition 'Use when' clause.

5 / 5

Trigger Term Quality

Natural trigger phrases are present — "when you first enter a new location", "need to refresh your understanding of the environment", "identify available resources" — alongside the concrete keyword "look around". Good coverage, but a few natural variations (e.g., "survey", "explore the room", "check what's in the room") are missing, so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is fairly clear — room-level survey via the specific 'look around' action in a game-environment context — with distinct triggers like entering a new location. Minor overlap risk remains with object-examination skills (the description does not itself carve out the examine/look-at boundary the way the body does), keeping it below anchor 5.

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

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.