agentleFS
wedsamuel1230wedsamuel1230/embedded-engineering-skills/skills/arduino-cli-skill/SKILL.md

arduino-cli-skill

Skill28 starsChanged 29 days agoMITView on GitHub

Use when users need Arduino CLI commands for board discovery, library installation, compilation, upload, or serial-port troubleshooting on Windows, macOS, or Linux. Use it as the CLI branch of a broader workflow when the project also involves Arduino IDE, PlatformIO, vendor tools, hardware, power, or deployment.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check rules/common-pitfalls.md before suggesting upload or compile fixes.

    line 24
  2. Very specific:

    If the target is Uno R4 family and the problem touches WiFi, firmware bridge, or OTA-related setup, open …

    line 25
  3. Very specific:

    Prefer arduino-cli JSON output when the result will be parsed or reused.

    line 27
  4. Distinctive:

    Prefer command output over remembered defaults when troubleshooting.

    line 51
  5. Distinctive:

    Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, …

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Arduino CLI Skill

Provide cross-platform arduino-cli workflows and command references.

Resources

  • references/commands.md - board, core, library, compile, and upload commands
  • references/serial-ports.md - OS-specific serial port discovery
  • rules/common-pitfalls.md - common command mistakes and recovery guidance
  • examples/README.md - runnable command sequences
  • ../../docs/board-support/uno-r4-family.md - Uno R4 Minima and Uno R4 WiFi support notes

Workflow

  1. Identify the user's platform and target board.
  2. Open references/serial-ports.md if the task depends on port discovery.
  3. Open references/commands.md for the exact command family you need.
  4. Check rules/common-pitfalls.md before suggesting upload or compile fixes.
  5. If the target is Uno R4 family and the problem touches WiFi, firmware bridge, or OTA-related setup, open ../../docs/board-support/uno-r4-family.md.
  6. Prefer arduino-cli JSON output when the result will be parsed or reused.

Compatibility And Proof Boundary

Record arduino-cli version, the core/index version, FQBN, libraries, host OS, and port before changing commands. Check library architecture support and board package compatibility. A successful compile is build proof only; an accepted upload is upload proof and does not establish hardware or system success. For IDE, PlatformIO, or vendor-specific commands, route to the appropriate branch instead of silently translating them.

Quick Start

arduino-cli board list
arduino-cli core list
arduino-cli compile --fqbn arduino:avr:uno path/to/sketch
arduino-cli upload -p /dev/ttyACM0 --fqbn arduino:avr:uno path/to/sketch

Verification

  • Confirm the fqbn matches the target board.
  • Confirm the selected serial port exists before upload.
  • Prefer command output over remembered defaults when troubleshooting.

See references/commands.md and references/serial-ports.md for detailed examples.

Shared Output Contract

Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, known limitations, and recovery/security notes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.