RuView Hardware Setup
ruvnet/RuView
Brings a RuView CSI sensing node online by building ESP32-S3 or ESP32-C6 firmware, flashing the board, provisioning WiFi and checking the serial output.
Build PlatformIO firmware and inspect real compilation, memory, artifacts and pin plans without implicitly accessing hardware.
Install Firmware
$ npx skills add autonomous-ai/openharness --skill firmware -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install autonomous-ai/openharness firmware --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/store/agents/firmware-studio/skills/firmware .claude/skills/firmware && rm -rf skills-srcUse ~/.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/
Install the "firmware" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/firmware-studio/skills/firmware into .claude/skills/firmware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firmware", 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 install https://github.com/autonomous-ai/openharness/tree/main/store/agents/firmware-studio/skills/firmwareType 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.
$ npx skills add autonomous-ai/openharness --skill firmware -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install autonomous-ai/openharness firmware --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/store/agents/firmware-studio/skills/firmware .agents/skills/firmware && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "firmware" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/firmware-studio/skills/firmware into .agents/skills/firmware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firmware", 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.
$ npx skills add autonomous-ai/openharness --skill firmware -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install autonomous-ai/openharness firmware --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/store/agents/firmware-studio/skills/firmware .cursor/skills/firmware && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "firmware" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/firmware-studio/skills/firmware into .cursor/skills/firmware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firmware", 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 https://github.com/autonomous-ai/openharness.git --path store/agents/firmware-studio/skills/firmware--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add autonomous-ai/openharness --skill firmware -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install autonomous-ai/openharness firmware --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/store/agents/firmware-studio/skills/firmware .gemini/skills/firmware && rm -rf skills-srcUse ~/.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/
Install the "firmware" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/firmware-studio/skills/firmware into .gemini/skills/firmware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firmware", 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.
$ gh skill install autonomous-ai/openharness firmwareInstalls 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).
$ npx skills add autonomous-ai/openharness --skill firmware -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .github/skills && cp -r skills-src/store/agents/firmware-studio/skills/firmware .github/skills/firmware && rm -rf skills-srcUse ~/.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/
Install the "firmware" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/firmware-studio/skills/firmware into .github/skills/firmware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firmware", 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.
$ npx skills add autonomous-ai/openharness --skill firmware -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install autonomous-ai/openharness firmware --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/store/agents/firmware-studio/skills/firmware .opencode/skills/firmware && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "firmware" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/firmware-studio/skills/firmware into .opencode/skills/firmware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "firmware", 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
firmware- GitHub stars
- 1.1k
- Token cost
- ~583 tokens
- SKILL.md length
- 277 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 100
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build PlatformIO firmware and inspect real compilation, memory, artifacts and pin plans without implicitly accessing hardware.
- Tasks that involve Embedded systems
- Runs Shell and JavaScript scripts from its folder; calls sh
What it does
Firmware is an agent skill from autonomous-ai/openharness. Build PlatformIO firmware and inspect real compilation, memory, artifacts and pin plans without implicitly accessing hardware.
Its SKILL.md is about 580 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/build-firmware.sh`).
It sits in Development, covering Embedded systems. It works with ESP32. The repository describes itself as: The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across… The licence is MIT.
When your agent uses it
- Tasks that involve Embedded systems
Example prompts
- “/firmware”
Requirements
- Node.js
- A Bash shell
What it can do on your machine
Read from SKILL.md and the folder at commit 50da5db. 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
Ships 3 files in scripts/ (Shell and JavaScript), which the agent can run.
Shell commands in SKILL.md call:
sh
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
Firmware loads about 583 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 277 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from autonomous-ai/openharness at commit 50da5db, republished under its MIT licence (© autonomous-ai). 277 words, ~583 tokens.
Download SKILL.mdSave it as
.claude/skills/firmware/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- firmware
- description
- Build PlatformIO firmware and inspect real compilation, memory, artifacts and pin plans without implicitly accessing hardware.
Firmware Studio
platformio.ini selects environments, platform, board and framework. Pin platform and library
versions for reproducibility; the starter uses espressif32@6.10.0 with Arduino. Arduino code is C++:
use src/main.cpp. Document a board's exact variant before choosing pins or peripherals.
sh "$FIRMWARE_SKILLS/firmware/scripts/build-firmware.sh"
sh "$FIRMWARE_SKILLS/firmware/scripts/build-firmware.sh" esp32devThe helper selects the requested environment, first default_envs entry, or first [env:name].
It runs pio run --project-dir ... -e ... exactly once, not a second compile to read sizes.
PIO_BIN can select an explicit binary; otherwise PATH or the package's PlatformIO venv is used.
Node 20+ can come from the machine or Harness's managed runtime.
Outputs: build-status.html, .harness/build.json, .harness/build.log and copied artifacts under
out/. Missing memory lines display as unavailable, not fabricated zeroes. RAM is the compiler's
static allocation, not a runtime peak. Flash is the selected build partition budget, not necessarily
the chip's total flash capacity. Advanced inherited INI values remain source text in the dashboard;
the compiler log is authoritative about the resolved target.
pins.json contains {"pins":[{"pin":"GPIO 2","role":"LED","direction":"Output","note":"..."}]}
and an optional top-level note. It documents intent only. The pictured board is conceptual.
Review the exact board documentation for input-only pins, boot straps, voltage and current limits.
A failed command, missing binary or invalid pin plan clears readiness and publishes a failure page.
Read the actual log and fix the cause, then rebuild. Inspect dashboard tabs, log filtering and
artifact downloads in the shared Web Viewer. proof.json includes a default tab-interaction recipe.
Device boundary
Compile first. pio run -t upload, -t erase, debugger connections and serial access are separate
real-device steps requiring the user's explicit authorization. A requested build does not authorize
any of them. Do not claim the firmware works on hardware until an actual approved test establishes it.
© autonomous-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in store/agents/firmware-studio/skills/firmware of autonomous-ai/openharness.
- SKILL.md
- scripts/build-firmware.sh
- scripts/build.mjs
- scripts/dashboard.html
Open the folder on GitHubat commit 50da5db
Compare with similar skills
Firmware 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Firmware this skillautonomous-ai/openharness | 1.1k | — | ~583 | Automated safety check: Pass | MIT | |
| RuView Hardware Setupruvnet/RuView | 97k | — | ~1.8k | Automated safety check: Notes | MIT | |
| Esp32 Firmware Engineeralxv2016/folloup-sticky | 116 | 1 repos | ~3.8k | Automated safety check: Pass | GPL-3.0 | |
| RuView mmWave Radar Setupruvnet/RuView | 97k | — | ~907 | Automated safety check: Notes | MIT | |
| Embedded DebugFastLED/FastLED | 7.5k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Auto EmbeddedDunCanYounG-1/MICU-auto-embedded | 253 | — | ~1.6k | Automated safety check: Pass | CC-BY-NC-4.0 |
Similar skills
Esp32 Firmware Engineer
alxv2016/folloup-sticky
ESP32 firmware engineering for ESP-IDF projects. An agent skill from alxv2016/folloup-sticky.
RuView mmWave Radar Setup
ruvnet/RuView
Sets up and runs 60 GHz and 24 GHz mmWave radar sensing on ESP32 boards in RuView, alone or fused with WiFi CSI.
Embedded Debug
FastLED/FastLED
Firmware crash analysis, stack trace decoder, and register dump interpreter for ESP32/ARM/AVR platforms.
Auto Embedded
DunCanYounG-1/MICU-auto-embedded
全平台嵌入式 AI 开发框架（对标 Trellis）：把 RIPER-5 五阶段协议 + 四文件记忆 + 分层架构门禁 + Scout/Builder/Verifier 多 Agent + 24 个工具调用技能（build/flash/debug/serial/can/modbus/visa/static/memory/rtos/scons），做成『装进工程、项目级 hook…
Embedded Cpp14 Misra
BlueAndi/Pixelix
A skill your agent uses when writing, reviewing, or refactoring C/C++ firmware code in this repository (src/, lib/, test/) — creating or editing .h/.hpp/.cpp files, applying MISRA-oriented and…
More from autonomous-ai/openharness
All 100 skills in this repoG-code Slicer Tool
autonomous-ai/openharness
Slices 3D mesh files into printer-profiled plain G-code through real slicer CLIs, with backend discovery, input inspection, dry runs and static validation.
Home Assistant Automation Builder
autonomous-ai/openharness
Turns a home-automation request into standard, testable automations.yaml, run against Home Assistant Core's real triggers and verified with its own trace tool.
Score Music Composer
autonomous-ai/openharness
Turns a musical brief into LilyPond concert-pitch music, checked parts for each instrument and a playable practice pack.
OrcaSlicer 3MF and G-code Workflow
autonomous-ai/openharness
Turns an STL and explicit printer and material requirements into compared OrcaSlicer plans, an editable 3MF project, checked G-code and a portable handoff.
Sheets and Docs Report Builder
autonomous-ai/openharness
Builds an editable DOCX report, a formula-driven XLSX workbook and a fresh LibreOffice PDF preview from one structured source file, then checks them together.
Bambu Labs
autonomous-ai/openharness
Dry-run, upload, and cautiously initiate local Bambu Lab print jobs from validated plain .gcode, using Bambu LAN FTPS/MQTT handoffs.
Related
Works with
Categories
Questions about Firmware
What does Firmware do?
Build PlatformIO firmware and inspect real compilation, memory, artifacts and pin plans without implicitly accessing hardware. Firmware is an agent skill from autonomous-ai/openharness. Build PlatformIO firmware and inspect real compilation, memory, artifacts and pin plans without implicitly accessing hardware.
When should I use Firmware?
Firmware fits situations like: tasks that involve Embedded systems.
How do I install Firmware in Claude Code?
Run `npx skills add autonomous-ai/openharness --skill firmware -a claude-code`. Or copy the skill folder (store/agents/firmware-studio/skills/firmware in autonomous-ai/openharness) into .claude/skills/firmware in your project. Claude Code loads it when a task matches its description.
How do I install Firmware in Codex?
Run `npx skills add autonomous-ai/openharness --skill firmware -a codex`. Or copy the skill folder (store/agents/firmware-studio/skills/firmware in autonomous-ai/openharness) into .agents/skills/firmware in your project. Codex loads it when a task matches its description.
Can I use Firmware 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 autonomous-ai/openharness --skill firmware -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/firmware, .gemini/skills/firmware, .github/skills/firmware and .opencode/skills/firmware in your project.
What does Firmware need to run?
Going by SKILL.md and its folder, Firmware needs a shell and JavaScript for the scripts in its folder and the command-line tools its instructions call (sh). Our summary lists: Node.js; A Bash shell.
Does Firmware 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 Firmware 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Firmware use?
Firmware is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Firmware use?
About 583 tokens (SKILL.md is roughly 2.3k 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 Firmware?
Skills that share tags, products or a category with Firmware: RuView Hardware Setup (ruvnet/RuView, 97k stars), Esp32 Firmware Engineer (alxv2016/folloup-sticky, 116 stars), RuView mmWave Radar Setup (ruvnet/RuView, 97k stars) and Embedded Debug (FastLED/FastLED, 7.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Firmware?
autonomous-ai (a GitHub organization) maintains it in autonomous-ai/openharness, which has 1,149 GitHub stars. The repository holds 100 skills in this directory. The repository was last updated on October 8, 2026.
Source: autonomous-ai/openharness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.