electronics-sourcing
Guide for AI agents to source electronic components using parts-mcp — tool sequencing, decision patterns, and multi-step workflows
62
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./content/sourceparts/skills/electronics-sourcing/SKILL.mdQuality
Discovery
32%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 identifies its domain (electronic component sourcing via parts-mcp) but relies on abstract meta-language ('decision patterns,' 'multi-step workflows') instead of listing concrete actions. It completely lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill. The trigger terms are too narrow and miss common user vocabulary around component sourcing.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks to find, source, or compare electronic components, check part availability, or build a bill of materials.'
Replace abstract meta-language ('decision patterns, multi-step workflows') with concrete actions like 'search for electronic parts, compare distributor pricing, check stock availability, find alternative components.'
Include natural user terms and file/format references such as 'BOM,' 'bill of materials,' 'component search,' 'distributor,' 'Mouser,' 'Digi-Key,' 'part number lookup.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (electronic component sourcing) and mentions some aspects like 'tool sequencing, decision patterns, and multi-step workflows,' but these are meta-descriptions of the skill's structure rather than concrete actions like 'search for components, compare prices, check availability.' | 2 / 3 |
Completeness | Describes what the skill is about at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'electronic components,' 'parts-mcp,' and 'source,' but misses common user variations like 'find parts,' 'component availability,' 'BOM,' 'distributor,' 'Mouser,' 'Digi-Key,' 'datasheet,' or 'procurement.' | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'parts-mcp' and 'electronic components' provides some distinctiveness, but the vague framing around 'tool sequencing, decision patterns, and multi-step workflows' could overlap with any MCP-based workflow skill. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill that provides clear tool sequencing patterns, explicit decision rules, and well-structured multi-step workflows with appropriate validation checkpoints. Its main weakness is that it's somewhat long for a single SKILL.md file — the content is good but could benefit from splitting detailed workflows (KiCad, manufacturing, cost optimization) into referenced sub-files. The conciseness is generally good but has room for minor tightening.
Suggestions
Consider splitting KiCad workflow, manufacturing pipeline, and cost optimization sections into separate referenced files to improve progressive disclosure and reduce the main file's token footprint.
Tighten the introductory sentence and some explanatory prose (e.g., 'This skill teaches you how to...' adds no value; partial failure explanations could be more telegraphic).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and well-organized, but includes some unnecessary elaboration. Phrases like 'This skill teaches you how to source electronic components effectively' and some of the explanatory text around partial failures could be tightened. However, it largely avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete tool calls with specific parameter examples, clear decision rules (e.g., '3+ specific parameters → use search_by_parameters'), and exact function signatures. The response patterns section maps user intents directly to tool sequences, making guidance immediately executable. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and explicit validation checkpoints. The BOM processing pattern includes polling logic with status checks, the manufacturing pipeline enforces DFM-first ordering, and partial failure handling includes clear feedback loops (attempt search → if still unmatched → report to user). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and logical grouping, but it's a fairly long monolithic document (~150 lines of substantive content). Some sections like the detailed partial failure handling, KiCad workflow, and cost optimization tips could be split into referenced files to keep the main skill leaner. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- andrewyng/context-hub
- Commit
eeb895b
- 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.