---
name: p2p-os-status
version: 1.0.0
description: Check and report health of the bare operating system, Hyperdrive, and Hyperswarm peers.
tags: [p2p, hyperdrive, monitoring]
requires: [bare-fs, hyperswarm]
---

# p2p-os-status Skill

## When to use

Use this skill whenever the user asks for system status, peer count, drive health, or debugging P2P connectivity.

## Execution steps

1. Use **`list_directory`** / **`read_file`** on relevant **`/home/...`** paths (personal vs system) when the question is about files on Hyperdrive.
2. Call **`get_swarm_peers`** (and **`get_system_info`** as needed) for swarm / session context when exposed by the booter.
3. Use **`read_proc_file`** on `**/proc/bare_os/*`** mirrors when the user cares about kernel/session metrics (see the **bare-os-kernel-proc** skill for feature/capability JSON).
4. Check SSH/kernel narrative only when **`read_proc_file`** or **`read_man_page`** confirms how this image exposes **`sshd`** (do not assume **`node`** exists).
5. When a **personal static site** matters, after **`login`** check **`~/.www`** (and optional **`curl -I http://127.0.0.1:8088/`**, or the port from **`BARE_OS_WWW_PORT`** in env); initd logs append to **`/var/log/bare-os/www.log`**.
6. Summarize in clear bullet points:

   - Drive sync status
   - Active peers
   - Any warnings or errors
   - Recent MEMORY.md highlights

## Output format

Always respond with:

- **Status Overview** (3-5 bullets)
- **Peer Summary**
- **Recommended Actions** (if any)

Do not perform any write operations unless explicitly instructed.