zephyr-development
Skill28 starsChanged 29 days agoMITView on GitHub
Build and debug Zephyr applications with west, devicetree, Kconfig and versioned workspaces. Use when a request concerns Zephyr board qualifiers, overlays, build failures, runners or RTOS diagnostics.
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
- 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
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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.
- Very specific: line 16
Read workspace and diagnosis.
≈ “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
Zephyr Development
Read the shared embedded contract and keep source/build, device and physical evidence separate.
Record the exact Zephyr revision, frozen west manifest, SDK/toolchain, host, board qualifier, application, overlays and build directory. A PlatformIO Zephyr package and a west workspace can contain different Zephyr releases.
Read workspace and diagnosis. Reproduce with the
existing build manager first. In a west workspace use west manifest --freeze
and inspect west list; neither a board family nor an old board alias is a
verified target. west build -b BOARD APP -d BUILD --pristine=auto configures and
compiles; a pristine build removes generated build state, so use a disposable
build directory. Retain zephyr.dts, .config, ELF/map and the first failing
compiler/linker command. Inspect final generated settings, not only overlays.
For devicetree failures inspect enabled node status, compatible/binding, pinctrl,
chosen nodes and aliases. For missing Kconfig dependencies inspect warnings
and generated .config; never force-select a symbol to silence a warning.
For runtime faults use the matching ELF and fault-forensics; for deadlock,
stack or scheduling evidence use memory-timing-debugging. Distinguish Zephyr
kernel APIs from FreeRTOS primitives.
west flash, west debug, west attach, runner erase and reset can alter or
halt hardware. Inspect the selected runner, probe serial, target voltage and
reset behavior before an authorized session. Do not infer physical operation
from the non-actuating F401 compile fixture. Deliver reproducible command,
effective configuration, root-cause evidence and the next falsifying check.
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.