---
name: bare-os-kernel-proc
version: 1.0.0
description: Read kernel feature flags and capability JSON from /proc/bare_os (authoritative runtime state, not man keywords).
tags: [kernel, proc, capabilities, debugging]
requires: [read_proc_file, vfs]
---

# bare-os-kernel-proc Skill

## When to use

Use when the user asks what kernel features are **on or off in this session**, what capabilities exist, or whether something (SSH, replication, metrics) is actually enabled. Do **not** infer live kernel state from **`read_man_page`** / **`apropos_man`** alone — those search documentation text.

## Execution steps

1. Call **`read_proc_file`** on **`/proc/bare_os/features`** or **`/proc/bare_os/features.json`** (same payload shape as documented in the static system prompt).
2. Call **`read_proc_file`** on **`/proc/bare_os/capabilities.json`** for structured capability bits.
3. Optionally read **`/proc/bare_os/metrics_live.json`** or related `**/proc/bare_os/*`** paths if the question is about live metrics (stay within tool allowlists).
4. Use **`get_system_info`** with **`want: capabilities`** or **`want: swarm`** only as a convenience when you already need bundled blobs; prefer **`read_proc_file`** for “what is enabled **now**?”.

## Output format

- **Sources**: list which `/proc/bare_os/*` files you read.
- **Summary**: 3–6 bullets of what is enabled/disabled or missing, in plain language.
- **Gaps**: if a path is missing or empty, say so — do not guess from docs.

## Constraints

- Read-only unless the user explicitly asks for a change that is allowed by **`AGENTS.md`** and tools policy.
- Do not paste large JSON verbatim into the user channel unless asked; summarize first.