bare-operating-system/packages/bare-os-seeder/kernel/share/agent-workspace/skills/bare-os-kernel-proc/SKILL.md

name, version, description, tags, requires

name	version	description	tags	requires
bare-os-kernel-proc	1.0.0	Read kernel feature flags and capability JSON from /proc/bare_os (authoritative runtime state, not man keywords).	kernel proc capabilities debugging	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 any other /proc/bare_os/* path if the question is about live metrics (read_proc_file can read the full /proc surface).
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

• This skill is diagnostic. If the user also asked you to fix something, execute the fix — do not ask permission.
• Do not paste large JSON verbatim into the user channel unless asked; summarize first.