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.

72

Quality

91%

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

86%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 tight, self-contained review procedure with exact file paths, tool calls, priority definitions with evidentiary requirements, and a concrete output template. The only improvements are marginal: trimming one over-explained warning and adding an explicit pre-report verification step.

Suggestions

Tighten the footprint-geometry warning in step 3 to its rule and one-line rationale (e.g., 'Never derive geometry from footprint source — footprint-local coordinates must be composed with placement rotation and board side first'), dropping the past-failure anecdote.

Add an explicit final checkpoint before ending the turn, such as 'Before finishing, re-check that every P0 and P1 line cites its measurement or report line', to close the workflow's validation gap.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no PCB fundamentals are explained, and lines like 'The sole declared finished board thickness is the `finishedThicknessMm` value under `manufacturing`' carry pure operational weight. One passage is trimmable: the footprint warning's failure anecdote ('a review that skipped that step has reported copper shorts that do not exist and prescribed a fix that would have broken a correct footprint') is motivating but over-explains, fitting the efficient-with-minor-trimming anchor rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

For an instruction-only skill, guidance is fully executable: exact files to read ('source/pcb.config.json', 'product/bom.json', 'product/constraints.json', 'reports/'), the exact tool to call ('Call `pcb.measure` for anything physical') with its returned sub-objects enumerated, the authoritative location of the thickness value, a concrete report template, and termination rules ('write `No findings.` after the summary and stop'). No gaps remain for the common case.

5 / 5

Workflow Clarity

A clear five-step sequence with real checkpoints: an evidentiary rule ('Every `P0` must cite a measurement or a report conclusion. If you cannot measure it, it is not a `P0`'), a conflict-resolution rule for thickness, and a defined end state. It sits just below the anchor-5 example because there is no final self-verification pass (e.g., re-checking each P0's citation before ending the turn) and no error-recovery loop, which the top anchor expects.

4 / 5

Progressive Disclosure

The skill has no bundle files (no references/, scripts/, or assets/ exist) and needs none: at ~44 lines it is self-contained and cleanly sectioned (Procedure, Priorities, Report Format, Out of scope), matching the scoring note that short skills with no need for external references score 5 on well-organized sections alone.

5 / 5

Total

18

/

20

Passed

Description

92%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 dense, highly specific description that names the exact action, its three input sources, its output artifact, and explicit positive and negative triggers. The only weakness is modest synonym coverage, which slightly limits natural-language triggering.

DimensionReasoningScore

Specificity

Concrete actions are explicitly listed: 'audit one immutable, Host-frozen PCB release candidate' with named inputs ('the design's own editable source, its manufacturing reports, and board-frame measurements from `pcb.measure`') and a defined deliverable ('returns a prioritized Markdown report'). Coverage is comprehensive for the skill's scope, matching the multiple-concrete-actions anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Both halves are explicit: the 'what' ('Independently audit one immutable, Host-frozen PCB release candidate using... measurements from `pcb.measure`... returns a prioritized Markdown report') and the 'when' ('Use only for the Host-owned PCB release review'), with negative triggers ('do not use for PCB editing, routing, or fabrication export'). This clearly matches the both-what-and-when-with-concrete-triggers anchor.

5 / 5

Trigger Term Quality

Good natural keywords: 'PCB release review', 'audit', 'release candidate', 'PCB', 'manufacturing reports', plus exclusion terms ('PCB editing, routing, or fabrication export') that add disambiguating vocabulary. Common synonyms like 'board review', 'design review', or 'tape-out' are missing, so it falls just short of the comprehensive-synonym anchor at 5.

4 / 5

Distinctiveness Conflict Risk

A clearly delineated niche — 'the Host-owned PCB release review' — with explicit exclusion of adjacent PCB skills (editing, routing, fabrication export), giving minimal conflict risk. It is well above the minor-overlap anchor at 4.

5 / 5

Total

19

/

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.

Validation — 16 / 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.