An exemplary instruction-only skill body: a tight numbered workflow with explicit validation gates, feedback loops, failure handling, and stop conditions, exact tool-level commands, and clean one-level-deep progressive disclosure into a real, well-organized reference bundle. No weaknesses found against the rubric anchors.

Dimension	Reasoning	Score
Conciseness	The body is lean and imperative: numbered operational steps, no explanations of concepts Claude already knows, no padding. Every clause (including the enumerations in step 3 and the boundary rules in steps 8-9) constrains behavior and earns its tokens — anchor 5.	5 / 5
Actionability	Fully executable guidance for an instruction-only skill: exact tool invocations with parameters (`parts.detail`, `user.ask` with `purpose="bom_item_confirmation"`, `pcb.run(profile="check")` / `pcb.run(profile="release")`), named files to read, and named fields to inspect. This matches anchor 5's copy-paste-ready commands covering the common cases.	5 / 5
Workflow Clarity	A clear 9-step sequence with explicit validation gates ("Re-validate required fields", "Set `bom_ready` true only after design-critical items are resolved"), a feedback loop ("Write every answer back and repeat only while concrete design-critical items remain"), and explicit failure handling ("return `bom_ready: false` with mitigation steps"). The batch BOM-export operation is fully covered by validation checkpoints, so no cap applies — anchor 5.	5 / 5
Progressive Disclosure	The SKILL.md is a concise orchestration overview, with detailed material appropriately split across three real, verified reference files (`hardware-bom-schema.md`, `sourcing-evidence-contract.md`, `finalization-contract.md`), each listed in a References section with a one-line purpose. References are one level deep and well signaled — anchor 5.	5 / 5
	Total	20 / 20 Passed

Description

67%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 concise, domain-specific trigger with an explicit "Use when" clause and several concrete actions, weakened mainly by the absence of the domain's most natural keyword ("BOM" / "bill of materials") and by actions phrased only as conditions on the artifact rather than as the skill's capabilities.

Suggestions

Add "BOM" and "bill of materials" as explicit trigger terms — these are the words users would most naturally say when they need this skill.

State the skill's actions directly (e.g., "Validates, enriches, and exports a selected electronic parts list / BOM") in addition to the "Use when" condition clause, so the "what" is explicit rather than inferred.

Replace the abstract "made procurement-ready" with a concrete action verb (e.g., "prepared for ordering") to tighten the last capability listed.

Dimension	Reasoning	Score
Specificity	The description names the domain ("selected electronic parts list") and lists several concrete actions ("validated, enriched, exported"), matching anchor 4. It falls short of anchor 5 because "made procurement-ready" is abstract and the actions are stated as conditions on the artifact rather than comprehensively covering what the skill does; it is clearly above anchor 3's 1-2 concrete actions.	4 / 5
Completeness	The "when" is explicit via the "Use when..." clause, and the "what" (validate, enrich, export) is present but only embedded inside the condition phrasing rather than stated as the skill's own actions. This fits anchor 4 ("both present; could be more explicit"), not anchor 5 which requires both clearly and explicitly stated.	4 / 5
Trigger Term Quality	Relevant terms are present ("electronic parts list", "validated", "enriched", "exported", "procurement-ready"), but the most natural keywords a user would say for this domain — "BOM" and "bill of materials" — are missing, matching anchor 3 ("some relevant keywords but missing common variations or synonyms") rather than anchor 4's good coverage.	3 / 5
Distinctiveness Conflict Risk	The staging language ("selected" parts list, "procurement-ready") carves out a clear niche that distinguishes it from generic document/export skills, but there is minor overlap risk with closely related component-selection and sourcing skills in the same EE domain — anchor 4 rather than anchor 5's minimal conflict risk.	4 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: reference/replicator-original/ee/bom-finalizer/SKILL.md
Commit: 18436cc

Reviewed: 18 hours ago

Table of Contents

Discovery Implementation Validation

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.