CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-conductivity-tester

Determines if an object is electrically conductive by integrating it into a circuit and observing a light bulb. Triggered when classifying an object based on conductivity.

68

Quality

82%

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

90%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 lean, highly actionable, and clearly sequenced with an observation checkpoint, fitting a simple single-purpose skill. Its main gap is an unreferenced bundle diagram and the absence of an error-recovery loop.

Suggestions

Reference references/circuit_diagram.md from the Core Procedure so the bundled diagram is discoverable, e.g. "See circuit_diagram.md for the wiring layout".

Add a brief error-recovery note for when the bulb state is ambiguous (e.g. re-verify connections before classifying).

DimensionReasoningScore

Conciseness

Lean, well-sectioned (~30 lines) with no padding about what circuits/batteries are; every line is operational and assumes Claude's competence. Not a 4 because there are no noticeable instances of over-explanation to trim.

5 / 5

Actionability

Provides a fully concrete, executable action sequence with named terminals (e.g. "Connect the battery anode to orange wire terminal 1") and specific commands (focus, wait1, look around). Not a 4 because the guidance is copy-paste ready for the environment with no major gaps.

5 / 5

Workflow Clarity

Clear numbered sequence (steps 1-5 with substeps a-f) and an explicit observation checkpoint (wait then look around; bulb ON/OFF decides classification). Not a 5 because there is no error-recovery feedback loop, and not a 3 because the validation/observation checkpoint is present and decisive.

4 / 5

Progressive Disclosure

Well-organized sections (Objective, Core Procedure, Key Notes) for a short skill, but the bundled references/circuit_diagram.md exists yet is never linked or signaled from the body. Not a 5 because the reference is not navigable from the overview, and not a 3 because structure is otherwise good and content is appropriately concise.

4 / 5

Total

18

/

20

Passed

Description

75%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 clearly states both what the skill does and when to trigger it in third-person voice, with a distinct niche. It is slightly limited in action specificity and natural-term coverage, relying on one conceptual root rather than varied synonyms.

Suggestions

Broaden trigger terms with natural synonyms a user might say, e.g. "conductor", "insulator", or "does this object conduct electricity".

Make the capability slightly more concrete by naming the test setup (battery + bulb circuit) rather than "integrating it into a circuit".

DimensionReasoningScore

Specificity

Names the domain (conductivity) and two concrete actions ("integrating it into a circuit" and "observing a light bulb"), but the actions are somewhat abstract and coverage is limited to a single determination. Not a 4 because it does not list several specific actions, and not a 2 because the domain and actions are named rather than generic.

3 / 5

Completeness

Explicitly answers what ("Determines if an object is electrically conductive by integrating it into a circuit and observing a light bulb") and when ("Triggered when classifying an object based on conductivity") with a concrete trigger phrase. Clearly a 5, not a 4, because both what and when are stated explicitly and concretely.

5 / 5

Trigger Term Quality

Contains relevant terms ("electrically conductive", "conductivity", "classifying") but they are variations of one root concept, missing common natural synonyms like "conductor", "insulator", or "does it conduct". Not a 4 because natural-term coverage is thin, and not a 2 because the terms present are domain-relevant rather than generic.

3 / 5

Distinctiveness Conflict Risk

Targets a narrow niche (conductivity classification via circuit/bulb) with distinct triggers, making overlap with other skills minimal. Not a 4 because the niche is clearly delineated with low conflict risk.

5 / 5

Total

16

/

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.

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.