Borrowing it
Nothing to install: this file belongs to oaslananka/easyeda-mcp-pro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/oaslananka/easyeda-mcp-pro/main/.opencode/skills/design-validation/SKILL.mdgit clone --depth 1 https://github.com/oaslananka/easyeda-mcp-proWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/oaslananka/easyeda-mcp-pro/design-validation)<a href="https://agentmods.dev/skills/oaslananka/easyeda-mcp-pro/design-validation"><img src="https://agentmods.dev/badge/skills/oaslananka/easyeda-mcp-pro/design-validation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/oaslananka/easyeda-mcp-pro/design-validation"><img src="https://agentmods.dev/badge/skills/oaslananka/easyeda-mcp-pro/design-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.01524 |
| Opus 5 | $0.00016 | $0.00762 |
| Sonnet 5 | $0.00007 | $0.00305 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade A, and why
design-validation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Validation Skill
Use this skill when an AI agent is asked to validate an EasyEDA Pro schematic, PCB, BOM, export, or production handoff through EasyEDA MCP Pro.
This skill is specific to oaslananka/easyeda-mcp-pro and must stay aligned with the registered MCP tools in src/tools/ and the tool list in README.md.
When to use
Use this skill for:
- ERC review
- DRC review
- Semantic ERC and netlist checks
- PCB constraint review
- Power-tree analysis
- BOM and sourcing validation
- Production QA and export readiness review
- Manufacturing handoff risk reporting
Do not use this skill to approve a project for fabrication or assembly without qualified human review.
Required context
Collect:
- Active EasyEDA project and bridge status
- Which document tab is focused in EasyEDA Pro — schematic validation tools need the schematic tab active, PCB validation tools need the PCB tab active. A tool called against the wrong tab does not error, it silently returns an empty/
not_availableresult — do not report "no issues found" from a validation run that may simply have had no data to check. - Validation target: schematic, PCB, BOM, export, quote, or production package
- Manufacturer or assembly constraints
- Power rails, currents, connector requirements, and critical nets
- Expected board stackup and mechanical constraints
- Export directory and artifact requirements
- Existing waivers or accepted risks
Primary MCP tools
Health and capability checks
easyeda_health_checkeasyeda_bridge_statuseasyeda_get_capabilitieseasyeda_get_tool_profileseasyeda_run_self_testeasyeda_live_write_regression(dev profile) — exercises real write paths against the live bridge and reports pass/fail per step; use to distinguish "the bridge itself is misbehaving" from "the design has real issues" when validation results look suspicious
Schematic validation
easyeda_erc_run— native ERC is coarse (per-severity aggregate counts only, e.g. "1 warning"); it does not natively report which pin/net/component is affected. This tool supplements it withinferred_floating_pins/detail_source(best-effort, located via netlist inference) — treatdetail_source: 'native_aggregate_only'as a signal that no itemized detail is available for that run.easyeda_semantic_erc_auto— extracts nets/devices/pins from the live schematic and runs semantic ERC without a hand-authored netlist. Electrical types are inferred from pin/net naming conventions, not verified against EasyEDA's own metadata (which is unreliably populated — a passive part's pins can report a native type like "IN"). Prefer this overeasyeda_semantic_erc_validatewhen the goal is validating what's actually drawn, not a hypothetical netlist.easyeda_semantic_erc_validate— same rule engine as..._auto, but takes a fully hand-authorednets/devicesstructure. Use when the schematic isn't drawn yet, or when inferred classification isn't trustworthy enough for the check being run.easyeda_schematic_validate_netlisteasyeda_schematic_verify_writeeasyeda_schematic_componentseasyeda_schematic_netseasyeda_schematic_net_detaileasyeda_power_tree_analyze
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 148 lines · 33 tokens per session scan A f92764eb3435
design-validation is a skill published in the GitHub repository oaslananka/easyeda-mcp-pro (45 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 1,524 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
loop2converge
The closed convergence loop for ANY benchmark subject — open-benchmark Evaluation, benchmark IC (doc→GDS), or IP-cell (doc→LEF/GDS). RUN the canonical front door, CLASSIFY every FAIL as flow / gate / tool, CONVERGE it by fixing the layer that owns it, PROVE the fix in the plugin cache against the real artefacts BEFORE…
phase1-coverage-loop
Closed-loop field-agent for Phase 1 coverage. Rotates through a benchmark IC folder (e.g. 2ndbanchmark/) running /vibe-ic-phase1 on each IC's README/prompt, measures input→L1-L27 token completeness with phase1inputvsgeneratedcompletenesscheck, and files chip-AGNOSTIC plugin backlog issues for systematic ingester gaps.…
formal-verify
Run formal property verification (FPV) on RTL by driving model-checkers such as SymbiYosys, Jasper, or VC Formal. Use when the user says "prove this", "formal verify", "model check", "run sby", or has SVA properties from assertion-gen that need to be proven or bounded.
phase2-rtl-verify
After designoneshotrunner emits RTL + SOF + reference TB PASS, AI spot-checks RTL quality and L9-contract conformance. Triggers when /vibe-ic-phase2 / /vibe-ic-phase2 returns PASS, or on phrases like "review the RTL", "check RTL quality", "verify phase 2 output".
kicad-pcb-review
Use this skill when reviewing, fixing, validating, or preparing KiCad PCB projects with the kicad MCP server.
analog-output-verify
After analogoneshotrunner emits A1..A9 outputs, AI spot-checks corner-sim coverage, hardmacro completeness, HIL data fidelity. Triggers on /vibe-ic-analog PASS or phrases like "review analog", "verify A8 hardmacro", "check analog corners".