{"id":79588,"plugin_id":"plugins_6ab427b8c6908191a438adb4b6f315d4","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:11:26.617Z","digest":"1605c8b7dde529c03a1e2f702530d3b87102eba63fdd34a61ce5e591a4eec8d5","against":null,"payload":{"description":"Inspect disk, memory, CPU, I/O, process and log symptoms using platform-aware, read-only Unix diagnostics.","included_files":[],"name":"system-observability","skill_md_contents":"---\nname: system-observability\ndescription: Inspect disk, memory, CPU, I/O, process and log symptoms using platform-aware, read-only Unix diagnostics.\n---\n\n# System diagnostics and resource usage\n\n## Scope and execution truth\nThis is a skills-only assistant workflow. Do not claim to execute system commands, inspect the user's host, install packages, or complete side effects without actual authorized tools and observed results. User-pasted output is evidence, not a machine connection.\n\n## Procedure\n1. Clarify symptom and operating context: disk pressure, CPU saturation, memory, permissions, hanging processes, logs or network failure.\n2. Start with read-only, low-impact commands and note whether measurements are snapshots or sampled intervals.\n3. Explain platform differences among `top`, `vm_stat`, `free`, `df`, `du`, `iostat`, `journalctl` and related tools; never assume all exist.\n4. Interpret only observed metrics; distinguish capacity, utilization, and latency, and do not invent root causes.\n5. Escalate to more invasive diagnostics only if warranted and approved; avoid dumping secrets from logs or environment.\n6. Give a targeted next diagnostic and validation criteria for the hypothesis.\n\n## Relevant references\n- Read `../../references/diagnostics-playbook.md` for domain-specific guidance.\n- Read `../../references/permissions-and-processes.md` for domain-specific guidance.\n- Read `../../references/security-and-secrets.md` for domain-specific guidance.\n\n## Completion checks\n- No guessed system state\n- Minimal diagnostic impact\n- Timebase and metrics interpreted correctly\n\n## Deliverable\nUse the minimum format that makes the answer actionable: the actual command or patch, platform assumptions, a preview before risky changes, and a reproducible validation step. Clearly label proposed actions versus observed execution.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}