Best use case
zephyr-rtos is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Specialized skill for Zephyr RTOS development and configuration
Teams using zephyr-rtos should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/zephyr-rtos/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How zephyr-rtos Compares
| Feature / Agent | zephyr-rtos | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Specialized skill for Zephyr RTOS development and configuration
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Zephyr RTOS Skill
## Overview
This skill provides specialized support for Zephyr RTOS development, including device tree configuration, Kconfig management, and integration with Zephyr's extensive subsystems.
## Capabilities
### Build System
- West build system operation and configuration
- CMake integration and customization
- Multi-image builds (MCUboot + app)
- Sysbuild configuration
- Custom board definitions
### Device Tree
- Device tree overlay generation
- Binding creation and modification
- Node property configuration
- Pinctrl and GPIO configuration
- Compatible string management
### Kconfig Management
- Kconfig option configuration
- Fragment file organization
- Configuration dependency analysis
- Board-specific defconfig
- Application-specific prj.conf
### Networking Stack
- TCP/IP stack configuration
- Socket API setup
- Network interface configuration
- MQTT, CoAP, LwM2M protocols
- Network shell commands
### Bluetooth Stack
- Bluetooth LE configuration
- GATT service definition
- Bluetooth Mesh setup
- Connection management
- Advertising configuration
### Power Management
- Power management framework configuration
- Device power states
- System power states
- Policy configuration
### Logging and Shell
- Logging backend configuration
- Log level management
- Shell command registration
- RTT and UART backends
### Secure Boot
- MCUboot integration
- Signed image generation
- Upgrade slot configuration
- Hardware security integration
## Target Processes
- `rtos-integration.js` - Zephyr RTOS setup and integration
- `secure-boot-implementation.js` - MCUboot and secure boot
- `ota-firmware-update.js` - Firmware update with MCUboot
- `low-power-design.js` - Zephyr power management
## Dependencies
- Zephyr SDK
- West meta-tool
- Device tree compiler (dtc)
- CMake and Ninja
## Usage Context
This skill is invoked when tasks require:
- Zephyr project setup and configuration
- Device tree customization
- Networking or Bluetooth stack setup
- Power management implementation
- Secure boot with MCUboot
## Example Configurations
### Basic Project Structure
```
app/
CMakeLists.txt
prj.conf
boards/
my_board.overlay
src/
main.c
```
### Device Tree Overlay
```dts
&i2c0 {
status = "okay";
clock-frequency = <I2C_BITRATE_FAST>;
sensor@48 {
compatible = "ti,tmp102";
reg = <0x48>;
};
};
```
### Kconfig Fragment
```kconfig
CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="My Device"
CONFIG_BT_GATT_DYNAMIC_DB=y
```Related Skills
freertos-integration
Expert skill for FreeRTOS configuration, debugging, and optimization
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.