How do I install the Firmware skill?

Run npx skillmds@latest add baibai2013/firmware in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Firmware safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Firmware?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Firmware free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Firmware?

baibai2013 (@baibai2013) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Firmware by baibai2013 — Agent Skill

Name: Firmware
Author: baibai2013

Firmware

Robot-dog firmware dry-run planning and validation skill for MCU target, motor-control loop, CAN protocol, safety state machine, calibration contract, build manifest, and hardware bring-up gates. Use this skill when the user asks for embedded firmware, motor firmware, FOC loop, CAN frames, calibration, firmware project scaffolding, or safe pre-flash validation.

baibai2013 69ee33c 21 files · 23.0 KB Updated Sep 17, 2026

File contents

firmware

This skill defines a safe firmware dry-run contract for robot-dog prototypes. The MVP validates firmware requirements and emits project manifests, CAN frame specs, and calibration placeholders. It does not compile vendor firmware, flash devices, spin motors, or interact with hardware.

When To Use

Use this skill for:

MCU/firmware project manifest planning.
Motor-control loop and bus-rate sanity checks.
CAN frame and telemetry contract generation.
Safety-state, emergency-stop, undervoltage, overcurrent, and thermal gates.
Calibration manifest requirements before hardware bring-up.

Workflow

Read <project>/firmware_plan.yaml.
Validate target MCU, control loop, bus, safety, and calibration requirements.
Write reports into <project>/reports/ and firmware artifacts into <project>/firmware/.
Return non-zero when required safety/build prerequisites are missing.

Commands

python skills/firmware/scripts/generate_project.py skills/firmware/examples/quadruped_mvp
python skills/firmware/scripts/run_firmware_tests.py skills/firmware/examples/quadruped_mvp

Rules

Never flash, upload, power hardware, or move motors without explicit separate tooling and user confirmation.
Treat missing emergency stop, undervoltage, overcurrent, or calibration as blockers.
Keep this MVP deterministic and hardware-free.
Do not import sibling subskill code. Read files only.

References

references/input-contract.md for firmware_plan.yaml fields.
references/safety-gates.md for blockers.
references/can-contract.md for CAN frame output.
references/output-contract.md for report fields.
references/examples.md for sample project layout.

---name: firmwaredescription: Robot-dog firmware dry-run planning and validation skill for MCU target, motor-control loop, CAN protocol, safety state machine, calibration contract, build manifest, and hardware bring-up gates. Use this skill when the user asks for embedded firmware, motor firmware, FOC loop, CAN frames, calibration, firmware project scaffolding, or safe pre-flash validation.---# firmwareThis skill defines a safe firmware dry-run contract for robot-dog prototypes. TheMVP validates firmware requirements and emits project manifests, CAN frame specs,and calibration placeholders. It does not compile vendor firmware, flash devices,spin motors, or interact with hardware.## When To UseUse this skill for:- MCU/firmware project manifest planning.- Motor-control loop and bus-rate sanity checks.- CAN frame and telemetry contract generation.- Safety-state, emergency-stop, undervoltage, overcurrent, and thermal gates.- Calibration manifest requirements before hardware bring-up.## Workflow1. Read `<project>/firmware_plan.yaml`.2. Validate target MCU, control loop, bus, safety, and calibration requirements.3. Write reports into `<project>/reports/` and firmware artifacts into `<project>/firmware/`.4. Return non-zero when required safety/build prerequisites are missing.## Commands```bashpython skills/firmware/scripts/generate_project.py skills/firmware/examples/quadruped_mvppython skills/firmware/scripts/run_firmware_tests.py skills/firmware/examples/quadruped_mvp```## Rules- Never flash, upload, power hardware, or move motors without explicit separate tooling and user confirmation.- Treat missing emergency stop, undervoltage, overcurrent, or calibration as blockers.- Keep this MVP deterministic and hardware-free.- Do not import sibling subskill code. Read files only.## References- `references/input-contract.md` for `firmware_plan.yaml` fields.- `references/safety-gates.md` for blockers.- `references/can-contract.md` for CAN frame output.- `references/output-contract.md` for report fields.- `references/examples.md` for sample project layout.

Frequently asked questions