CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-circuit-connector

This skill connects two electrical components (e.g., wires, batteries, devices) by their terminals to build or modify a circuit. Use when constructing electrical setups for testing, such as conductivity checks or device activation. The input includes two component identifiers and their connection points, and the output is an established electrical connection.

64

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./experiments/src/skills/scienceworld/scienceworld-circuit-connector/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 clear, actionable single-purpose skill with a well-signaled reference file and a sensible procedure. Main weaknesses are minor redundancy with the description, basic-circuit over-explanation, and validation placed outside the numbered workflow.

Suggestions

Remove or condense the 'When to Use' section since the trigger guidance already lives in the frontmatter description, and trim the 'Circuit Logic' bullet that explains basic series-circuit concepts Claude already knows.

Fold the verification step into the Procedure as an explicit numbered step (e.g., '5. Verify: examine components or check indicators') so the validation checkpoint is part of the workflow rather than a separate principle.

Show a brief `examine OBJ` usage example for terminal discovery, or explicitly defer it to references/circuit_basics.md, to close the gap in formulating commands when terminals are unknown.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the "When to Use" section duplicates the frontmatter description and the "Circuit Logic" bullet explains basic series-circuit concepts Claude already knows, so it could be tightened.

3 / 5

Actionability

It gives the exact command syntax (`connect <ComponentA> <TerminalA> to <ComponentB> <TerminalB>`) plus a real trajectory example and expected success output, but terminal discovery relies on a mentioned-but-not-shown `examine` action and on the reference file.

4 / 5

Workflow Clarity

The four-step Procedure is clearly sequenced and Key Principles covers verification and error handling, but the validation checkpoint lives in a separate section rather than being an explicit numbered step in the workflow.

4 / 5

Progressive Disclosure

The body is a concise overview pointing one level deep to the real `references/circuit_basics.md` for diagrams and troubleshooting, with minor overlap between the body's Error Handling and the reference's Troubleshooting section.

4 / 5

Total

15

/

20

Passed

Description

82%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, well-structured description that clearly conveys both capability and trigger conditions with a concrete input/output contract. Slightly limited specificity because it centers on a single connect action rather than a broader action set.

DimensionReasoningScore

Specificity

It names the domain and one concrete action ("connects two electrical components ... by their terminals") plus the input/output contract, but does not enumerate multiple distinct actions, so it stops at 1-2 concrete actions rather than comprehensive coverage.

3 / 5

Completeness

It explicitly states what the skill does (connects components by terminals; input is two identifiers + connection points; output is an established connection) and when to use it ("Use when constructing electrical setups for testing, such as conductivity checks or device activation").

5 / 5

Trigger Term Quality

Natural trigger phrases like "constructing electrical setups for testing," "conductivity checks," and "device activation" match what a user would say, though synonym/extension coverage is not exhaustive.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and clearly scoped to terminal-to-terminal electrical connections with distinct triggers (conductivity checks, device activation), minimizing overlap with unrelated skills.

5 / 5

Total

17

/

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.