CtrlK
BlogDocsLog inGet started
Tessl Logo

replicator-pcb

Use before Project Replicator PCB source, layout, routing, DRC, fabrication, or PCB visual-review work.

67

Quality

81%

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

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.

This is a high-quality, densely informative skill body: executable examples, explicit validation-laden workflows for destructive fabrication operations, and clean one-level-deep reference structure. The only minor weakness is occasional repetition across the electromechanical-footprint guidance that could be condensed.

DimensionReasoningScore

Conciseness

Nearly every line is non-obvious domain policy (source ownership, chirality hard rules, JLC SMT gates) that assumes Claude's competence with almost no concept padding, though a few sections repeat the 'do not hand-draw' guidance and could be tightened.

4 / 5

Actionability

Provides copy-paste-ready TSX/JSON examples and names exact commands, config fields, and failure diagnostics (e.g. pcb.run(profile="check"), <HotSwapKeySwitch switch="mx" socket="c41430893"/>, freerouting_reroute_target_unknown) covering the common cases.

5 / 5

Workflow Clarity

Preview Loop, Connectivity Diagnosis, and Copper Pour Islands are explicit numbered sequences with validation checkpoints and feedback loops (rerun check, confirm no new island), exactly the pattern rewarded for destructive/batch PCB operations.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview that offloads full config shape and footprint details to three real, clearly-signaled, one-level-deep reference files (built-in-elements.md, footprints.md, pcb-config.md), each with a stated purpose.

5 / 5

Total

19

/

20

Passed

Description

70%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 has a clear, well-scoped 'when' trigger and a distinctive niche, but it lists work areas rather than stating what the skill actually does, leaving the 'what' only implied. Stronger if rewritten as a third-person capability statement (e.g. 'Owns Replicator PCB source, layout, routing, DRC, fabrication, and visual-review policy.') followed by the existing 'Use when...' clause.

Suggestions

Lead with a concrete capability verb (e.g. 'Owns and enforces Replicator PCB source, layout, routing, DRC, fabrication, and visual-review policy') so the 'what' is explicit, not implied.

Add a few concrete trigger synonyms users might say, such as Gerbers, drill files, or .kicad_pcb, to broaden natural keyword coverage.

Keep the strong 'Use before...work' clause but pair it with the stated action so both 'what' and 'when' are unambiguous.

DimensionReasoningScore

Specificity

Lists several concrete PCB work areas ("source, layout, routing, DRC, fabrication, PCB visual-review") rather than vague language, but enumerates work domains rather than discrete actions, so it stops short of fully comprehensive.

4 / 5

Completeness

The 'when' is explicit ("Use before Project Replicator PCB...work"), but the 'what' is only implied via a list of work areas rather than a stated capability, so completeness caps at 3 per the missing-element guidance.

3 / 5

Trigger Term Quality

Natural PCB-engineer terms ("layout, routing, DRC, fabrication, visual-review") plus an explicit "Use before...work" trigger give good keyword coverage, though file-extension synonyms (e.g. .kicad_pcb, Gerbers) are absent.

4 / 5

Distinctiveness Conflict Risk

The named "Project Replicator PCB" niche is narrow with distinct triggers and explicitly delegates general tscircuit concerns to a separate skill, minimizing conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (505 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
JimmyPang02/open-replicator
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.