CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-circuit-builder

This skill constructs a simple electrical circuit by connecting components like batteries, wires, and light bulbs. Use when the agent needs to test electrical conductivity or create a functional circuit for an experiment. The input is a set of available components, and the output is a fully connected circuit ready for activation.

71

Quality

89%

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

85%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 delivers highly actionable, well-sequenced instructions with exact commands, an explicit validation step, and error handling, at good token efficiency. The main weakness is the orphaned, empty references/circuit_schematic.md file that the body never points to, which leaves the bundle structure disconnected from the SKILL.md overview.

Suggestions

Either link references/circuit_schematic.md from the body (e.g., under Key Principles: 'See [circuit_schematic.md](references/circuit_schematic.md) for the schematic') or remove it — it is currently an empty stub that the body never references.

Trim the duplication between Section 3 (Core Procedure) and Section 6 (Example) — e.g., keep the parameterized templates and show only the final worked sequence, or fold the concrete example values into the templates.

Make the observation step unambiguous by specifying the exact iteration count or command form for 'wait1' rather than '1-2 iterations'.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence (no explanation of what circuits or conductivity are), but the 10-step Example section duplicates the parameterized Core Procedure almost line-for-line. Efficient with minor duplication that could be trimmed, matching anchor 4 rather than 5; well above anchor 3 since there is no unnecessary concept explanation.

4 / 5

Actionability

Provides exact executable commands with placeholders ('connect battery anode to <Wire1> terminal 1'), concrete substitute examples ('e.g., orange wire'), and a fully worked copy-paste-ready example covering the common case. Matches the anchor-5 example of fully executable, specific guidance.

5 / 5

Workflow Clarity

Clear sequenced workflow: prerequisites, numbered build steps, explicit validation checkpoint ('wait1', 'look around', check whether the light bulb is on), conditional final action based on the result, and error recovery guidance ('If a component is missing, examine the room'). Matches anchor 5's explicit validation and feedback-loop pattern; the operation is not destructive or batch, so no cap applies.

5 / 5

Progressive Disclosure

The body is well-organized with clear sections and is roughly the right size, but the bundle's only reference file (references/circuit_schematic.md) is never mentioned or linked anywhere in the body and itself contains only empty headings. References are present in the bundle but entirely un-signaled, matching anchor 3 rather than 4.

3 / 5

Total

17

/

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 strong description that clearly and explicitly states what the skill does, when to use it, and its input/output contract in third person with concrete component names. Keyword coverage is good but could add a few natural synonyms to reach the top trigger-term anchor.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('constructs a simple electrical circuit by connecting components like batteries, wires, and light bulbs', 'test electrical conductivity') with named components, but coverage has minor gaps (e.g., no mention of sorting or concluding actions). Fits anchor 4 better than 3 because more than 1-2 specific actions are named, and better than 5 because coverage is not comprehensive.

4 / 5

Completeness

It explicitly answers both 'what' ('constructs a simple electrical circuit by connecting components...') and 'when' ('Use when the agent needs to test electrical conductivity or create a functional circuit for an experiment') with concrete trigger phrases, plus input/output definitions. Clearly matches the anchor-5 example pattern.

5 / 5

Trigger Term Quality

'test electrical conductivity', 'functional circuit', and 'experiment' are natural user phrases, giving good keyword coverage. Score 5 requires synonyms and variations (e.g., 'electricity', 'conductive', 'build a circuit'), a few of which are missing, so it sits just below the top anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (circuit construction for conductivity testing) with distinct, domain-specific triggers; unlikely to fire for unrelated skills. Third-person voice ('This skill constructs...') is used correctly, so no specificity penalty applies.

5 / 5

Total

18

/

20

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.

Validation — 16 / 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.