菜单
Inspect, derive, and measure QSpice waveform results after a simulation. Use when reading signals from a `.qraw`, comparing nodes, computing derived expressions like V(out)-V(in), measuring RMS/peak/gain/THD, or exporting traces for further analysis.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Place schematic components readably without overlap — use suggest_component_placement, add_component auto_place, or apply_schematic_layout_spec for batch JSON specs; keep parts upright (0° rotation), and follow workflow coordinate tables for complex circuits like buck converters.
Author, scaffold, build, and validate QSpice `.DLL` custom-device blocks for mixed-signal C/C++ models. Use when adding a controller or behavioral block backed by compiled code, generating a C++ scaffold from a symbol, building the DLL, or checking that a symbol matches its source.
Simulate and characterize switching power converters in QSpice. Use for buck/boost/SMPS work — staging transient and AC analyses, measuring efficiency and step response, and assessing loop gain, phase margin, and gain margin for stability.
Drive the QSpice MCP server end to end — discover or author a circuit, generate a netlist, run a simulation, and read or measure waveforms. Use when starting any QSpice task, when unsure which tool to call, when asked to simulate a circuit, build a buck/boost or other topology, inspect a .qsch, or read simulation results.
Diagnose and fix QSpice simulations that fail to converge, stop early, or produce no usable waveform. Use when a run errors, the log shows "no convergence", "timestep too small", singular-matrix, or gmin-stepping failures, or when V(out) is missing/flat after a simulation.
| name | qspice-waveform-analysis |
| description | Inspect, derive, and measure QSpice waveform results after a simulation. Use when reading signals from a `.qraw`, comparing nodes, computing derived expressions like V(out)-V(in), measuring RMS/peak/gain/THD, or exporting traces for further analysis. |
| license | MIT |
| metadata | {"author":"qspice-mcp","version":"1.0"} |
A workflow for turning a completed .qraw result into answers: which signals
exist, what a derived quantity looks like, and what the scalar metrics are.
V(out)-V(in) or instantaneous power V(n1)*I(L1).qspice-convergence-debugging.qspice-getting-started.list_signals (and list_steps for stepped/.step runs) to
learn the exact, case-correct signal names. QSpice lowercases net names, so a
node drawn as VOUT is read as V(vout).read_waveform with a signal and optional
t_start/t_end. Responses are budget-capped (2000 points); narrow the
window instead of asking for everything.evaluate_waveform_expression with an arithmetic
expression over signal tokens — V(out)-V(in), V(out)*I(L1),
2*V(fb). Only + - * / **, parentheses, and numeric constants are allowed;
all referenced signals must share one axis (same raw, step, window).measure_waveform for RMS/mean/max/min/peak-to-peak on one
signal; read_fourier for .four THD summaries; read_noise for .noise
integrated/spot output.plot_waveforms for a PNG preview; export_waveform_csv
when downstream tooling needs the full series outside the MCP budget.list_signals first; never assume casing.evaluate_waveform_expression over manually reading two traces and
subtracting by hand — it aligns axes and applies the budget.component (magnitude/phase) rather
than relying on auto.measure_waveform, not just that the
read succeeded.