design-review

design-review is a skill for Claude Code from nickkraakman/skidl-skills. It costs 96 tokens per session (865 once invoked), scanned A, original, MIT.

A three-part review process for SKiDL circuits: electrical rule checking, architecture review against requirements, and code-quality review. It records severity-ranked findings and suggested fixes in a design-review file.

In plain words
What is it for?
Use it after writing or changing a SKiDL circuit, or before exporting its netlist or generating its bill of materials.
Why use it?
It catches electrical, design, and implementation problems before a circuit is exported or a bill of materials is generated.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the skidl-skills plugin — 4 skills, 9 agents, 2 hooks shipped together

Good fit Use it after writing or changing a SKiDL circuit, or before exporting its netlist or generating its bill of materials.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nickkraakman/skidl-skills/design-review
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add nickkraakman/skidl-skills --skill design-review
Clone the repo
git clone --depth 1 https://github.com/nickkraakman/skidl-skills

Made for: Claude Code.

Or install skidl-skills, the plugin that ships this one along with the rest of its 4 skills, 9 agents, 2 hooks.

Wrote 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.

agentmods badge for design-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/nickkraakman/skidl-skills/design-review/github.svg)](https://agentmods.dev/skills/nickkraakman/skidl-skills/design-review)
Your own site
<a href="https://agentmods.dev/skills/nickkraakman/skidl-skills/design-review"><img src="https://agentmods.dev/badge/skills/nickkraakman/skidl-skills/design-review/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.

agentmods 80×15 button for design-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/nickkraakman/skidl-skills/design-review"><img src="https://agentmods.dev/badge/skills/nickkraakman/skidl-skills/design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 865 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00096 $0.00865
Opus 5 $0.00048 $0.00432
Sonnet 5 $0.00019 $0.00173
Haiku 4.5 $0.00010 $0.00086

Measured 12d ago against content hash 5fb9fd589289, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

design-review 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 12d 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.

skills/design-review/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Review

When to use

  • Before exporting a netlist or generating a BOM
  • After skidl-coder finishes a circuit
  • User says "review the circuit", "design review", or "check the design"
  • Invoked via /skidl-ee:design-review [circuit_name]

Inputs

  • circuits/<circuit_name>.py — SKiDL source
  • SPEC.md — captured design requirements
  • architecture/ folder (if present) — block diagram and net plan
  • pipeline_state.json — current pipeline status

Procedure

Run these three checks (in parallel where possible):

1. Electrical Rules (ERC)

  • Spawn the erc-reviewer agent (it applies the erc-rules skill automatically)
  • Receive erc_report.md with pass/fail verdict

2. Architecture Sanity

  • Re-read SPEC.md and architecture/ folder
  • Check:
    • All functional blocks present in the circuit?
    • Power budget realistic?
    • Net plan complete and consistent with code?
    • Known design risks (decoupling, protection, EMI) addressed?

3. SKiDL Code Quality

  • Read current circuits/*.py file(s)
  • Verify using the .claude/rules/skidl-syntax.md rules:
    • Every part has ref, value, and footprint?
    • @subcircuit used for repeated blocks?
    • Decoupling caps named C_DECOUP_*?
    • NC on all intentionally unused pins?
    • Net naming: UPPERCASE power rails, camelCase signals?
    • ERC() call present in __main__?

4. Footprint Validation

  • Run: python3 .claude/scripts/validate-footprints.py circuits/<circuit_name>/ (or .py for monolithic)
  • Every missing footprint is a HIGH severity finding — it will cause KiCad import errors
  • For each missing footprint in the report:
    • If the script suggests close matches → recommend the corrected string
    • If no standard library match exists → generate a custom footprint:
      1. Read the datasheet mechanical drawing from datasheets/<MPN>_SUMMARY.md or PDF
      2. Run .claude/scripts/generate-footprint.py with pad positions and sizes
      3. Update the circuit code to reference ProjectLocal:FootprintName
  • Do not mark review complete until footprint validation exits 0

Read the full file on GitHub · 90 lines

Changes

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.

  1. 12d ago First seen · 90 lines · 96 tokens per session scan A 5fb9fd589289

Subscribe to this mod's changes

design-review is a skill published in the GitHub repository nickkraakman/skidl-skills (18 stars, last pushed 5mo ago), licensed MIT. It adds 96 tokens to every session and 865 once invoked, about $0.0005 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.