rfauto
RF/microwave design automation + LLM orchestration: 16 EM/EDA engines behind one interface, 75 parameterized template families, 340 deterministic calculators, 87 calibration anchors; AI agents drive everything via MCP (157 tools) — physics numbers come only from deterministic kernels, never from the…
Install / Use
claude mcp add geer1895 -- npx -y github:geer1895/rfautoIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
AutomationSupported Platforms
Our assessment of rfauto
rfauto scores 87/100 on our quality scale, 1596th of 2,790 Automation skills we index.
Its MCP Server is 24 KB long, well organised into 39 sections with 20 code examples: a thorough specification that gives an agent plenty to work with.
It has 46 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated 5 days ago, so rfauto is actively maintained.
- Our last check on 2026-11-13 found the source still online.
- It is released under GPL-3.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
- Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-11. Automated pattern scan on 2026-11-11. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
rfauto compared with similar skills
All 4 of these similar skills score higher than rfauto; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| rfauto (this skill)by geer1895 | 87 | 46 | 5d ago | MCP Server |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install rfauto?
- Run
claude mcp add geer1895 -- npx -y github:geer1895/rfauto. The install tabs above show the steps for each supported agent. - Which AI agents does rfauto work with?
- It is written for Claude Code, Claude Desktop and Zed, as a MCP Server file. Other agents that read the same format can often use it too.
- Is rfauto safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is GPL-3.0-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is rfauto still maintained?
- The repository was last updated 5 days ago, so rfauto is actively maintained.
Skill content
View source on GitHubrfauto
English | 简体中文
rfauto turns RF/microwave design from "draw, wait for the solver, copy numbers" into one reproducible automated loop. Describe the device you want; it derives first-cut dimensions from closed-form physics, drives whichever solver you have, runs every result through quality gates that catch numerical artifacts, then optimizes the dimensions — and hands you a report where every number carries its provenance. AI assistants can drive all of it over MCP, under one iron rule:
Every physical number (frequency, loss, geometry) is produced by the deterministic kernel or by a solver — never invented by the language model.
Measured counts for this revision (exact; verifiable with scripts/check_numbers.py):
CALCULATOR_REGISTRY 340 (with experimental 341) · TEMPLATE_META 75 ·
EXPECTED_TEMPLATES 75 · ANCHORS 87 · CLI commands 297 (leaves) ·
(166 MCP tools + 10 resources)
Scale numbers: MCP tools 166 (+10 resources) | CLI commands 297 (leaves) | CALCULATOR_REGISTRY 340 [with experimental 341] | device templates 75 | anchors 87
<!-- AUTO-NUMBERS:END -->Contents · Capability map · Quick start · Why trust it · Engine ladder · Architecture · Docs map · Roadmap

1. Capability map (nine domains)
Each domain works on its own; together they form the loop above. Every command below is copy-pasteable.
1.1 Device modeling and synthesis
75 parameterized device templates — dividers, couplers, filters, antennas, transitions, lumped IPD passives. Each template synthesizes first-cut dimensions from closed-form physics and registers the acceptance criteria for that family, so you can tell a real result from a grid artifact. Line widths are never copied from a document: they come from skrf Hammerstad-Jensen synthesis (single source).
rfauto syn mline 50.0 --freq 2.4 --stackup rogers4350b_h0.508
# width: 1.1133 mm eps_eff: 2.8530
rfauto templates list # the 75 families and their parameters
rfauto templates golden-diff # geometry golden regression
A recipe is the input: one YAML file describes frequency, substrate, targets and constraints, and every channel reads the same file.
1.2 Multi-engine simulation
One adapter layer, 16 channels: HFSS, ADS, openEMS, COMSOL, Elmer, NGSolve, Meep, Icepak, Q3D, Palace, KiCad, ngspice, FDTDX (JAX), MMT (analytical mode-matching), QucsatorRF, and a VNA measurement channel. Commercial engines are optional extras; the whole core runs on the built-in fake channel — no license needed to try everything.
rfauto solvers list # registered channels and availability
rfauto run recipes/patch_antenna_v1.yaml --adapter fake
1.3 Optimization and tuning
TPE / CMA-ES / NSGA-II for multi-objective work (Pareto fronts), plus a surrogate route: fit a cheap model on a batch of results, search on the model, and spend expensive solves only where they matter. Batch campaigns carry budget admission, quotas and watchdogs, so they can run unattended overnight.

rfauto tune recipes/wilkinson_pd_v1.yaml --adapter fake --max-trials 40
rfauto sweep recipes/wilkinson_pd_v1.yaml --adapter fake
rfauto campaign plan --config campaign.yaml
1.4 Quality gates
Solvers fail quietly: a coarse mesh shifts the resonance, a wrong port solves to ±0 dB, a truncated pulse pushes |S11| above 1 — and the garbage looks as plausible as the truth. rfauto makes the judgment an explicit gate.

