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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A tight, actionable, well-structured body for a simple skill, with an explicit success-validation step. The main defect is that the existing reference file containing troubleshooting and edge cases is never referenced by path, weakening navigation and the error-recovery guidance.

Suggestions

Link the troubleshooting guide explicitly, e.g. change "consult the troubleshooting guide" to "consult [references/execution_examples.md](references/execution_examples.md)", so the existing bundle file is discoverable.

Merge the "Pre-condition" note with Trigger Condition 3 (or vice versa) and trim the Purpose section's restatement of the description to remove redundancy.

Consider surfacing the edge cases that are already written (closed container, substance items, ambiguous names) as a brief pointer in the body, since they directly affect when this skill applies.

Dimension	Reasoning	Score
Conciseness	The body is lean (~30 lines) with no over-explanation of known concepts, but the Purpose section repeats the frontmatter description and the "Pre-condition" note ("This skill assumes the container is already open") duplicates Trigger Condition 3. Not a 5 because these redundancies could be trimmed; well above 3 because every section otherwise earns its place.	4 / 5
Actionability	Fully executable guidance: the exact command form `pick up <ITEM>`, the expected observation string ("You move the <ITEM> to the inventory."), a pre-check command (`look around`), and a complete worked example (avocado seed in a jar). Matches the copy-paste-ready top anchor; not a 4 because no gaps remain for this single-action skill.	5 / 5
Workflow Clarity	Clear sequence (Verify Context → Execute Transfer → Confirm Success) with an explicit validation checkpoint against the expected observation and an error-recovery path. Not a 5 because "consult the troubleshooting guide" names no file or path, leaving the recovery step underspecified; not a 3 because validation is explicit, not implicit.	4 / 5
Progressive Disclosure	The bundle contains references/execution_examples.md (troubleshooting and edge cases) and the body alludes to it ("consult the troubleshooting guide"), but never names or links the file — a reference that is present yet not clearly signaled, matching anchor 3. Not a 4 because the one existing reference is effectively buried; above 2 because the body itself is well-sectioned and appropriately sized.	3 / 5
	Total	16 / 20 Passed

Description

78%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 that clearly states both capability and trigger conditions with concrete examples. Its weaknesses are mild redundancy in the final sentence and slightly thin action coverage relative to the top specificity anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("retrieves a specified item from a container by using the 'pick up' action", "outputs confirmation"), but coverage is narrow and the third sentence ("The skill handles the object transfer") restates rather than adds. Not a 4 because it does not list several specific actions; not a 2 because the action named is concrete, not generic.	3 / 5
Completeness	Explicitly answers both: what ("retrieves a specified item from a container by using the 'pick up' action... outputs confirmation that the item is now in the agent's inventory") and when ("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 when-clause is explicit with concrete conditions, matching the top anchor; not a 4 because the trigger guidance is already specific.	5 / 5
Trigger Term Quality	Good natural-term coverage for the niche: "pick up", "container", "jar, box, or hive", "inventory", "item". Not a 5 because common variations like "take", "grab", or "get" are missing; clearly above 3 since multiple synonyms and concrete container examples are given.	4 / 5
Distinctiveness Conflict Risk	Clear niche (transferring items from open containers to inventory) with distinct triggers ("pick up", container, inventory). Minor overlap risk with a generic object-retrieval or container-opening skill keeps it below 5; well above 3 because the open-container, item-in-container trigger is quite specific.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: experiments/src/skills/scienceworld/scienceworld-container-item-retriever/SKILL.md
Commit: 358ec82

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.