scienceworld-device-activator

Activates a device (e.g., blast furnace, stove) to initiate a process like heating. Use this skill when you have placed materials inside a device and need to start its operation. Takes a device name as input and outputs a confirmation of activation, enabling tasks that require energy input or material processing to progress.

Quality

90%

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

92%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, highly actionable single-purpose skill with excellent command-level guidance and validation checkpoints. The one real gap is progressive disclosure: an existing reference file with complementary device specs is not referenced from the body.

Suggestions

Add a short pointer in the body to references/device_specifications.md (e.g., a "## Device specifics" line: "For per-device operating temperatures, confirmation strings, and safety protocols, see [device_specifications.md](references/device_specifications.md)") so the bundle content is reachable.

Consider moving the device-specific confirmation strings currently inlined in the example into the reference file and linking, keeping the body as a concise overview.

Verify the example's quoted observations match the confirmation strings documented in device_specifications.md to avoid drift between the two.

Dimension	Reasoning	Score
Conciseness	Lean ~38-line body that assumes Claude's competence, explains no basic concepts, and makes every line actionable; the only mild redundancy is the Purpose line restating the description.	5 / 5
Actionability	Fully executable game commands ("activate <DEVICE_NAME>", "look at <DEVICE_NAME>", "use thermometer on <MATERIAL>") plus a complete worked blast-furnace example with expected observation strings, copy-paste ready and covering the common case.	5 / 5
Workflow Clarity	Six-step Core Workflow with explicit validation checkpoints (check "turned off" before, confirm "turned on" after, monitor with thermometer, deactivate when done) and an explicit "Always verify activation succeeded before proceeding" feedback rule.	5 / 5
Progressive Disclosure	The body is well organized into clear sections, but a provided bundle file (references/device_specifications.md) containing device-specific operating temperatures, exact confirmation strings, and safety protocols is never linked or signaled from the body, leaving that content orphaned.	3 / 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.

A well-crafted description that clearly states capability, input/output, and an explicit use-when trigger with concrete device examples. Only minor room for improvement in synonym coverage of trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete elements ("Activates a device", "initiate a process like heating", "Takes a device name as input", "outputs a confirmation of activation") with worked examples (blast furnace, stove), though the core action is essentially singular so comprehensive multi-action coverage is not reached.	4 / 5
Completeness	Explicitly answers both what ("Activates a device ... Takes a device name as input and outputs a confirmation of activation") and when ("Use this skill when you have placed materials inside a device and need to start its operation") with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Good natural keyword coverage ("activate", "blast furnace", "stove", "heating", "start its operation", "placed materials inside a device", "energy input"), but a few natural synonyms a user might say (e.g. "turn on", "light") are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche (post-loading device activation) with distinct device-name 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-device-activator/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.