pico-sdk-development
Skill28 starsChanged 29 days agoMITView on GitHub
Build and debug native Raspberry Pi Pico SDK applications with CMake, RP2040/RP2350 targets, PIO and SWD. Use when requests concern Pico SDK configuration, linker output, multicore/PIO or native SDK migration; distinguish Arduino-Pico.
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-cli-skillSkill
- 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
- 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
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Read the shared embedded contract and keep source/build, device and physical evidence separate.
- Distinctive: line 12
Read native SDK workflow. Confirm RP2040 versus RP2350, exact board, flash population, SDK revision, compiler and CMake cache.
- Very specific: line 17
Use an out-of-source build with the repository's PICO_BOARD, PICO_PLATFORM, SDK path and toolchain.
≈ “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
Pico SDK Development
Read the shared embedded contract and keep source/build, device and physical evidence separate.
Read native SDK workflow. Confirm RP2040 versus RP2350, exact board, flash population, SDK revision, compiler and CMake cache. Arduino-Pico is a different framework; its core version is not the Pico SDK version. Preserve a requested CPU architecture and board profile.
Use an out-of-source build with the repository's PICO_BOARD, PICO_PLATFORM,
SDK path and toolchain. Avoid changing a populated build directory to another
chip or SDK; create a fresh build directory. Build the ELF before producing or
copying a UF2. Keep map/ELF and SDK revision together.
For PIO inspect instruction count, wrap points, clock divider, FIFO direction,
DREQ, pin mapping and DMA ownership; a legal instruction program can still wait
forever on the wrong pin/IRQ. For multicore code identify shared-data ownership,
locks and flash/XIP assumptions. SDK multicore is not automatically FreeRTOS.
Route runtime scheduling to memory-timing-debugging and SWD to
probe-debugging. USB CDC and UART stdio are distinct transports.
BOOTSEL/UF2 copying, picotool load, probe program and flash write hardware.
Build-only work ends at artifacts. Deliver the exact CMake configuration,
resolved SDK/compiler, compile result and target checks still required.
See platform coverage for the exact tested combination. A source procedure is not a claim that every target was tested.
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.