CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-inventory-manager

Handles picking up objects from the environment into the agent's inventory or moving them out to containers. Use this skill when you need to acquire an object for later use (pick up) or place an object into a specific container as part of a task requirement (move). Takes an object name and location as input and confirms the transfer to or from inventory.

70

Quality

85%

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.

The body is concise, actionable, and has a clear workflow with an explicit verify/retry checkpoint. Its one weakness is progressive disclosure: a real bundle file (environment_actions.md) with deeper action grammar exists but is never referenced or linked from SKILL.md, leaving useful detail undiscoverable.

Suggestions

Add a short '## Action reference' section linking references/environment_actions.md so the full action grammar and supporting actions are discoverable one level deep.

Trim the inlined action-grammar detail (e.g., state-suffix notes already covered by the reference) to avoid duplicating content that belongs in the bundle file.

DimensionReasoningScore

Conciseness

The body is lean across Purpose, a 4-step workflow, a compact action table, two short examples, and three notes, with no padding or explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Provides concrete executable commands ("pick up metal pot containing nothing in kitchen", "move metal pot to blue box", "look around") with expected result strings, matching the fully-executable-specific-examples anchor for this instruction-only skill.

3 / 3

Workflow Clarity

The numbered Core Workflow (Locate, Acquire, Place, Verify) includes an explicit validation checkpoint in step 4 (check observation feedback; on failure re-verify names with "look around"), matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

Sections are well-organized, but the body never signals or links the provided references/environment_actions.md bundle and instead inlines action grammar that the reference covers, fitting the references-present-but-not-clearly-signaled anchor.

2 / 3

Total

11

/

12

Passed

Description

77%

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 clearly states concrete capabilities and includes an explicit 'Use this skill when' trigger, covering both what and when. Its main weakness is generic trigger verbs (acquire, place) that limit distinctiveness and natural-term coverage, leaving it somewhat prone to overlap with similar object-handling skills.

Suggestions

Add environment-specific trigger terms (e.g., 'ScienceWorld inventory', 'pick up an object in a room', 'move an item to a colored box/container') to improve distinctiveness and natural keyword coverage.

Name the operating domain explicitly in the opening clause (e.g., 'Manages inventory in the ScienceWorld text environment') to reduce conflict with generic object-handling skills.

DimensionReasoningScore

Specificity

Lists concrete, named actions ("picking up objects... into the agent's inventory", "moving them out to containers", "acquire... (pick up)", "place... into a specific container") and names inputs (object name, location), matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers what ("Handles picking up... or moving them out to containers... confirms the transfer") and when ("Use this skill when you need to acquire an object for later use... or place an object into a specific container as part of a task requirement"), matching the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Includes relevant trigger verbs ("acquire an object for later use (pick up)", "place an object into a specific container") but the terms are fairly generic with limited natural variation, fitting the some-relevant-keywords-but-missing-common-variations anchor.

2 / 3

Distinctiveness Conflict Risk

Tied to a specific environment's object-manipulation grammar, but trigger language like "acquire an object" and "place an object into a container" is generic enough to overlap with other object-handling skills, fitting the somewhat-specific-but-could-overlap anchor.

2 / 3

Total

10

/

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.