scienceworld-tool-validator

Use when the agent has acquired a tool or instrument and needs to verify it is operational before first use in a critical task step. This skill performs a lightweight pre-use check via "focus on [TOOL] in inventory" and confirms readiness based on the system's response, ensuring the tool is functional before measurement, activation, or connection operations.

Quality

88%

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

88%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 body is a concise, actionable, single-purpose validation skill with a clear sequenced workflow and an explicit readiness checkpoint. Its main gap is that the bundled references/action_primer.md is not referenced from the body, leaving the progressive-disclosure structure slightly under-signalized.

Suggestions

Link references/action_primer.md from the body (e.g., a 'See action_primer.md for the full action list' note under Workflow or Key Principles) so the bundle reference is clearly signaled.

Tighten Key Principles to avoid restating the Workflow (drop the 'Timing' and 'Simplicity' points already implied by steps 1-3) to push conciseness to fully lean.

Expand the error path in step 3 ('unless an error is observed') with one concrete recovery action so the feedback loop is explicit rather than implied.

Dimension	Reasoning	Score
Conciseness	Lean and well-structured with no padding about what ScienceWorld is, but the Key Principles section partially restates Workflow content ('Validate immediately after acquisition', 'focus on is the primary validation method'), keeping it just short of fully lean.	4 / 5
Actionability	Provides fully executable, copy-paste-ready command transcripts ('pick up thermometer', 'focus on thermometer in inventory', 'use thermometer on unknown substance B') with two concrete worked examples covering the common cases.	5 / 5
Workflow Clarity	A clear 4-step sequence (Acquire, Execute validation, Confirm readiness, Proceed) with an explicit validation checkpoint ('A successful response confirms the tool is operational') and a stated error-feedback path; appropriate for this simple validation skill.	5 / 5
Progressive Disclosure	The body is self-contained and well-organized into clear sections, but the provided references/action_primer.md bundle file is never signaled or linked from the SKILL.md body, a minor organization gap against the actual bundle structure.	4 / 5
	Total	18 / 20 Passed

Description

87%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 strong: it explicitly states both the capability and a concrete 'Use when' trigger, names the specific validation action and operation contexts, and occupies a distinct niche. Minor room to broaden trigger-term synonyms and enumerate more concrete actions for full top marks.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete actions ('performs a lightweight pre-use check via "focus on [TOOL] in inventory"', 'confirms readiness based on the system's response') plus operation contexts (measurement, activation, connection), but centers on essentially one validation action rather than a comprehensive set.	4 / 5
Completeness	Explicitly answers both what ('performs a lightweight pre-use check via focus on [TOOL] in inventory and confirms readiness') and when ('Use when the agent has acquired a tool... before first use in a critical task step') with a concrete trigger clause.	5 / 5
Trigger Term Quality	Has a natural 'Use when the agent has acquired a tool or instrument and needs to verify it is operational before first use' trigger with relevant keywords, but the phrasing is procedural/niche rather than spanning the full range of colloquial synonyms a user might say.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — pre-use tool validation in ScienceWorld via the specific 'focus on' action — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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-tool-validator/SKILL.md
Commit: 076c6df

Reviewed: 6 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.