CtrlK
BlogDocsLog inGet started
Tessl Logo

bom-finalizer

Use when a selected electronic parts list must be validated, enriched, exported, or made procurement-ready.

77

Quality

96%

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.

A tightly written instruction skill with a clear, validated workflow and well-organized one-level references. It appropriately assumes domain competence and gates a batch-style export operation behind explicit readiness checks.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; nearly every token earns its place in the dense 9-step workflow.

5 / 5

Actionability

Concrete tool calls (parts.detail, user.ask with purpose='bom_item_confirmation', pcb.run profiles), specific file references, and explicit decision rules give fully executable guidance despite being instruction-only.

5 / 5

Workflow Clarity

A clearly sequenced 9-step process with explicit validation gates (re-validate at step 4, bom_ready gating at step 6) and a feedback loop (repeat step 5 until design-critical items resolve; return bom_ready:false with mitigations).

5 / 5

Progressive Disclosure

The References section signals three one-level-deep files with one-line descriptions, and all three (hardware-bom-schema.md, sourcing-evidence-contract.md, finalization-contract.md) are present in ./references/.

5 / 5

Total

20

/

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 concise, third-person description that clearly states both capability and trigger conditions. Adding the natural term 'BOM' or 'bill of materials' would push trigger coverage to fully comprehensive.

Suggestions

Add the natural synonyms 'BOM' or 'bill of materials' so users who say those terms trigger the skill.

Consider naming the input/output artifact explicitly (e.g., 'selected components to a procurement-ready BOM') to sharpen the what.

DimensionReasoningScore

Specificity

Names the electronic parts-list domain and lists four concrete actions ('validated, enriched, exported, or made procurement-ready'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

It explicitly answers both what (validate/enrich/export/procurement-ready) and when ('Use when a selected electronic parts list must be...') with a concrete trigger clause.

5 / 5

Trigger Term Quality

Good domain keywords are present, but common natural synonyms a user would say ('BOM', 'bill of materials') are missing, so it falls just short of comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The electronic-parts-list/procurement-ready niche is specific with distinct triggers and minimal overlap with other skills.

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.

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.