- Home
- Skills
- Code Quality & Review
- Embedded Firmware Development
More screenshots
Works with the AI Agents you already use
Embedded Firmware Development
Write and review embedded C firmware that survives the hardware: FreeRTOS synchronization, ISR discipline, lifecycle cleanup, storage integrity, and sensor state machines.
$5
Embedded Firmware Development
Example session with this skill installed
Review this valve-controller module before it ships: a task drives a solenoid over PWM, a UART ISR receives commands, and config is saved to internal flash whenever a command changes it. It passed bench testing but a field unit stopped responding to the first command after a UART error.
- Read your context and instructions
- Compiled the embedded firmware development
PROTOCOL WALK
- Lifecycle map — init, start, stop, error recovery. The stop path exists; the recovery path was never audited. That is where this review expects to find the field bug.
- Resource audit — config is written to flash on every UART command. At field command rates that is thousands of writes a day against a 10k-cycle sector: the store wears out in weeks. Finding 1: batch config writes and commit on change-settle, not per command.
- Synchronization audit — the PWM duty value shared between the control task and the command handler is guarded by a binary semaphore taken with an infinite wait. Finding 2: no priority inheritance, so a low-priority holder stalls the control task, and a wedged holder hangs it forever. Convert to a mutex with a 50 ms timeout.
- ISR audit — the UART ISR formats a log string before queueing it. Finding 3: unbounded work in the hot path. Latch the byte, notify the task, format there.
- Lifecycle audit —
cmd_pendingis cleared in stop and init but not in the error-recovery path. Finding 4: after a UART framing error, recovery inherits a stuck pending flag and the next start ignores the first command. That is the reported field symptom, on exactly one trigger path.
VERDICT — Fail against the pre-delivery quality gate. Four findings, ordered by consequence: stale flag first, flash wear second, then the semaphore and ISR findings. Each fix is one line to one function; re-review runs the stale-flag audit across all four lifecycle paths before this module ships.
Connects securely to your tools. The creator never sees your data.
About this skill
A working method for embedded C firmware, organized around the failures that actually brick devices, drain batteries, and corrupt storage in the field. It starts with the resource model — fixed stacks, a hostile heap, flash that wears out, power that can vanish mid-operation — then enforces a seven-step protocol for writing or reviewing any module: map the lifecycle paths first, audit resources, audit synchronization against a primitive-selection table (mutex for exclusion, semaphore for signaling, queue for data, never a binary semaphore standing in for a mutex), audit every ISR against a non-negotiable contract (capture, clear, defer — nothing else), and audit storage writes so at least one valid copy survives any interruption. The highest-yield section covers the stale-flag bug class: async flags like pending, busy, and data_ready that survive a stop, reset, or error-recovery path and silently block the next operation, with correct-vs-broken code side by side. Sensor drivers are treated as the state machines they are, including the error transitions most drivers omit. A worked example walks a pressure-sensor driver from field symptom ("dead after stop/start") to root cause, and the skill ships with a stale-flag audit checklist, a defect triage table, and a pre-delivery quality gate that decides pass or fail in writing.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.
- It reviews and directs; it cannot run your hardware — stack high-water marks, timing, and power-loss behavior still need bench confirmation.
- Examples are C and FreeRTOS-flavored; other RTOS APIs map closely but are not spelled out.
- It does not cover schematic or PCB-level issues, bootloader signing chains, or safety-certification processes.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
Permissions
No special permissions declared or detected