Agent skill

Autodesign

Drive an autonomous spec-to-board PCB design with the eda-agent MCP server (Altium Designer or EasyEDA Pro).

Apache-2.0Auto-check passedAgent Workflows

Install Autodesign

skills CLI

$ npx skills add salitronic/eda-agent --skill autodesign -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install salitronic/eda-agent autodesign --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/salitronic/eda-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/autodesign .claude/skills/autodesign && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "autodesign" agent skill from https://github.com/salitronic/eda-agent/tree/main/skills/autodesign into .claude/skills/autodesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autodesign", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/salitronic/eda-agent/tree/main/skills/autodesign

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add salitronic/eda-agent --skill autodesign -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install salitronic/eda-agent autodesign --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/salitronic/eda-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/autodesign .agents/skills/autodesign && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "autodesign" agent skill from https://github.com/salitronic/eda-agent/tree/main/skills/autodesign into .agents/skills/autodesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autodesign", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add salitronic/eda-agent --skill autodesign -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install salitronic/eda-agent autodesign --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/salitronic/eda-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/autodesign .cursor/skills/autodesign && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "autodesign" agent skill from https://github.com/salitronic/eda-agent/tree/main/skills/autodesign into .cursor/skills/autodesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autodesign", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/salitronic/eda-agent.git --path skills/autodesign

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add salitronic/eda-agent --skill autodesign -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install salitronic/eda-agent autodesign --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/salitronic/eda-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/autodesign .gemini/skills/autodesign && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "autodesign" agent skill from https://github.com/salitronic/eda-agent/tree/main/skills/autodesign into .gemini/skills/autodesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autodesign", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install salitronic/eda-agent autodesign

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add salitronic/eda-agent --skill autodesign -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/salitronic/eda-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/autodesign .github/skills/autodesign && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "autodesign" agent skill from https://github.com/salitronic/eda-agent/tree/main/skills/autodesign into .github/skills/autodesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autodesign", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add salitronic/eda-agent --skill autodesign -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install salitronic/eda-agent autodesign --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/salitronic/eda-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/autodesign .opencode/skills/autodesign && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "autodesign" agent skill from https://github.com/salitronic/eda-agent/tree/main/skills/autodesign into .opencode/skills/autodesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autodesign", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: autodesign
GitHub stars: 238
Token cost: ~1.2k tokens
SKILL.md length: 574 words
Files: 1
Skills in repo: 1
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Drive an autonomous spec-to-board PCB design with the eda-agent MCP server (Altium Designer or EasyEDA Pro).

Works in 5 steps: design_session_start(requirement) opens… → If a project is open or will be… → Loop: design_next_action(session_id) and… → …
Asks to design a board/schematic from a requirement
SKILL.md covers Before you start, The loop, How the board is laid out and Resuming, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Autodesign is an agent skill from salitronic/eda-agent. Drive an autonomous spec-to-board PCB design with the eda-agent MCP server (Altium Designer or EasyEDA Pro). Apply when the user asks to design a board/schematic from a requirement, wants an end-to-end autonomous design run, or mentions the design harness, designnextaction, design sessions, or spec-to-board. Requires the eda-agent MCP server connected to a running Altium Designer or EasyEDA Pro; the KiCad backend does not register the design harness.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers and Design review and critique. It works with Model Context Protocol and EasyEDA. The repository describes itself as: Open-source MCP server that lets an AI drive a live session of Altium Designer, and optionally KiCad or EasyEDA Pro, editing the open design in place while you watch. 300+ tools… The licence is Apache-2.0.

When your agent uses it

Asks to design a board/schematic from a requirement
Wants an end-to-end autonomous design run
Mentions the design harness
Designnextaction

Example prompts

“/autodesign”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

design_session_start(requirement) opens the durable journal. Keep the
If a project is open or will be modified, checkpoint first so the whole
Loop: design_next_action(session_id) and act on status
Checkpoint again before each high-risk mutating stage: sch_to_pcb,
Long engine runs (routing a dense board) can exceed the tool timeout;

What it can do on your machine

Read from SKILL.md and the folder at commit fc97ec8. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Autodesign loads about 1.2k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 574 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~117
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from salitronic/eda-agent at commit fc97ec8, republished under its Apache-2.0 licence (© salitronic). 574 words, ~1,175 tokens.

