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.

63

Quality

73%

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

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with exact command syntax and a worked example, and it uses progressive disclosure well by offloading detail to a real reference file. The main gaps are minor conciseness redundancy and verification being framed as a principle rather than an explicit in-flow checkpoint.

Suggestions

Deduplicate the command syntax: state the `connect <ComponentA> <TerminalA> to <ComponentB> <TerminalB>` pattern once and reference it from the Procedure rather than restating it under Formulate Command.

Promote verification into an explicit numbered step with a retry loop (e.g., '5. Verify with `examine OBJ`; if the connection is absent, re-check terminal names and re-issue the command') so the checkpoint is part of the workflow.

Trim the When-to-Use section since it largely restates the frontmatter description; keep only the scenario bullets that add new information.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the command syntax is restated (Primary Action and Formulate Command) and the When-to-Use section overlaps the frontmatter description, so it could be tightened; it is not padded with concepts Claude already knows, keeping it above the bottom anchor.

2 / 3

Actionability

It provides the exact executable command syntax (`connect <ComponentA> <TerminalA> to <ComponentB> <TerminalB>`) with a concrete trajectory example and the expected confirmation observation, making the guidance copy-paste ready for the environment.

3 / 3

Workflow Clarity

A clear numbered procedure exists with verification and error-handling described, but verification lives in a separate Key Principles section rather than as an explicit checkpoint within the flow, leaving checkpoints implicit rather than integrated.

2 / 3

Progressive Disclosure

The SKILL.md is a concise overview that signals one clearly-named one-level-deep reference (`references/circuit_basics.md`, a real file) for deeper material, matching the well-organized overview-plus-reference top anchor.

3 / 3

Total

10

/

12

Passed

Description

75%

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 on completeness and distinctiveness, clearly stating both the capability and when to use it within a well-scoped niche. It is held back slightly by trigger phrasing that favors process language over plain user terms and by describing essentially one action rather than multiple concrete actions.

DimensionReasoningScore

Specificity

It concretely describes a single core action ("connects two electrical components ... by their terminals") plus an explicit input/output contract, but it does not list multiple distinct concrete actions, so it sits at the 'names domain and some actions' level rather than the multi-action top anchor.

2 / 3

Completeness

It clearly answers both what ("connects two electrical components ... to build or modify a circuit") and when (explicit "Use when constructing electrical setups for testing"), matching the top anchor that requires both an explicit capability statement and an explicit trigger clause.

3 / 3

Trigger Term Quality

The "Use when" clause offers relevant keywords ("conductivity checks", "device activation", "constructing electrical setups"), but the phrasing leans on process descriptions and omits plain natural user phrasing like "connect X to Y" or "build a circuit", so coverage is partial rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

The trigger is narrowly scoped to electrical circuit connection via component terminals, a clear niche unlikely to fire for unrelated skills, matching the distinct-trigger top anchor.

3 / 3

Total

10

/

12

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.