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
- wedsamuel1230/arduino-skillsword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- wedsamuel1230/arduino-skills★ 28100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/arduino-skills.mdcCursor rule
- cli-creatorSkill
- plugin-creatorSkill
- skill-creatorSkill
- arduino-code-generatorSkill
- arduino-project-builderSkill
- arduino-serial-monitorSkill
- arduino-workflow-routerSkill
- battery-selectorSkill
- board-selectionSkill
- board-supportSkill
- bom-generatorSkill
- boot-flash-recoverySkill
- bus-debuggingSkill
- circuit-debuggerSkill
- code-review-facilitatorSkill
- datasheet-interpreterSkill
- embedded-build-workflowSkill
- embedded-project-loopSkill
- enclosure-designerSkill
- error-message-explainerSkill
- fault-forensicsSkill
- field-power-and-connectivity-triagerSkill
- freertos-patternsSkill
- hardware-tddSkill
- i2c-bringup-diagnosticianSkill
- library-selectionSkill
- memory-budgetingSkill
- memory-timing-debuggingSkill
- mermaid-diagram-generatorSkill
- micropython-developmentSkill
- non-blocking-patternsSkill
- ota-deployment-guardianSkill
- pico-sdk-developmentSkill
- pin-assignmentSkill
- power-budget-calculatorSkill
- probe-debuggingSkill
- readme-generatorSkill
- realtime-control-designSkill
- sensor-calibration-workbenchSkill
- sensor-signal-filteringSkill
- stm32-developmentSkill
- usb-debuggingSkill
- wireless-telemetrySkill
- wiring-safety-checkSkill
- zephyr-developmentSkill
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
- Very specific: line 24
Check rules/common-pitfalls.md before suggesting upload or compile fixes.
- Very specific: line 25
If the target is Uno R4 family and the problem touches WiFi, firmware bridge, or OTA-related setup, open …
- Very specific: line 27
Prefer arduino-cli JSON output when the result will be parsed or reused.
- Distinctive: line 51
Prefer command output over remembered defaults when troubleshooting.
- Distinctive: line 57
Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, …
≈ “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.
Files
Arduino CLI Skill
Provide cross-platform arduino-cli workflows and command references.
Resources
references/commands.md- board, core, library, compile, and upload commandsreferences/serial-ports.md- OS-specific serial port discoveryrules/common-pitfalls.md- common command mistakes and recovery guidanceexamples/README.md- runnable command sequences../../docs/board-support/uno-r4-family.md- Uno R4 Minima and Uno R4 WiFi support notes
Workflow
- Identify the user's platform and target board.
- Open
references/serial-ports.mdif the task depends on port discovery. - Open
references/commands.mdfor the exact command family you need. - Check
rules/common-pitfalls.mdbefore suggesting upload or compile fixes. - 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. - Prefer
arduino-cliJSON 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/sketchVerification
- Confirm the
fqbnmatches 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.
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
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.

