os-kernel-architecture
Guidance on OS and kernel architecture design trade-offs.
Install
mkdir -p .claude/skills/os-kernel-architecture && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16284" && unzip -o skill.zip -d .claude/skills/os-kernel-architecture && rm skill.zipInstalls to .claude/skills/os-kernel-architecture
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Operating-system and kernel architecture decisions: monolithic vs microkernel vs hybrid vs unikernel/exokernel, scheduler design, virtual memory & paging, IPC mechanisms, syscall/ABI boundaries, and interrupt handling. Architect-level trade-offs, not driver implementation. USE WHEN: designing or evaluating an OS/kernel, RTOS-vs-GPOS choice, kernel structure, scheduler/memory/IPC subsystem design, syscall/ABI surface, "monolithic", "microkernel", "unikernel", "exokernel", "scheduler", "virtual memory", "IPC". DO NOT USE FOR: Windows driver implementation (use windows driver skills); app-level concurrency (use language skills); container internals (use `virtualization`).Key capabilities
- →Evaluate monolithic kernel structures
- →Analyze microkernel designs for isolation and verifiability
- →Assess hybrid kernel architectures
- →Consider unikernel approaches for single-purpose applications
- →Examine exokernel designs for application control
- →Design scheduler, memory management, IPC, syscall/ABI, and interrupt subsystems
How it works
This skill provides a framework for evaluating different OS and kernel architectures by comparing their structures, pros, cons, and suitability for various use cases. It also details key subsystems that must be designed.
Inputs & outputs
When to use os-kernel-architecture
- →Comparing monolithic vs microkernel designs
- →Designing kernel subsystems
- →Selecting OS architecture
About this skill
OS / Kernel Architecture
Architect-level decisions for operating systems and kernels.
Kernel structure — the core decision
| Structure | Idea | Pros | Cons | Fits |
|---|---|---|---|---|
| Monolithic | All services in kernel space (Linux) | Fast (no IPC for services), mature | Large TCB, a fault can panic the system | General-purpose, performance-first |
| Microkernel | Minimal kernel; drivers/FS/net as user servers (seL4, QNX) | Isolation, verifiability, restartable servers | IPC cost on hot paths | Safety/security-critical, high-assurance |
| Hybrid | Monolithic core + some servers (XNU, NT) | Pragmatic balance | Ambiguous boundaries | Commercial desktop/mobile OS |
| Unikernel | App + minimal libOS into one address space (MirageOS) | Tiny attack surface, fast boot | Single app, weak isolation within | Single-purpose cloud/edge appliances |
| Exokernel | Kernel only multiplexes hardware; libOS in app | Max app control | Complexity pushed to apps | Research / specialized perf |
Decision drivers: isolation/assurance vs IPC overhead, TCB size, fault containment, restartability, verification goals (seL4 = formally verified).
Subsystems the architecture must pin down
- Scheduler: fairness (CFS) vs real-time (RMS/EDF, priority + inheritance to avoid priority inversion) vs throughput (batch). Preemptible vs cooperative. Tickless vs periodic tick. SMP load balancing, CPU affinity, NUMA awareness.
- Memory management: virtual memory + paging, page table levels, TLB pressure, huge pages, demand paging vs pinned, copy-on-write, NUMA placement, OOM policy. MMU-less (embedded) changes everything.
- IPC: synchronous rendezvous (seL4/L4) vs async message queues vs shared memory + doorbells. IPC latency is the microkernel make-or-break metric.
- Syscall/ABI: trap vs
syscallinstruction, vDSO for hot read-only calls, capability-based vs ambient-authority, ABI stability contract. - Interrupts: top-half/bottom-half split, threaded IRQs, interrupt latency and determinism (hard real-time needs bounded latency), MSI/MSI-X.
When to recommend what
- Need provable isolation / restartable drivers → microkernel (seL4/QNX).
- Need max throughput, rich ecosystem → monolithic (Linux).
- Single cloud/edge appliance → unikernel.
- Hard real-time → RTOS or PREEMPT_RT, EDF/RMS scheduling, bounded IRQ
latency (see
embedded-rtos).
Load deeper material with fetch_docs("os-kernel-architecture", <topic>) when
the knowledge base has it.
When not to use it
- →For Windows driver implementation
- →For app-level concurrency concerns
- →For container internals
Limitations
- →Does not cover Windows driver implementation
- →Does not cover app-level concurrency
- →Does not cover container internals
How it compares
This skill focuses on architect-level decisions for OS and kernel design, providing a structured comparison of different kernel types and their subsystems, rather than low-level implementation details.
Compared to similar skills
os-kernel-architecture side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| os-kernel-architecture (this skill) | 0 | 2mo | No flags | Advanced |
| software-architecture | 333 | 6mo | No flags | Intermediate |
| architect-review | 109 | 4mo | No flags | Advanced |
| mcp-builder | 136 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by claude-dev-suite
View all by claude-dev-suite →You might also like
software-architecture
davila7
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
architect-review
sickn33
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
solid-principles
SmidigStorm
Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.
codex
Lucklyric
Invoke Codex CLI for complex coding tasks requiring high reasoning capabilities. This skill should be invoked when users explicitly mention "Codex", request complex implementation challenges, advanced reasoning, or need high-reasoning model assistance. Automatically triggers on codex-related requests and supports session continuation for iterative development.
architecture-patterns
wshobson
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.