Rtos
Use when the user asks about FreeRTOS, task priorities, xTaskCreate, ISR-safe queues, mutex vs semaphore, priority inversion, task notifications, task stack overflow or Zephyr threads. Produces RTOS task design, ISR deferral and timing analysis. Not for bare-metal superloops (use c-cpp-patterns or bare-metal-rust).
Install
npx skills add j4flmao/agent-skills --skill rtosgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/embedded-systems/rtos ~/.claude/skills/rtosPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# RTOS Engineering (FreeRTOS / Zephyr)
## Purpose
Turn a firmware feature into a set of tasks, priorities and communication primitives that meet deadlines deterministically. The skill covers how the FreeRTOS kernel actually schedules, which primitive to use for each interaction, how to keep ISRs short, how to size stacks and heaps statically, and how to prove timing on the target.
## Agent Protocol
### Trigger
"FreeRTOS", "RTOS task", "xTaskCreate", "task priority", "mutex vs semaphore", "priority inversion", "task notification", "stack overflow", "Zephyr thread", "RTOS queue", "ISR to task", "hard real-time", "rate monotonic", "EDF", "WCET", "RTOS vs Linux", "PREEMPT_RT".
### Input Context
- MCU/core (Cortex-M0/M3/M4F/M7/M33, RISC-V, ESP32), clock, RAM/flash budget
- Kernel and version (FreeRTOS V10/V11, SMP or not; Zephyr version)
- Deadlines and periods of each activity, interrupt sources and rates
- Safety/coding standard (MISRA C, IEC 61508/ISO 26262 context)
### Output Artifact
Task table, primitive choices, C code for tasks/ISRs, `FreeRTOSConfig.h` settings. No file unless requested.
### Response Format
```
Tasks: {name | priority | period/deadline | stack words | blocks on}
IPC: {producer -> primitive -> consumer}
ISRs: {source | work done in ISR | deferred to}
Config: {key FreeRTOSConfig.h settings}
Code: {snippet}
Verification: {WCET/response-time check, stack high-water marks, trace}
```
## 0. Is It Real-Time, and Which Platform?Details
- Skill name
rtos- Repository
- j4flmao/agent-skills
- Path
skills/embedded-systems/rtos/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Rtos skill do?
Use when the user asks about FreeRTOS, task priorities, xTaskCreate, ISR-safe queues, mutex vs semaphore, priority inversion, task notifications, task stack overflow or Zephyr threads. Produces RTOS task design, ISR deferral and timing analysis. Not for bare-metal superloops (use c-cpp-patterns or bare-metal-rust).
How do I install the Rtos skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill rtos. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Rtos popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Ask First
23nathanonn/agent-skills
Ask clarifying questions before executing tasks. Use this skill whenever the user says "ask me questions first", "clarify before doing", "ask before you start", invokes /ask-first, or wants Claude to gather requirements through Q&A before taking action. Also trigger when the user provides a task prefixed with "ask:" or says things like "I need help figuring out how to..." or "help me think through...". This skill ensures nothing is assumed — Claude asks until 95% confident, then executes.
Memory Management
45j4flmao/agent-skills
Use when the user asks about game engine memory, arena allocators, pool allocators, frame allocators, fragmentation, memory tracking and budgets, cache-friendly layout or GC spikes. Produces an allocator hierarchy and budget tracking. Not for embedded static-only allocation (use c-cpp-patterns).
Ironloop
10edouard-claude/ironloop
Verification-first software engineering harness with 5 layers (spec → gen → test → sim → pentest). Use when generating, reviewing, or planning code with AI agents, especially for Rust projects, new feature work, legacy migrations, or any task where code correctness must be guaranteed. Activates on phrases like "build a", "implement", "refactor", "review this code", "migrate from", "add tests for", or when the user describes a coding task with correctness or security requirements.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.