How do I install the Embedded Rtos skill?

Run npx skillmds@latest add claude-dev-suite/embedded-rtos in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Embedded Rtos safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Embedded Rtos?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Embedded Rtos free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Embedded Rtos?

claude-dev-suite (@claude-dev-suite) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Embedded Rtos by claude-dev-suite — Agent Skill

Name: Embedded Rtos
Rating: 4.5 (4 reviews)
Author: claude-dev-suite

Embedded Rtos

Embedded, firmware, and real-time systems architecture: bare-metal vs RTOS (FreeRTOS/Zephyr), real-time scheduling (RMS/EDF), WCET and schedulability, priority inversion, interrupt latency, memory/energy budgets, MMU-less design. USE WHEN: designing firmware/embedded/IoT/MCU systems, real-time deadlines, "RTOS", "FreeRTOS", "Zephyr", "bare-metal", "WCET", "hard real-time", "priority inversion", "interrupt latency", "deadline", microcontroller architecture. DO NOT USE FOR: general OS/kernel design (use `os-kernel-architecture`); cloud/server perf (use `hardware-aware-design`); app code (use language skills).

claude-dev-suite Updated Sep 8, 2026 28 repo stars

File contents

Embedded / Firmware / RTOS Architecture

Bare-metal vs RTOS vs GPOS — the first decision

Option	When	Cost
Bare-metal (superloop + ISRs)	Tiny MCU, few tasks, hard determinism	No task abstraction; hand-rolled scheduling
RTOS (FreeRTOS, Zephyr, ThreadX)	Many concurrent tasks, deadlines, drivers	Footprint (KBs), scheduling overhead
GPOS w/ RT patch (Linux PREEMPT_RT)	Rich connectivity + soft/firm RT	MBs RAM, MMU, bounded-but-larger latency

Real-time scheduling & schedulability

Hard vs soft vs firm real-time: missing a hard deadline = system failure.
RMS (rate-monotonic, fixed priority): schedulable if Σ(Cᵢ/Tᵢ) ≤ n(2^(1/n)−1).
EDF (earliest-deadline-first, dynamic): optimal, schedulable up to 100% CPU, but harder to reason about overload.
WCET (worst-case execution time) is the input everything depends on — caches, branch prediction, DMA contention make it hard; measure + analyze.
Priority inversion → use priority inheritance or priority ceiling on mutexes (the Mars Pathfinder bug). Avoid unbounded blocking.

Architecture constraints that dominate

Memory: often no MMU → no virtual memory, no process isolation; static allocation preferred (no heap fragmentation); stack sizing per task.
Interrupt latency: keep ISRs short (top-half), defer to tasks; measure worst-case disable-interrupt windows.
Power: tickless idle, sleep states, peripheral clock gating, wake sources; energy-per-inference for edge AI (see ai-systems/edge).
Determinism over throughput: avoid dynamic allocation, unbounded loops, and non-deterministic libraries on hot paths.

When to recommend what

Hard deadlines + tiny MCU → bare-metal or small RTOS, RMS/EDF, static alloc.
Connectivity + soft RT → Zephyr or Linux PREEMPT_RT.
Safety-critical (ISO 26262 / DO-178C / IEC 62304) → certified RTOS, redundancy, formal/coverage analysis (pairs with a safety-critical skill when present).

---name: embedded-rtosdescription: Embedded, firmware, and real-time systems architecture: bare-metal vs RTOS (FreeRTOS/Zephyr), real-time scheduling (RMS/EDF), WCET and schedulability, priority inversion, interrupt latency, memory/energy budgets, MMU-less design. USE WHEN: designing firmware/embedded/IoT/MCU systems, real-time deadlines, "RTOS", "FreeRTOS", "Zephyr", "bare-metal", "WCET", "hard real-time", "priority inversion", "interrupt latency", "deadline", microcontroller architecture. DO NOT USE FOR: general OS/kernel design (use `os-kernel-architecture`); cloud/server perf (use `hardware-aware-design`); app code (use language skills).---# Embedded / Firmware / RTOS Architecture## Bare-metal vs RTOS vs GPOS — the first decision| Option | When | Cost ||---|---|---|| **Bare-metal (superloop + ISRs)** | Tiny MCU, few tasks, hard determinism | No task abstraction; hand-rolled scheduling || **RTOS (FreeRTOS, Zephyr, ThreadX)** | Many concurrent tasks, deadlines, drivers | Footprint (KBs), scheduling overhead || **GPOS w/ RT patch (Linux PREEMPT_RT)** | Rich connectivity + soft/firm RT | MBs RAM, MMU, bounded-but-larger latency |## Real-time scheduling & schedulability- **Hard vs soft vs firm** real-time: missing a hard deadline = system failure.- **RMS** (rate-monotonic, fixed priority): schedulable if Σ(Cᵢ/Tᵢ) ≤ n(2^(1/n)−1).- **EDF** (earliest-deadline-first, dynamic): optimal, schedulable up to 100% CPU, but harder to reason about overload.- **WCET** (worst-case execution time) is the input everything depends on — caches, branch prediction, DMA contention make it hard; measure + analyze.- **Priority inversion** → use priority inheritance or priority ceiling on mutexes (the Mars Pathfinder bug). Avoid unbounded blocking.## Architecture constraints that dominate- **Memory**: often no MMU → no virtual memory, no process isolation; static allocation preferred (no heap fragmentation); stack sizing per task.- **Interrupt latency**: keep ISRs short (top-half), defer to tasks; measure worst-case disable-interrupt windows.- **Power**: tickless idle, sleep states, peripheral clock gating, wake sources; energy-per-inference for edge AI (see `ai-systems`/edge).- **Determinism over throughput**: avoid dynamic allocation, unbounded loops, and non-deterministic libraries on hot paths.## When to recommend what- Hard deadlines + tiny MCU → bare-metal or small RTOS, RMS/EDF, static alloc.- Connectivity + soft RT → Zephyr or Linux PREEMPT_RT.- Safety-critical (ISO 26262 / DO-178C / IEC 62304) → certified RTOS, redundancy, formal/coverage analysis (pairs with a safety-critical skill when present).

Frequently asked questions