CtrlK
BlogDocsLog inGet started
Tessl Logo

pcb-release-review

Independently audit one immutable, Host-frozen PCB release candidate using the design's own editable source, its manufacturing reports, and board-frame measurements from `pcb.measure`. Use only for the Host-owned PCB release review that returns a prioritized Markdown report; do not use for PCB editing, routing, or fabrication export.

76

Quality

93%

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

100%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 content is an exemplar of an instruction-only review skill: tight, concrete, and unambiguous about what to read, how to measure, how to classify findings, and how to format the final report. No bundle files are needed or referenced.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it never explains what a PCB, DRC, or BOM is, and every line (including the footprint-geometry caution) is load-bearing rather than padded.

5 / 5

Actionability

Concrete and executable: names exact files (source/pcb.config.json, product/bom.json, product/constraints.json, reports/), exact `pcb.measure` sub-commands with their return values, and a fixed report structure with a hard P0-citation rule.

5 / 5

Workflow Clarity

A numbered 5-step procedure with an explicit validation checkpoint ("Compare declared intent against produced artifacts"), a P0 evidence gate ("If you cannot measure it, it is not a P0"), and a defined end-state; the read-only, non-destructive nature means no batch/destructive cap applies.

5 / 5

Progressive Disclosure

A self-contained ~45-line skill with no bundle files and no external references, organized into clear sections (Procedure, Priorities, Report Format, Out of scope) — meeting the simple-skill exception for a 5.

5 / 5

Total

20

/

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.

The description is well-constructed: it states a concrete purpose, lists the inputs it works from, names the deliverable, and gives explicit positive and negative trigger guidance. It is distinct from sibling PCB skills and uses correct third-person voice.

Suggestions

Consider splitting "audit" into two or three named concrete actions (e.g. "compares declared intent against produced artifacts and reports P0/P1/Deferred findings") to push specificity toward a 5.

Add a couple of natural synonyms users might say (e.g. "board review", "release sign-off") alongside "PCB release review" to widen trigger coverage.

DimensionReasoningScore

Specificity

Enumerates concrete inputs ("editable source, its manufacturing reports, and board-frame measurements from `pcb.measure`") and a concrete deliverable ("prioritized Markdown report"), but the actions are consolidated under a single "audit" verb rather than a list of discrete specific actions.

4 / 5

Completeness

Clearly answers both what ("Independently audit one immutable, Host-frozen PCB release candidate ... returns a prioritized Markdown report") and when ("Use only for the Host-owned PCB release review") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural triggers are present ("PCB release review", "Host-owned PCB release review", "prioritized Markdown report") alongside explicit anti-triggers ("PCB editing, routing, or fabrication export"), with only a few synonyms missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche ("Host-owned PCB release review") with an explicit negative boundary ("do not use for PCB editing, routing, or fabrication export") gives minimal conflict risk with other skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.