gasp-diagnosticslisted

# GASP Diagnostics Enables comprehensive Linux system diagnostics using GASP's AI-optimized monitoring output. Actively fetches metrics from hosts and provides intelligent analysis with context-aware interpretation. ## Fetching GASP Metrics When user mentions a host or requests a system check: 1. **Fetch the metrics endpoint** ``` web_fetch("http://{hostname}:8080/metrics") ``` 2. **Hostname formats supported** - mDNS/local: `accelerated.local`, `hyperion.local` - DNS names: `proxmox1`, `dev-server`, `workstation` - IP addresses: `192.168.1.100` 3. **Default port**: 8080 (unless user specifies otherwise) 4. **Error handling** - Host unreachable: Inform user, suggest checking if GASP is running - Port closed/refused: Try suggesting `systemctl status gasp` on the host - JSON parse error: GASP may not be installed or wrong endpoint - Timeout: Network issue or host down 5. **Multi-host queries**: If user mentions multiple hosts, fetch each in sequence and compare ## Quick Diagnosis Workflow For any system check request: 1. **Fetch** metrics from specified host(s) 2. **Check summary first**: Look at `summary.health` and `summary.concerns[]` 3. **Identify issues** using metric correlations below 4. **Report** findings with severity and specific recommendations ## Trigger Examples These user messages should trigger this skill and active fetching: - "Check hyperion for me" - "What's going on with accelerated.local?" - "Is proxmox1 having is