niuniubinghero

Embedded Agent Skills — Development skill for Claude Code

Development community

Agent skills (SKILL.md) for embedded software development — build/flash/debug/observe/trace with honest declare-and-degrade capability contracts.

How to install Embedded Agent Skills

This entry records only its repository, not the path inside it, so there is no exact command to give. Open niuniubinghero/embedded-agent-skills and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Embedded Agent Skills does

Agent skills (SKILL.md) for embedded software development — build/flash/debug/observe/trace with honest declare-and-degrade capability contracts. Works with Claude Code, Codex, Qoder and other agents.

Alternatives in Development

Sales Safari — Mine watering holes for product opportunities; observe conversations, sort findings into pain killers vs money 324 ★
Playbook — How to dispatch well — choosing flash vs pro, writing self-contained briefs, parallelism, verifying results, a 116 ★
Little Agent — A lightweight embedded agent framework (similar to Claude Code and OpenAI Codex) 95 ★

README

embedded-agent-skills

Not to be confused with the third-party "embeddedskills" repo — this project is unrelated.

A public, vendor-neutral collection of agent skills for **embedded software developers in every industry**: firmware bring-up, flashing, debugging, observation, and fault analysis — driven by AI coding agents through a strict, honest contract.

The design goal is taming agent hallucination in a domain where a confident wrong answer bricks hardware: every failure is explicit, every unsupported capability is declared, every destructive action is dry-run first, and every "pass" requires a post-condition check.

What is in here

core/ — the contract: profile schema, five capability verbs, envelope, error-code registry, provider interface, and platform-agnostic methodology skills.
platforms/ — vendor packs (STM32 validated first; ESP-IDF probe; others planned).
domains/ — protocol packs (UART/SPI/I2C/CAN/Modbus…) and scenario packs (bring-up, OTA, production test, low-power).
mcp/ — MCP server form (P6; see roadmap below).

The five verbs

`build` · `flash` · `debug` · `observe` · `trace` — packs implement a verb or **declare `unsupported`**; upper layers auto-degrade. Intrusiveness is declared data on providers (`intrusive: none|halt|reset`), and safety-critical targets pin `safety.no_halt: true` so the core refuses halt-class actions. Irreversible operations (option bytes, OTP, full-chip erase) always run two-phase: `prepare` → explicit confirmation → `commit` → mandatory verification.

Status

**v0.1.0** (`docs/VERSION`, changes in `CHANGELOG.md`) — P0 and P1 are complete: the core contract, the `emb` CLI, mock and GCC-Arm reference providers, the three v1 contract documents, five seed knowledge skills, and the verification tiers that prove them. No platform packs yet.

What that version does *not* mean: no real programmer, probe or debugger is wired up, so `flash`/`debug`/`observe`/`trace` are proven at the mo