CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-container-relocator

Moves an object from inventory to a specified container in a target room. Use when the task requires placing an item into a particular receptacle (e.g., 'move it to the orange box').

60

Quality

76%

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-container-relocator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 four-step procedure with concrete commands and an explicit verification step, appropriate for a simple skill. The main defect is navigation: the existing action_primer.md reference is orphaned, and there is no error-recovery path if the move or verification fails.

Suggestions

Link references/action_primer.md from the body where its content is needed — e.g., in step 1 ("If not, acquire it first — see [action_primer.md](references/action_primer.md) for `pick up`") and for object naming patterns before constructing the `move` command.

Add a brief failure path after step 4, such as: if the object is not inside the container, confirm the object name (see naming patterns) and re-run `move`, or use `look around` to locate the correct container.

Tighten the Example Flow so it demonstrates the full procedure including the `look at orange box` verification step, instead of repeating only steps 2-3.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation and every step phrased as an action. It is not a 5 because the "Example Flow (from trajectory)" section largely duplicates procedure steps 2-3 ("teleport to workshop", "move dove egg to orange box") instead of each token earning new value.

4 / 5

Actionability

Concrete executable commands with placeholders ("teleport to <ROOM>", "move <OBJECT> to <CONTAINER>", "look at <CONTAINER>") plus a fully instantiated example. Not a 5 because the example omits the verification step and no guidance is given for the case where the move command fails or the object is not accessible.

4 / 5

Workflow Clarity

A clear numbered sequence with an explicit validation step ("look at <CONTAINER> — verify the object is now inside") and a conditional fallback in step 1 ("If not, acquire it first"). Not a 5 because there is no feedback loop instructing what to do if verification fails or the transfer does not succeed.

4 / 5

Progressive Disclosure

The body's own sections are well-organized for a short skill, but the provided bundle file references/action_primer.md — which documents prerequisite actions ("pick up"), "focus on", "look around", room names, and object naming patterns needed for steps 1-2 — is never referenced or linked from SKILL.md, making it undiscoverable. Not a 4 because the bundle's reference is entirely unsignaled rather than a minor organization gap.

3 / 5

Total

15

/

20

Passed

Description

70%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 concise, third-person description that clearly answers both "what" and "when" with a concrete example trigger phrase. Its main limitations are single-action specificity and missing common trigger synonyms such as "put" or "drop".

DimensionReasoningScore

Specificity

"Moves an object from inventory to a specified container in a target room" names the domain and one concrete action, matching the 1-2-concrete-actions anchor. It is not a 4 because the description does not list several specific actions or cover the fuller capability space (e.g., acquiring the object, locating the container).

3 / 5

Completeness

Both parts are present: a clear third-person "what" and an explicit "Use when the task requires placing an item into a particular receptacle" with a concrete example phrase. Not a 5 because the "when" clause covers a single narrow trigger phrasing rather than multiple concrete trigger conditions, and not a 3 because the "when" is explicitly stated rather than implied.

4 / 5

Trigger Term Quality

Includes natural terms ("move", "placing an item into a particular receptacle") plus a verbatim user utterance ("move it to the orange box") that a user would plausibly say. Not a 5 because common synonyms like "put", "drop", or "store" are missing.

4 / 5

Distinctiveness Conflict Risk

The inventory-to-container transfer niche is mostly distinct with clear triggers. Not a 5 because the generic action framing ("Moves an object") could overlap with closely related object-manipulation skills in the same environment.

4 / 5

Total

15

/

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.