Arduino Firmware Building

Use this skill when the user wants to design, build, upload and test firmware for any Arduino-compatible board end to end with arduino-cli: identifies the board and FQBN via cli search, requires user-provided board/library documentation, validates requirements, writes plan and comprehensive test spec (including edge cases, boundary limits, negative inputs, and fault resilience), stops for user review & approval, implements functional code and test cases via two parallel subagents followed by a third integration & compilation subagent, uploads with user-assisted bootloader/reset steps, captures

8 stars 4 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add nguyentoanthang/arduino-firmware-building --skill arduino-firmware-building

Manual install

git clone --depth 1 https://github.com/nguyentoanthang/arduino-firmware-building.git /tmp/arduino-firmware-building
mkdir -p ~/.claude/skills
cp -r /tmp/arduino-firmware-building/. ~/.claude/skills/arduino-firmware-building

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Arduino Firmware Building

Autonomous build / flash / test loop using `arduino-cli`, serial logs and a human assistant for steps the agent cannot do. The skill is completely board-agnostic: everything board- or library-specific comes strictly from user-provided documentation, never from assumptions. **Input requirement:** the user must provide a documentation folder (or specify its path) containing the board specification (pins, memory, peripherals, upload/bootloader procedure, board options) and library API documentation. **Sketch folder:** when the skill is invoked, create a new sketch folder in the current working directory (a short snake_case name derived from the request, not already existing; the main `.ino` must have the same name as the folder) and work only inside it, unless the user names another location.

`<skill_dir>` = the folder containing this SKILL.md.

## Phase 0: Environment check and board identification (once)
1. **Toolchain check and board identification:**
   - Check `arduino-cli version` and installed cores (`arduino-cli core list`).
   - **Board Name & FQBN Search:**
     - If the user did not provide a specific board name in their request, ask them for the board name.
     - Run `arduino-cli board search <name provided by user>` to search the board package index. The output displays the matching **Board Name**, **FQBN** (Fully Qualified Board Name), and **Platform ID**.

Read the full skill on GitHub

Details

Skill name: arduino-firmware-building
Repository: nguyentoanthang/arduino-firmware-building
Repo updated: 24 October 2026

FAQ

What does the Arduino Firmware Building skill do?

How do I install the Arduino Firmware Building skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add nguyentoanthang/arduino-firmware-building --skill arduino-firmware-building. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Arduino Firmware Building popular?

It lives in nguyentoanthang/arduino-firmware-building, which has 8 GitHub stars and 4 forks.

Related skills

Universal Checkout

zincio/skills

Discover, buy, track, and return real products from Amazon, Walmart, Target and almost any other US online retailer through the Zinc API (zinc.com). Needs no account to begin — the agent mints its own test key, then earns a live key and a $5 starter credit once its operator approves it. Pay from a pre-funded wallet, per request over MPP or x402, or with a Stripe Link card.

Testing & QAIn 1 list

Jest

anivar/jest-skill

Jest best practices, patterns, and API guidance for JavaScript/TypeScript testing. Covers mock design, async testing, matchers, timer mocks, snapshots, module mocking, configuration, and CI optimization. Baseline: jest ^30.5.2. Triggers on: jest imports, describe, it, test, expect, jest.fn, jest.mock, jest.spyOn, mentions of "jest", "unit test", "test suite", or "mock".

Testing & QA

Dpia Generator

wnallen/dpia-generator

Use whenever the user wants to run, draft, or stress-test a Data Protection Impact Assessment or any jurisdiction's equivalent for a new or modified processing. Triggers: "run a DPIA on", "assess privacy risk for", "is this Article 35 / high risk?", "need a Colorado data protection assessment / LGPD RIPD / PIPL PIPIA / Law 25 PIA?", any new-processing description (tool, vendor, AI feature, monitoring) with a privacy-risk question, or a pasted vendor page with a GDPR/ICO/CNIL/EDPB/CPPA/ANPD question. Also "index our privacy notice" — a portable notice profile later runs check for policy drift.

Testing & QA

Healthsim

mark64oswald/healthsim-workspace

HealthSim generates realistic synthetic healthcare data for testing EMR systems, claims processing, pharmacy benefits, and analytics. Use for ANY request involving: (1) synthetic patients, clinical data, or medical records, (2) healthcare claims, billing, or adjudication, (3) pharmacy prescriptions, formularies, or drug utilization, (4) HL7v2, FHIR, X12, or NCPDP formatted output, (5) healthcare testing scenarios or sample data generation.

Testing & QA

Autoreg

Ikhdev1/autoreg-agent-skill

Build and run automated service registrations end to end: recon a signup flow, generate an adapter, drive real Chromium/Gecko with a persistent identity, read email OTP codes, solve or inject CAPTCHA tokens, route through proxies, and verify accounts. Use this skill whenever the user asks to auto-register or mass register on a service, create accounts, automate signup/registration, bypass browser fingerprint checks, wire temporary mail or SMS, or turn a manual signup flow into a repeatable script — even if they do not say "autoreg". Also use it for QA/test-account provisioning and for debuggin

Testing & QA

Forge

ikennaokpala/forge

Autonomous quality engineering swarm that forges production-ready code through continuous behavioral verification, exhaustive E2E testing, and self-healing fix loops. Combines DDD+ADR+TDD methodology with BDD/Gherkin specifications, 7 quality gates, defect prediction, chaos testing, and cross-context dependency awareness. Architecture-agnostic - works with monoliths, microservices, modular monoliths, and any bounded-context topology.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.