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').

74

Quality

91%

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

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, actionable body with concrete commands, a worked example, and an explicit verification step. The one gap is progressive disclosure: the existing references/action_primer.md bundle file is not referenced from the body even though it documents prerequisite actions the procedure relies on.

Suggestions

Link references/action_primer.md from the body — e.g., in step 1 add 'If not, acquire it first (see [action_primer.md](references/action_primer.md) for pick up / focus on)' — so the prerequisite actions are surfaced rather than left implicit.

Add a one-line pointer to action_primer.md under the Procedure section (e.g., 'See references/action_primer.md for the full action vocabulary and object-naming patterns') to make the bundle discoverable.

Optionally state the failure branch for step 4 (what to do if the object is not inside after 'look at <CONTAINER>') to round out the verification feedback loop.

DimensionReasoningScore

Conciseness

The body is lean — a 4-step procedure and a short worked example with no padding and no explanation of concepts Claude already knows (unlike the verbose 1-anchor 'PDF (Portable Document Format) files are a common file format...'); every line earns its place.

3 / 3

Actionability

It gives concrete executable commands with placeholders — 'teleport to <ROOM>', 'move <OBJECT> to <CONTAINER>', 'look at <CONTAINER>' — plus a fully filled worked example ('teleport to workshop', 'move dove egg to orange box'), matching the copy-paste-ready 3-anchor rather than the pseudocode 2-anchor.

3 / 3

Workflow Clarity

The 4-step procedure is clearly sequenced and includes an explicit verification checkpoint — step 4 'look at <CONTAINER> — verify the object is now inside'; this is a simple, non-destructive single-object move so the missing-failure-branch cap does not apply, fitting the 3-anchor's clear-sequence-with-explicit-validation criterion.

3 / 3

Progressive Disclosure

The body is well organized into 'Procedure' and 'Example Flow' sections, but a provided bundle file references/action_primer.md (which documents the prerequisite 'pick up'/'focus on'/'look around' actions that step 1's 'acquire it first' implicitly depends on) is never linked or signaled from the body, matching the 2-anchor 'references present but not clearly signaled'.

2 / 3

Total

11

/

12

Passed

Description

90%

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, concise description that pairs a concrete capability statement with an explicit 'Use when' trigger and a natural example utterance. The only minor gap is that it describes a single composite action rather than enumerating multiple discrete capabilities.

DimensionReasoningScore

Specificity

The description names a concrete action — 'Moves an object from inventory to a specified container in a target room' — but it is a single composite action rather than the 'multiple specific concrete actions' required for a 3 (cf. the 3-anchor 'Extract text and tables, fill forms, merge documents').

2 / 3

Completeness

It explicitly answers both 'what' ('Moves an object from inventory to a specified container in a target room') and 'when' via an explicit 'Use when...' clause with a trigger example, matching the 3-anchor that requires both an explicit what and an explicit trigger.

3 / 3

Trigger Term Quality

The trigger 'Use when the task requires placing an item into a particular receptacle (e.g., "move it to the orange box")' embeds a literal user utterance — exactly what a user would naturally say — satisfying the 'would a user naturally say this' guideline; it is not the jargon-only or generic case that anchors a 1 or 2.

3 / 3

Distinctiveness Conflict Risk

The niche is clear and narrow — relocating an item into a specific container/receptacle in a target room, anchored by the distinct utterance 'move it to the orange box' — making it unlikely to fire for unrelated skills; it is not the generic 'Helps with code and documents' case that anchors a 1.

3 / 3

Total

11

/

12

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.