sys-diag
Skill1 starsChanged 3 months agoMITView on GitHub
Use when diagnosing system health issues, checking RAM/swap pressure, inspecting storage utilization, verifying systemd service failures, or analyzing WSL2 kernel metrics
In this repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- async-python-patternsSkill
- bash-defensive-patternsSkill
- brainstormingSkill
- clean-systemSkill
- debian-linux-triageSkill
- dispatching-parallel-agentsSkill
- dotfilesSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- handoffSkill
- harness-checkSkill
- mcp-builderSkill
- perf-tuneSkill
- prompt-architectSkill
- python-mcp-server-generatorSkill
- python-performance-optimizationSkill
- python-testing-patternsSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- security-and-hardeningSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- tmux-agentsSkill
- update-runtimesSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
- wsl-snapshotSkill
- async-python-patternsSkill
- bash-defensive-patternsSkill
- brainstormingSkill
- clean-systemSkill
- debian-linux-triageSkill
- dispatching-parallel-agentsSkill
- dotfilesSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- handoffSkill
- harness-checkSkill
- mcp-builderSkill
- perf-tuneSkill
- prompt-architectSkill
- python-mcp-server-generatorSkill
- python-performance-optimizationSkill
- python-testing-patternsSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- security-and-hardeningSkill
- subagent-driven-developmentSkill
- sys-diagSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- tmux-agentsSkill
- update-runtimesSkill
- using-git-worktreesSkill
- The first 60 shown.
The file
Files
System Diagnostics Skill
Comprehensive diagnostic engine for inspecting Debian WSL2 system health, resource headroom, running processes, and active systemd units.
Trigger Scenarios
- High memory pressure or sluggish terminal response
- Investigating systemd unit degradation or crashed services
- Verifying WSL2 kernel, uptime, or network connectivity
- Periodic or pre-maintenance health baseline inspection
Invocation
${PROJECT_DIR:-.}/scripts/sys_diag.sh [flags]Command Options
| Option | Description |
| (none) | Standard diagnostic output (kernel, memory, ext4 disk, top CPU/RAM processes, failed systemd units) |
--full | Extended diagnostics including network listening sockets and 9P mount inspection |
--json | Machine-readable JSON output for automated telemetry and tooling |
Safety Classification
- Tier 0 (Autonomous Read-Only): Non-destructive execution with zero side effects.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

