component-selection

Use when electronic components must be selected, priced, checked for stock, compared with alternatives, or prepared as BOM-ready candidates with datasheet-backed implementation evidence.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 well-structured, actionable skill body that defers detail to real, clearly-labeled reference files and includes a validation gate around the irreversible PCB release step. The main weaknesses are a dense compound sentence and feedback loops that are implied rather than explicit.

Suggestions

Split the long 'Do not proceed from pinout recognition...' sentence into shorter sequenced steps for readability and token efficiency.

Make the error-recovery loop explicit (e.g., 'If pcb.run(profile="check") reports errors: fix and re-run check before proceeding to release').

Include one inline example of the expected structured JSON output or a sample tool call with arguments so guidance is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Lean and directive with no basic-concept padding, but the long compound sentence in the 'Do not proceed from pinout recognition...' paragraph is dense and could be split to tighten further, so it sits below the every-token-earns-its-place anchor.	4 / 5
Actionability	Names concrete, executable tools and commands ('parts.search', 'parts.detail', 'pcb.run(profile="check")', 'source/pcb.config.json') in a clear sequence, but provides no inline example invocation with arguments or sample structured JSON output (deferred to references), leaving minor gaps.	4 / 5
Workflow Clarity	Seven numbered steps with an explicit validation gate ('Only a current successful check authorizes pcb.run(profile="release")'), but the fix-and-revalidate feedback loop is implied rather than spelled out, so it falls just short of the explicit-recovery anchor.	4 / 5
Progressive Disclosure	A concise overview body pointing to well-signaled, one-level-deep references (selection-workflow.md, enclosure-constraints.md, schema.md — all real bundle files) each with a one-line description, with detail appropriately split into those files.	5 / 5
	Total	17 / 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 strong, specific description that clearly states both capabilities and a 'Use when' trigger with concrete, domain-appropriate keywords. Slightly technical phrasing in the latter half prevents a perfect trigger-term score.

Suggestions

Add common synonyms users might say ('parts', 'sourcing', 'component sourcing') to broaden natural trigger coverage.

Soften jargon like 'BOM-ready candidates' and 'datasheet-backed implementation evidence' toward phrasings a user would naturally request.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'selected, priced, checked for stock, compared with alternatives, or prepared as BOM-ready candidates with datasheet-backed implementation evidence' — giving comprehensive coverage rather than the minor gaps of a 4.	5 / 5
Completeness	Explicitly answers both what (component selection, pricing, stock, comparison, BOM preparation) and when via the concrete 'Use when...' trigger clause, matching the anchor for clear what-and-when with trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('electronic components', 'stock', 'alternatives', 'BOM'), but the jargon-heavy phrases 'BOM-ready candidates' and 'datasheet-backed implementation evidence' and the absence of common synonyms like 'parts' or 'sourcing' keep it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (electronic component selection with datasheet evidence) with distinct, specialized triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 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/component-selection/SKILL.md
Commit: 18436cc

Reviewed: 1 day 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.