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.

77

Quality

96%

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 concise, actionable, single-purpose skill with a clear verify-execute-confirm workflow and an error-recovery path. The main weakness is a missing explicit link to the bundled troubleshooting reference, leaving navigation only implied.

Suggestions

In the Execution Workflow and Important Notes, replace the generic "consult the troubleshooting guide" with an explicit link to [references/execution_examples.md](references/execution_examples.md) so the one-level-deep reference is clearly signaled.

Add a short "## References" or "## Troubleshooting" section near the end pointing to references/execution_examples.md for edge cases (closed container, item not found, ambiguous names, substances).

Remove the duplicated open-container precondition between Trigger Condition #3 and the Important Notes Pre-condition, or cross-reference one from the other, to tighten the already-lean body further.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines) with tight sections (Purpose, Trigger Conditions, Core Action, Workflow, Notes, Example) and no padding or explanation of concepts Claude already knows; nearly every token earns its place despite a minor restatement of the open-container precondition.

3 / 3

Actionability

Gives the exact action format ("pick up <ITEM>" with <ITEM> as the observed object name), the precise expected observation string, and a worked example ("pick up avocado seed"), making it copy-paste ready for the environment.

3 / 3

Workflow Clarity

Sequences Verify Context -> Execute Transfer -> Confirm Success with an explicit validation checkpoint (expected observation) and an error-recovery fallback to troubleshooting; for this simple single-action skill the workflow is clear and well-organized.

3 / 3

Progressive Disclosure

The overview is clear and troubleshooting content is correctly split into references/execution_examples.md, but the body only says "consult the troubleshooting guide" without linking the actual file path, so the one-level-deep reference is present but not clearly signaled.

2 / 3

Total

11

/

12

Passed

Description

100%

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 well-crafted description that is concrete, third-person, and explicitly states both the capability and its trigger conditions with natural domain keywords. It is specific and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Names a concrete action ("using the 'pick up' action"), the object transfer to inventory, and the expected output confirmation rather than vague language. For a single-action skill this level of concreteness matches the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers what ("retrieves a specified item from a container by using the 'pick up' action") and when ("It should be triggered when the agent has identified a needed item inside an open container"), an explicit trigger clause equivalent to 'Use when...', so it is not capped at 2.

3 / 3

Trigger Term Quality

Includes natural domain terms users/agents encounter ("item", "container", "jar, box, or hive", "inventory", "pick up") with concrete container examples, giving good coverage of phrasing a caller would actually use.

3 / 3

Distinctiveness Conflict Risk

Targets a narrow, well-scoped niche (item inside an open, accessible container transferred to inventory) with distinct triggers, making conflict with unrelated skills unlikely.

3 / 3

Total

12

/

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.