CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-container-item-retriever

This skill retrieves a specified item from a container by using the 'pick up' action. It should be triggered when the agent has identified a needed item inside an open container (e.g., a jar, box, or hive) and must transfer it to inventory for later use. The skill handles the object transfer, assuming the container is already accessible, and outputs confirmation that the item is now in the agent's inventory.

67

Quality

81%

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

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

The content is a tight, actionable single-purpose skill body with a clear workflow and validation checkpoint. Its main weakness is progressive disclosure: a real reference file exists but is not linked or signaled from the body.

Suggestions

Link the existing bundle file explicitly, e.g. change 'consult the troubleshooting guide' to 'See [execution_examples.md](references/execution_examples.md) for troubleshooting and edge cases'.

Add a brief retry/feedback loop in the Execution Workflow for when the expected observation does not appear (e.g., 'If the observation differs, verify the item name and container state, then retry').

Optionally surface the edge cases from execution_examples.md (closed container, substance items) as one-line inline notes so the body is self-sufficient for the common failures.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or explanation of concepts Claude already knows; every section (Purpose, Trigger Conditions, Core Action, Workflow, Notes, Example) earns its place.

5 / 5

Actionability

Gives the concrete executable unit ('pick up <ITEM>'), the exact expected observation string, and a worked example; just short of a 5 because it is an environment command rather than copy-paste code and offers no handling for the noted ambiguity case.

4 / 5

Workflow Clarity

A clear three-step workflow (Verify Context -> Execute Transfer -> Confirm Success) with an explicit success observation checkpoint; minor gap is that troubleshooting is referenced but not integrated as a retry loop in the main flow.

4 / 5

Progressive Disclosure

Sections are well-organized, but the existing bundle file references/execution_examples.md is never linked from the body — 'consult the troubleshooting guide' is an un-signaled, path-less pointer — leaving references present but not clearly signaled.

3 / 5

Total

16

/

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.

The description is clear, third-person, and answers both what and when with concrete trigger phrases and example containers. It is well above average with only minor redundancy and a few missing synonyms.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('retrieves a specified item', 'pick up' action, 'transfer it to inventory') rather than vague language, though there is minor phrasing redundancy keeping it just below a 5.

4 / 5

Completeness

Explicitly states both what it does ('retrieves a specified item... using the pick up action') and when to trigger ('It should be triggered when the agent has identified a needed item inside an open container'), matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural trigger context ('identified a needed item inside an open container', 'e.g., a jar, box, or hive') that a user/agent would naturally voice, with only a few synonyms missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (item retrieval from an already-open container) with distinct triggers, carrying only minor overlap risk with closely related pick-up or open-container skills.

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.

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.