Six gates cover six classes of failure: port semantics (five geometric criteria at model-build time), grid artifacts (energy / convergence / minimum spacing), physics invariants (passivity / reciprocity / symmetry), cross-engine arbitration (a second engine on the same structure), artifact freshness (manifest fingerprint vs files on disk), and anchor drift. A result that misses a gate is reported FAIL with the gate name and the margin — never silently passed.
1.5 Calibration and anchors
87 calibration anchors cover 68 device families (75 templates ship; families
without an anchor say so). Layered by evidence strength: 18 are backed by an
HFSS ↔ openEMS dual-engine comparison, 2 by HFSS/MMT arbitration, 1 by HFSS
self-consistency; 62 are closed-form or quasi-static FD reference anchors (59
closed-form + 3 FD, each with formula source and validity domain on file); the
remaining 4 have no engine comparison and say so — a closed-form anchor is never
dressed up as engine-backed.
Artifact freshness has four states (fresh/stale/legacy/error): an old file
replacing a new run is flagged, and rfauto runs verify exits 1.
rfauto anchors list # values / status / provenance
rfauto anchors validate # check provenance records one by one
rfauto runs verify <run_id> # freshness (stale ⇒ exit code 1)
1.6 Datasets and the lake
Every run drops a self-describing directory: environment fingerprint, recipe snapshot, metrics, figures, Touchstone files, and a manifest recording hashes of all artifacts. Datasets assemble runs into a queryable lake with tiered compaction and batch collection.
runs/20261026_132409_ff7c0bde/
├── meta.json # environment fingerprint (versions, git sha, deps)
├── recipe.snapshot.yaml # the recipe snapshot this run used (replay reads it)
├── manifest.json # SHA256 + size of every artifact (freshness basis)
├── report.md # human-readable report: metrics, gates, verdict
└── results/
├── metrics.json # machine-readable metrics
├── params.s3p # Touchstone (real-engine channels only)
└── figs/ # figures
rfauto runs list
rfauto dataset materialize --help
rfauto lake index
1.7 Remote execution and batch
A machine registry with liveness probes and per-machine mutex: send the heavy work to a compute server and keep only orchestration locally. Remote HFSS runs over gRPC attach; batch jobs launch short-lived processes. Everything is cleaned up on completion (processes killed, scheduled tasks removed, artifacts pulled back) so no orphan holds a license seat.
rfauto remote probe # liveness and version check
rfauto remote status
1.8 AI orchestration (MCP)
166 MCP tools and 10 resources: Claude Desktop, Cursor or your own agent can operate the framework. Agent changes land in a sandbox draft and must pass validation gates before touching the workspace; the agent emits typed tool calls only, and the kernel fills in the physics.
pip install -e ".[mcp]"
python -m rfauto.mcp_server # stdio transport
1.9 Workbench
rfauto ui starts a local review workbench (your data never leaves the machine):
24 views over run history, S-parameters, 3D fields, the template gallery, campaign
boards, calibration, datasets, reports and a microwave toolbox. Command palette
(Ctrl+K), deep links, whole-site zh/EN switch.



Quick start

Requirements: Python 3.10–3.12 (python --version). No commercial tool is
needed — steps 0–6 run entirely license-free in about ten minutes.
Step 0 · Get the code
# A. with git (recommended, easy to update)
git clone https://github.com/geer1895/rfauto && cd rfauto
# B. without git: use Code → Download ZIP on GitHub, or grab
# "Source code (zip)" from the Releases page and unzip it
Step 1 · Install
python -m venv .venv
.venv\Scripts\activate # Linux/macOS: source .venv/bin/activate
pip install -e ".[ui]" # core + browser workbench
rfauto --help # a command table means it works
Steps 2–6 only need the core (pip install -e .); rfauto ui needs the [ui]
extra (starlette/uvicorn); the test suite needs [dev].
Step 2 · Health check
rfauto doctor
Returns a table in a second: Python version, AEDT/ADS detection (marked "not
configured" if absent — the license-free flow is unaffected), cache mode. Add
--janitor --min-free-gb 8 to also list orphan solver processes and enforce a
memory floor — worth doing before long real-engine runs.
Step 3 · First simulation (no license)
rfauto run recipes/wilkinson_pd_v1.yaml --adapter fake
Measured output on the development machine (2.4 GHz Wilkinson divider, Rogers 4350B 0.508 mm):
✓ done run_id: 20261026_132409_ff7c0bde
metrics:
s11_db_max_in_band: -12.4325
s11_db_min_in_band: -16.2978
s21_db_mean_in_band: -3.5887
iso_s23_db_min_in_band: 27.3788
The fake channel is a closed-form analytical model, not an EM solve — its job is to exercise "recipe → run → artifacts → gates" in seconds. Real physics starts at step 7, with the same recipe and the same gates.
Step 4 · Read the artifacts
Each run lands in runs/<timestamp>_<hash>/ (layout in
1.6). Look at report.md (human) and
results/metrics.json (machine), then verify freshness:
rfauto runs verify 20261026_132409_ff7c0bde
fresh means the files on disk still match the closing fingerprint; stale (an
old file replacing a new one) exits 1 and is never silently passed.

Step 5 · Open the workbench
rfauto ui # http://127.0.0.1:8642, loopback only
rfauto ui --port 8643 # use another port if a stale instance holds 8642
The left rail is the workspace: Dashboard, Run History, S-Parameters, Template Gallery, Microwave Tools (341 calculators), Calibration, Datasets… The zh/EN switch sits at the top right.
Step 6 · Tune one round
rfauto tune recipes/wilkinson_pd_v1.yaml --adapter fake --max-trials 40
Measured: 40 trials in about 46 s, cost dropping from 3.64 to 2.55, with the
recommended λ/4 arm 18.00 mm, 70.7 Ω arm width 0.448 mm and 50 Ω feed 1.151 mm
(s11_db_max_in_band improves from −11.46 to −12.45 dB). The Tuning view in
the workbench lets you watch it trial by trial.
Step 7 · Switch to a real engine
pip install -e ".[hfss]" # pyaedt; requires AEDT 2025 R1
# or build openEMS (free) following docs/openems_build_guide.md
Replace --adapter fake with --adapter openems or --adapter hfss — the recipe
and the gates do not change. Before unattended HFSS runs, read
[docs/una
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
