CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-inventory-focus

Use when the agent needs to confirm and prepare a specific inventory item before using it in an experiment or task step. This "focus on [ITEM] in inventory" action verifies the correct item has been collected and signals intent, ensuring operational readiness for subsequent actions like measurement, combination, or placement.

72

Quality

88%

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, highly actionable, and presents a clear validated workflow. The only gap is that the provided reference file (action_context.md) is not linked or signaled from the body, leaving progressive disclosure incomplete.

Suggestions

Add a clearly signaled link to references/action_context.md (e.g., a short "See [action_context.md](references/action_context.md) for environment assumptions and common object names" line) so the existing bundle file is discoverable from the body.

Confirm the reference file's common object names (thermometer, unknown substance B, blue box) stay consistent with the examples to avoid drift.

DimensionReasoningScore

Conciseness

The ~58-line body is lean: it assumes Claude's competence, avoids explaining what an inventory or focus action is, and every section (Purpose, When to Use, Workflow, Examples, Notes) earns its place without padding.

3 / 3

Actionability

It provides exact executable commands (e.g., `pick up thermometer`, `focus on thermometer in inventory`, `use thermometer on unknown substance B`) plus the exact system confirmation string to watch for, and two complete copy-paste-ready transcript examples.

3 / 3

Workflow Clarity

The four-step workflow (Acquire -> Focus -> Confirm readiness -> Proceed) is clearly sequenced with an explicit validation checkpoint (waiting for "You focus on the [ITEM].") and error-recovery guidance in the notes; this is a low-risk single action so the present checkpoint satisfies the validation requirement.

3 / 3

Progressive Disclosure

The body is well-organized into clear standalone sections, but a bundle file (references/action_context.md) exists and is never referenced or signaled from the body, so it does not reach the well-signaled one-level-deep reference anchor.

2 / 3

Total

11

/

12

Passed

Description

85%

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-constructed description that covers what and when with an explicit "Use when..." trigger and concrete actions. The main weakness is trigger phrasing that leans procedural rather than mirroring natural user language.

Suggestions

Add natural-language trigger terms a user would actually say (e.g., "before measuring or combining an item", "when unsure which item was picked up") alongside the procedural phrasing.

Consider naming the ScienceWorld environment explicitly to sharpen distinctiveness against generic inventory skills.

DimensionReasoningScore

Specificity

The description names multiple concrete actions -- verifying the correct item has been collected, signaling intent, and "measurement, combination, or placement" -- matching the anchor that lists several specific concrete actions rather than a single vague domain statement.

3 / 3

Completeness

It explicitly answers both what (the focus-on action verifies the item and signals intent) and when, opening with an explicit "Use when the agent needs to confirm and prepare a specific inventory item before using it..." clause, satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

It includes relevant terms ("inventory item", "experiment", "task step", "focus on [ITEM] in inventory") but the phrasing is procedural/jargon rather than natural user language, and it omits common variations a user would actually say. It is above the no-relevant-keywords anchor (1) but lacks the broad natural-term coverage of a 3.

2 / 3

Distinctiveness Conflict Risk

The skill targets a narrow, distinctive action (focus on a specific inventory item before an experiment step) with triggers unlikely to fire for unrelated skills, fitting the clear-niche anchor.

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.