Skip to content
Back to skills

Zephyr Rtos

ASecurity

Specialized skill for Zephyr RTOS development and configuration

  • 1,760 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 2, 2026
ai-agentsgoshellbashnodeapibackendsecurity

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 2, 2026

npx -y skills add a5c-ai/babysitter --skill zephyr-rtos --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Zephyr Rtos?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Zephyr Rtos
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/a5c-ai-zephyr-rtos-babysitter/badge)](https://www.skillsdirectory.com/skills/a5c-ai-zephyr-rtos-babysitter)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: zephyr-rtos
description: Specialized skill for Zephyr RTOS development and configuration
category: RTOS
allowed-tools:
  - Bash
  - Read
  - Write
  - Edit
  - Glob
  - Grep
graph:
  domains: [domain:embedded-systems]
  specializations: [specialization:embedded-systems]
  skillAreas: [skill-area:rtos-programming, skill-area:firmware-development, skill-area:real-time-os]
  roles: [role:embedded-engineer]
---

# 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
```

Files in this skill

  • README.md852 B
  • SKILL.md2.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…