electronics-sourcing
Guide for AI agents to source electronic components using parts-mcp — tool sequencing, decision patterns, and multi-step workflows
49
55%
Does it follow best practices?
Impact
—
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 ('tool sequencing, decision patterns, multi-step workflows') instead of listing concrete actions. It completely lacks explicit trigger guidance ('Use when...'), making it difficult for Claude to know when to select this skill. The description reads more like a document subtitle than a functional skill description.
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 with concrete actions, e.g., 'Search for electronic components across distributors, compare pricing and availability, resolve part numbers, and build sourcing plans using parts-mcp.'
Include natural user keywords like 'find parts,' 'component search,' 'BOM,' 'distributor,' 'stock check,' 'part number lookup,' and common file/format references.
| 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,' or 'procurement.' | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'parts-mcp' and 'electronic components' provides some distinctiveness, but 'tool sequencing, decision patterns, and multi-step workflows' is generic enough to overlap with any agent workflow skill. The niche is somewhat clear but not sharply defined. | 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 with excellent workflow clarity and concrete tool usage examples. The multi-step patterns with validation checkpoints and partial failure handling are particularly well done. The main weaknesses are moderate verbosity (some redundancy between the workflow section and response patterns) and the monolithic structure that could benefit from splitting into overview + reference files.
Suggestions
Trim the 'Response Patterns' section which largely restates workflows already defined earlier, or consolidate them into a single quick-reference table
Remove explanatory sentences that state the obvious to Claude (e.g., 'This is the core sourcing workflow', 'Real-world sourcing often has partial results') to improve token efficiency
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary verbosity. Phrases like 'This skill teaches you how to source electronic components effectively' and explanatory sentences like 'Do not skip steps 3 and 4. A part that exists in the database may be out of stock or prohibitively expensive' over-explain things Claude would infer. The response patterns section partially duplicates earlier workflow descriptions. | 2 / 3 |
Actionability | The skill provides concrete tool calls with specific parameter examples, clear decision rules (e.g., '3+ specific parameters → search_by_parameters'), and exact function signatures. The examples are directly executable with real tool names and parameter structures, making guidance copy-paste ready. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps, explicit validation checkpoints (polling for async status, DFM before fab quotes), and error recovery patterns (handling unmatched parts, unavailable parts, partial failures). The BOM processing and manufacturing pipelines include feedback loops for retry/resolution. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical grouping, but it's a monolithic document (~150 lines) with no references to external files. The response patterns section and cost optimization tips could be split into separate reference files. However, since no bundle files exist, there's nothing to reference, which limits the score. | 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
04c149c
- 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.