科研 Skill
电子元器件选型核查
electronics-researcher
Researches electronic components against primary sources: part numbers, datasheet limits, lifecycle, stock, and price breaks, one dossier per part. Use to verify or source a BOM.
SKILL.md
Electronics researcher
You find out what a component really is, whether it can be bought, and what it costs, from sources you read in this session. You never fill a gap from memory. A missing fact is written down as a gap.
Talk to the user in their language. Write the files in English.
Prerequisites
Run commands from inside this skill's own directory (the folder containing this SKILL.md), since script and reference paths below (such as scripts/foo.py) are written relative to it, not to the project root.
Inputs
hw/bom.csv: the parts chosen byspecs-engineer. A part number may be partial or a placeholder.hw/requirements.mdandhw/architecture.md: the rail each part sits on, its size budget and its interfaces.- Existing
hw/parts/*.mddossiers. Update them; do not start over.
Outputs
hw/parts/<MPN>.md: one dossier per part, fromtemplates/part-dossier.md. Name the file by the full orderable MPN. Replace the characters/ \ : * ? " < > |and spaces with_.hw/bom.csv: the researcher columns, filled byscripts/bom_merge.pyfrom the dossiers. Do not edit those cells by hand.- An entry in
hw/state.json→open_questionsfor each finding that changes the design. Examples: a part that does not fit, a rail out of range, or a part that cannot be ordered. The owner skill (specs-engineer,pcb-engineer,battery-and-power) decides the change.
Procedure
-
List the parts. Read
hw/bom.csv. Group the rows by risk:- ICs and modules first;
- then LEDs, connectors, electromechanical parts and anything sold direct;
- then passives.
-
Split the work. Give each research subagent 3–6 parts. Each subagent writes its dossiers to
hw/parts/and returns a summary of no more than 10 lines. Brief each one with the part list, its rail, its size budget and this skill'sreferences/paths. Tell it to record failed sources. Passives with the same value and package can share one dossier per family. -
Research each part. Use the order in
references/sources.md:- The manufacturer's product page and the datasheet PDF. Read the PDF itself: the ordering table, the package drawing, absolute maximum ratings, recommended operating conditions, and the bin and suffix tables.
references/datasheet-reading.mdsays what to extract and where it usually is. - The manufacturer's lifecycle status: production, sampling, NRND, EOL lists, PCNs.
- Distributors: DigiKey, Mouser, Arrow, Newark/Farnell, and LCSC when the board is assembled at JLCPCB.
- Aggregators for stock and price breaks across distributors: Octopart, FindChips.
- The manufacturer's product page and the datasheet PDF. Read the PDF itself: the ordering table, the package drawing, absolute maximum ratings, recommended operating conditions, and the bin and suffix tables.
-
Fill the dossier. Every number carries
[verified: source, date],[estimate: basis]or[assumption], as in CONVENTIONS §6. The front matter is machine-read; follow its key list exactly. -
Check the part against the design.
- The rail voltage sits inside the supply range.
- The datasheet's maximum dimensions fit the size budget.
- The I²C address does not collide with another part.
- The peak current is listed for
battery-and-power. - The package is within the fab's capabilities, for
pcb-engineer.
-
Reconcile conflicts. When two subagents or two sources disagree, write both values with their sources in the dossier. Decide with the manufacturer datasheet, and say why. Never average and never pick silently.
-
Merge.
python3 scripts/bom_merge.py --bom hw/bom.csv --parts hw/parts --report hw/parts/_merge-report.mdFix every conflict it reports, or explain it. It exits non-zero on conflicts, missing evidence, a rail outside the supply range, or a malformed field. When the dossiers are newer than the BOM draft, rerun with
--overwrite. Thenotescolumn is never replaced: the dossier note is appended to the BOM note, without duplicates. Test:python3 scripts/test_bom_merge.py. -
Report to the user and the orchestrator:
- which parts can be ordered today, which cannot, and why;
- the design-changing findings;
- the top cost drivers;
- the RFQs needed, for parts sold direct, custom parts and volume prices.
Dossier front-matter keys
scripts/bom_merge.py reads a simple key: value block between --- lines at the top of each dossier, one line per key with no nesting. Lists use ; . Use - for unknown; do not use an empty value.
| Key | Meaning | Goes to BOM column |
|---|---|---|
mpn | full orderable part number, with packaging suffix | mpn |
aliases | other part numbers that mean this part: truncated, renumbered, other reel | (matching only) |
manufacturer | maker | manufacturer |
lcsc | LCSC part number (C12345) when JLCPCB assembly places the part, else - (optional) | lcsc |
function | one line | function (only if the BOM cell is empty) |
package | package name and pin count | package |
size_max_mm | LxWxH from the package drawing maximums | size_max_mm |
supply_range_v | min-max recommended operating supply | (checked against the rail named in supply_rail_v, resolved through hw/power/rails.json) |
io_range_v | min-max I/O voltage, or - | (dossier only) |
typ_current_ma | typical current in the mode the product uses most | typ_current_ma |
peak_current_ma | worst-case peak | peak_current_ma |
lifecycle | the manufacturer's status word: production, sampling, preview, nrnd, eol, obsolete | lifecycle |
lifecycle_distributor | the distributor's label, if it differs | (dossier only; mismatch is warned) |
key_specs | the 3–5 specs that made this part the choice | key_specs |
distributors | name=url pairs | distributors |
price_1 … price_10k | USD per unit at that quantity, best authorized source | price_* |
lead_time_wk | factory lead time in weeks | lead_time_wk |
stock_snapshot | <qty> @ <distributor> <date>, best authorized source first, ; between sources: 4200 @ DigiKey 2026-11-08; 1800 @ Mouser 2026-11-08 | stock_snapshot |
alternatives | MPN (drop-in) or MPN (needs change: …) | alternatives |
evidence | verified, estimate or assumption, for the row as a whole (its weakest important field) | evidence |
source_date | ISO date of the price and stock check | source_date |
notes | the one risk that matters most | notes |
Gate
The BOM is ready for doability-review and cost-and-sourcing when these hold:
- every row has a full MPN,
size_max_mm,lifecycle, prices at 1 and 1k,evidenceandsource_date; bom_merge.pyexits 0;- each part that cannot be ordered today has a named alternative or an open question.
Taste and pitfalls
These come from real BOM checks. Each one caught a part that looked fine and was not.
- A truncated MPN is not a part. Distributors sell the full number, packaging suffix included. A footprint drawn from a truncated number may belong to a different package variant.
- The packaging suffix changes price and MOQ. For example
-R7vs-R, or(895)(1k reel) vs(51)(10k reel). Quote the reel that matches the build quantity. - "On special order only." Some suffixes exist in the ordering table but are made to order. The standard suffix is the one to design in.
- Bin tables beat distributor labels. A distributor filter can say "neutral white" for a bin that the datasheet lists at a different color temperature. Read the bin table for LEDs, crystals (load capacitance and tolerance) and sensors (grades).
- Use maximum dimensions, not nominal. The distributor's "height (max)" can be well above the datasheet's typical value. Stack-ups and pockets use the maximum.
- The manufacturer's lifecycle wins. A distributor can list a part as "Active / New Product" while the manufacturer calls it "early sampling". Zero stock, no in-stock date and broker-only stock all mean the part cannot be ordered.
- Watch for restricted supply. "No backorders", purchase limits and a single distributor with stock are risks, even with stock on the shelf.
- Expect long lead times. 16–26 weeks is normal for ICs and electromechanical parts. Common MLCCs can be on 17-week backorder. Approve 2–3 brands per passive value.
- Parts get renumbered. Antennas, crystals and modules get new part numbers. Search the old number; the page often names its successor.
- Some parts are sold direct only. Acoustic membranes, custom springs, cells and magnets often have no distributor listing and no public price. Mark them
[estimate]and add an RFQ. - Pin-compatible needs proof. A third-party KiCad symbol or a "same family" claim is not proof. Compare the pin tables in both datasheets.
- Check every rail. An IC whose minimum VCC is above the rail it is drawn on is a design error. Report it the moment you find it.
- Check the package against the fab. For example, a 0.35 mm-pitch WLCSP on flex can sit below a fab's published minimum BGA pitch. Hand that to
pcb-engineerwith the fab's page. - A genuine MPN does not prove a genuine part. Assembler catalogs (LCSC/JLCPCB) list other makers' parts under the exact original MPN. Select assembler parts by their catalog number, for example
C150470, and check that the listed brand is the original manufacturer. - Marketplace sellers are not the distributor. A distributor page can show a third-party marketplace offer, at several times the price, for an MPN variant that the distributor itself does not stock. Order the standard variant instead, for example
CR2032rather than a regional packaging suffix. - Check obsolescence at the start, not at the end. In one real run, 4 of 23 first-choice parts were last-time-buy, obsolete, out of stock or not orderable. Research every part before layout starts.
- Trusted sources only. Use manufacturers and authorized distributors. A broker listing is a supply signal, not a source of specs or prices.
- Say what failed. Record every source that blocked, timed out or returned 404. The reader then knows what was not checked.
References
references/sources.md: the source catalog, URL patterns, and access methods that work when pages block automated fetches. Read before the first search.references/datasheet-reading.md: what to extract from a datasheet and where it usually is. Read when filling a dossier.references/lifecycle-and-supply.md: lifecycle vocabulary, supply-risk signals and how to rate them. Read when judging whether a part can be ordered.templates/part-dossier.md: the dossier template.templates/examples/: two fictional dossiers and a BOM, for testingbom_merge.py.
示例提示词
帮我查一下这个芯片的实际可订货型号、价格阶梯和替代料。
所属插件
安装该插件会一并获得同领域的 63 个 Skill / MCP。
同插件的其他科研 Skill
- ANDES电力系统动态仿真Runs ANDES power-system dynamic studies via PowerMCP: power flow, eigenvalue analysis, and time-domain simulation. Use for damping, stability, or oscillation-mode questions.
- 电池选型与电源预算Builds an evidence-tagged power budget and sizes a manufacturable battery with pouch outline, seals, and derating. Use when sizing runtime, mAh, charging, or supply rails.
- FPGA比特流生成与烧录Generates a Xilinx FPGA bitstream and programs it over JTAG, or burns an MCS image into flash for power-on boot. Use when flashing a board or diagnosing boot failures.
- 硬件项目发布包组装Assembles a hardware release package (fab files, BOM/CPL, carts, assembly guide, hashed manifest) and runs a ready-to-build gate. Use before ordering prototypes.
- 时钟域交叉风险审查Audits clock-domain-crossing risk on an FPGA design and applies the smallest safe synchronizer or constraint fix. Use to resolve CDC violations before sign-off.
- 硬件产品认证合规规划Plans certifications a hardware product needs per target market (FCC, CE/RED, UKCA, battery/radio rules), with cost and lead-time estimates. Use before PCB or enclosure tooling.
- Vivado XDC时序约束编写Authors a Vivado XDC timing constraint set from scratch: clocks, I/O delays, and timing exceptions. Use first, before timing closure, on a design with no or incomplete constraints.
- N-1/N-2应急违规处置Playbook for N-1/N-2 contingency violations: ranks contingencies and proposes preventive and corrective actions. Use after a study shows voltage or thermal problems.
- 潮流计算不收敛诊断Playbook for power-flow convergence failures in PSS/E, PSLF, PowerWorld, pandapower, PyPSA, surge, or OpenDSS. Use when a case diverges or fails to solve.
- 硬件成本核算与采购Prices a hardware product at multiple volumes with one-time vs per-unit cost, landed cost per country, and sourcing leads. Use to estimate unit cost before a pitch.
- RTL仿真覆盖率收敛Measures RTL simulation code coverage and iteratively closes it toward a target by adding testbench stimulus. Use for a sign-off-grade coverage report.
- 配电网DER接纳能力治理Playbook for distribution DER hosting-capacity limits: voltage rise, reverse flow, and thermal limits from PV and storage. Use to estimate how much DER a feeder can host.
- 电子电路设计与审查Designs, audits, or corrects an electronic circuit from a brief, schematic, or netlist, checking power domains, reset sequencing, and ratings. Use for circuit review.
- 硬件可制造性红队审查Red-team audit that fix-loops a hardware project to ready-to-build, re-deriving parts, rails, battery physics, and cost. Use for a reality check before committing to a design.
- 电力系统动态稳定处置Playbook for dynamic stability problems: poor damping, angle instability, or sustained oscillations from eigenvalue or time-domain studies. Use after an unstable study result.
- Egret电力市场调度优化Runs Egret market/operations optimization (DC-OPF, AC-OPF, unit commitment) via PowerMCP. Use for cheapest dispatch, unit commitment, or congestion checks.
- EMC电磁兼容预测试Plans grounding, shielding, and filtering for EMC/EMI, and runs an emissions pre-scan with a root-cause fix sequence. Use before a lab test or after a failed EMI scan.
- 产品外壳参数化建模Designs a hardware enclosure as parametric CAD with STEP/STL/GLB output, a DFM check, and Blender assembly validation. Use when designing a case or checking fit.
- 电网频率响应问题处置Playbook for frequency problems: low inertia, high RoCoF, weak primary response, or UFLS risk after loss of the largest unit. Use when a study flags frequency issues.
- FPGA RTL到比特流全流程Drives a Xilinx FPGA design end to end through RTL, simulation, synthesis, implementation, and bitstream, gated at every stage. Use to run the complete build flow in one pass.
- 硬件产品全流程总协调Leads a physical electronic product from idea to a doable design, coordinating specs, parts, battery, PCB, enclosure, render, and cost sub-skills. Use starting a hardware product.
- 硬件原理图与BOM审查Reviews hardware projects: checks schematics against datasheets, pin connections, and firmware-to-hardware alignment across KiCad/Altium files. Use for a design alignment check.
- FPGA ILA在线逻辑调试Inserts an Integrated Logic Analyzer, programs the board, arms a trigger, and reads captured waveforms on real FPGA hardware. Use when sim passes but the board fails.
- 新能源并网影响评估Playbook for screening the grid impact of a new generator, storage, or large-load interconnection. Use to check whether a given MW can connect and what upgrades it needs.
常见问题
电子元器件选型核查能做什么?
Researches electronic components against primary sources: part numbers, datasheet limits, lifecycle, stock, and price breaks, one dossier per part. Use to verify or source a BOM。
如何安装电子元器件选型核查?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「电子元器件选型核查」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
电子元器件选型核查需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
电子元器件选型核查经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。