Download SKILL.mdSave it as .claude/skills/autodesign/SKILL.md (or your agent's skills folder).

name: autodesign
description: Drive an autonomous spec-to-board PCB design with the eda-agent MCP server (Altium Designer or EasyEDA Pro). Apply when the user asks to design a board/schematic from a requirement, wants an end-to-end autonomous design run, or mentions the design harness, design_next_action, design sessions, or spec-to-board. Requires the eda-agent MCP server connected to a running Altium Designer or EasyEDA Pro; the KiCad backend does not register the design harness.

Autonomous PCB design (eda-agent)

Drive a full spec-to-board design by looping the server-side state machine. The server owns sequencing, gates, and durable state, so you never memorize the workflow: you call design_next_action, do what it says, log the result, and repeat. A weaker model produces a plainer board, never a broken pipeline, because the integrity lives server-side.

Before you start

Confirm the editor is actually answering, with app_ping on Altium or easyeda_ping on EasyEDA. Ping, not app_get_status: status reports that the process exists and that something once called attach, and neither of those proves the bridge replies. If it does not answer, tell the user how to start it; don't guess.
Read design_get_discipline once: the hard rules and the DesignPlan schema. Or call design_autonomy_guide for the full protocol + the 13 stages with their tools and exit gates.

The loop

design_session_start(requirement) opens the durable journal. Keep the returned session_id; every later call takes it. Then design_live_view so the user can watch the board change, and record each decision with its reason before acting on it (design_live_note).
If a project is open or will be modified, checkpoint first so the whole run is revertible in one step: app_checkpoint("before autonomous run") on Altium, easyeda_checkpoint on EasyEDA.
Loop: design_next_action(session_id) and act on status:
- proceed / retry: do the stage using its suggested_tools until the exit_gate is met, then design_session_log(event="stage_result", stage=<stage>, status="ok"). Where the gate names numbers (placement, routing, pours, verification), measure them with pcb_layout_audit and pass the result as data=: the harness checks them and sends the stage back if one fails. If you cannot finish without the user, log status="blocked" with a question and stop.
- blocked: put open_question to the user; when answered, design_session_log(event="resolved", text=<answer>) and continue.
- complete: the 13 stages are done; write the design report with design_session_report and review outputs with the user.
Checkpoint again before each high-risk mutating stage: sch_to_pcb, routing, pours_tuning.
Long engine runs (routing a dense board) can exceed the tool timeout; start them with design_job_start and poll design_job_status / design_job_result.

Bounded retries: a stage that fails 3 times escalates to a human question automatically. Don't loop past it; surface it.

Show full SKILL.md (218 more words)Show less

How the board is laid out

The discipline's "Board layout method" is the standard: floorplan before placement (fixed skeleton, critical corridors, sections, one rectangle per sub-block in signal-flow order), each block laid out to a pattern, the legaliser's moves read rather than accepted, routing in stages (pairs, plane fan-out with dog-bones, buses as a whole, then the rest), and one small checked step at a time. A scattered placement means the method is wrong; no parameter fixes it.

Resuming

A run survives context loss. In a fresh session, call design_session_resume(session_id) (or design_next_action) and pick up from recorded state: the journal, not the chat history, is the source of truth.

Hard constraints (non-negotiable)

Datasheet-first: every device fact fetched and cited from the manufacturer datasheet; never fabricated. Use WebSearch/WebFetch.
NDA isolation: never mine or reference other client designs.
No third-party routing engines or account-gated APIs in the design loop: the in-house router is the only routing engine.
Verify render-and-look, not by score alone; the visual rubric is the shipping bar.
No unverifiable safety tables: ship only sourced/verified values.

Discovering tools

The surface is 350+ tools. Use tool_catalog(category=, maturity=, interaction=, query=) to find the right one without loading every schema; interaction="modal" and "partial" flag tools that need a human or leave work incomplete. Run a discovered tool by name with tool_invoke.

Files

Just SKILL.md in skills/autodesign of salitronic/eda-agent.

Open the folder on GitHubat commit fc97ec8

Compare with similar skills

Autodesign next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Autodesign compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Autodesign this skillsalitronic/eda-agent	238	—	~1.2k	Automated safety check: Pass	Apache-2.0	yesterday
Azsdk Common Pipeline TroubleshootingAzure/azure-sdk-for-android	121	—	~496	Automated safety check: Pass	MIT	4 mo ago
Easyeda Copilotbiosshot/easyeda-copilot	165	—	~2.7k	Automated safety check: Pass	MIT	2 days ago
Azsdk Common Pipeline AnalysisAzure/azure-sdk-tools	134	—	~1.2k	Automated safety check: Pass	MIT	yesterday
MCP Server Builderanthropics/skills	180k	62 repos	~2.3k	Automated safety check: Pass	Apache-2.0	2 days ago
MCP Server BuildershareAI-lab/learn-claude-code	78k	5 repos	~1.2k	Automated safety check: Pass	MIT	9 days ago

Similar skills

Azsdk Common Pipeline Troubleshooting
Azure/azure-sdk-for-android
Official
Diagnose and resolve failures in Azure SDK CI and generation pipelines.
121 GitHub stars~496 tokensUpdated 4 mo ago
Agent WorkflowsAuto-check passed
Easyeda Copilot
biosshot/easyeda-copilot
Create, modify, place, route, or review EasyEDA schematics and PCBs with EasyEDA Copilot, using direct MCP tools when available or the generated standalone CLI skill.
165 GitHub stars~2.7k tokensUpdated 2 days ago
Agent WorkflowsAuto-check passed
Azsdk Common Pipeline Analysis
Azure/azure-sdk-tools
Official
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format.
134 GitHub stars~1.2k tokensUpdated yesterday
Testing & QAAuto-check passed
MCP Server Builder
anthropics/skills
Official
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
180k GitHub starsUsed in 62 repos~2.3k tokens
Agent WorkflowsAuto-check passed
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
78k GitHub starsUsed in 5 repos~1.2k tokens
Agent WorkflowsAuto-check passed
MCP Integration for Plugins
anthropics/claude-plugins-official
Official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
37k GitHub starsUsed in 11 repos~3.1k tokens
Agent WorkflowsAuto-check passed

Works with

Questions about Autodesign

What does Autodesign do?

Drive an autonomous spec-to-board PCB design with the eda-agent MCP server (Altium Designer or EasyEDA Pro). Autodesign is an agent skill from salitronic/eda-agent. Drive an autonomous spec-to-board PCB design with the eda-agent MCP server (Altium Designer or EasyEDA Pro).

When should I use Autodesign?

Autodesign fits situations like: asks to design a board/schematic from a requirement; wants an end-to-end autonomous design run; mentions the design harness; designnextaction.

How do I install Autodesign in Claude Code?

Run `npx skills add salitronic/eda-agent --skill autodesign -a claude-code`. Or copy the skill folder (skills/autodesign in salitronic/eda-agent) into .claude/skills/autodesign in your project. Claude Code loads it when a task matches its description.

How do I install Autodesign in Codex?

Run `npx skills add salitronic/eda-agent --skill autodesign -a codex`. Or copy the skill folder (skills/autodesign in salitronic/eda-agent) into .agents/skills/autodesign in your project. Codex loads it when a task matches its description.

Can I use Autodesign in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add salitronic/eda-agent --skill autodesign -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/autodesign, .gemini/skills/autodesign, .github/skills/autodesign and .opencode/skills/autodesign in your project.

What does Autodesign need to run?

SKILL.md names no scripts, command-line tools or credentials: Autodesign is instructions for the agent only.

Does Autodesign access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Autodesign safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Autodesign use?

Autodesign is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Autodesign use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Autodesign?

Skills that share tags, products or a category with Autodesign: Azsdk Common Pipeline Troubleshooting (Azure/azure-sdk-for-android, 121 stars), Easyeda Copilot (biosshot/easyeda-copilot, 165 stars), Azsdk Common Pipeline Analysis (Azure/azure-sdk-tools, 134 stars) and MCP Server Builder (anthropics/skills, 180k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Autodesign?

salitronic (a GitHub user) maintains it in salitronic/eda-agent, which has 238 GitHub stars. The repository was last updated on October 6, 2026.

Source: salitronic/eda-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Autodesign

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Autonomous PCB design (eda-agent)

Before you start

The loop

How the board is laid out

Resuming

Hard constraints (non-negotiable)

Discovering tools

Files

Compare with similar skills

Similar skills

Azsdk Common Pipeline Troubleshooting

Easyeda Copilot

Azsdk Common Pipeline Analysis

MCP Server Builder

MCP Server Builder

MCP Integration for Plugins

Related

Questions about Autodesign