Install
$ agentstack add skill-milind220-ki-stack-ki-stack-render ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
ki-stack-render
Purpose
This skill teaches the agent how to turn KiCad design artifacts into visual outputs.
It is the canonical ki-stack skill for:
- schematic rendering
- PCB 2D rendering
- PCB 3D raster rendering
- symbol rendering
- footprint rendering
- SVG to PNG conversion when raster images are needed
- before/after visual verification
When to use it
Use this skill when the user asks to:
- render a schematic sheet or whole schematic
- render a board or a specific layer set
- get a visual look at a symbol or footprint
- export PDF or SVG deliverables
- generate a PNG/JPEG screenshot-like artifact
- verify that a change actually looks correct
Shared assumptions
- Prefer
kicad-clias the default render path. - Prefer deterministic exports over GUI screenshots.
- If the model needs raster images and the CLI emits SVG, convert the SVG to PNG.
- Always report exact command lines and output paths.
Phase 1: Orient
- Locate
kicad-cli:
``bash skills/ki-stack/bin/kicad-cli-path ``
- Detect the version:
``bash skills/ki-stack/bin/kicad-version ``
- If the input path is unclear, find likely KiCad files:
``bash skills/ki-stack/bin/kicad-project-find ``
Phase 2: Identify render target
Choose one of these target classes:
- schematic
- pcb-2d
- pcb-3d
- symbol
- footprint
Map the request to the target class before choosing the command.
Examples:
- "Show me this board" ->
pcb-2dorpcb-3d - "Render this symbol" ->
symbol - "Give me a screenshot of the footprint" ->
footprint - "Visualize page 2 of the schematic" ->
schematic
Phase 3: Render
Use the helper wrapper whenever possible.
Schematic SVG
skills/ki-stack/bin/kicad-render schematic-svg design.kicad_sch out_dir
Schematic PDF
skills/ki-stack/bin/kicad-render schematic-pdf design.kicad_sch design.pdf
PCB SVG
skills/ki-stack/bin/kicad-render pcb-svg board.kicad_pcb out_dir --layers F.Cu,F.SilkS,Edge.Cuts --mode-single
PCB PDF
skills/ki-stack/bin/kicad-render pcb-pdf board.kicad_pcb board.pdf --layers F.Cu,F.SilkS,Edge.Cuts --mode-single
PCB 3D PNG/JPEG
skills/ki-stack/bin/kicad-render pcb-render board.kicad_pcb board.png --width 1800 --height 1200 --side top
Symbol SVG
skills/ki-stack/bin/kicad-render symbol-svg library.kicad_sym out_dir --symbol Device:R
Footprint SVG
skills/ki-stack/bin/kicad-render footprint-svg my.pretty out_dir --footprint SOIC-8_3.9x4.9mm_P1.27mm
Phase 4: Convert if needed
If the output is SVG but the downstream model needs PNG:
skills/ki-stack/bin/kicad-svg-to-png input.svg output.png
Phase 5: Verify
For render tasks, verification means:
- the command succeeded
- the output file exists
- the output format matches what the user asked for
- if this is a before/after check, both paths are preserved and clearly labeled
Prefer a before/after loop for edit verification:
- render before
- perform edit
- render after
- report both artifact paths
Phase 6: Report
Always report:
- render target type
- command used
- output path(s)
- any conversion steps used
- any version-specific caveats
Helper assets
References:
skills/ki-stack/references/render-recipes.mdskills/ki-stack/references/version-matrix.md
Helpers:
skills/ki-stack/bin/kicad-cli-pathskills/ki-stack/bin/kicad-versionskills/ki-stack/bin/kicad-project-findskills/ki-stack/bin/kicad-renderskills/ki-stack/bin/kicad-svg-to-png
Guardrails
- If
kicad-cliis unavailable, stop and reportBLOCKED. - If the input type is ambiguous, identify the file type before rendering.
- If a command fails, capture stderr and try a narrower invocation rather than guessing.
- If the user wants a GUI screenshot specifically, say that this skill produces deterministic exports rather than true live GUI screenshots.
Completion states
DONE: artifact created and path reportedDONE_WITH_CONCERNS: artifact created but format conversion or version caveat existsBLOCKED: no CLI or render command failed irrecoverablyNEEDS_CONTEXT: missing input path, missing target symbol/footprint name, or output format is unspecified
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Milind220
- Source: Milind220/Ki-Stack
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.