tux

Stop manually grepping logs and hunting for misconfigured services. This Linux troubleshooting suite provides a systematic way to diagnose and repair system health issues. It handles everything from kernel errors and OOM kills to disk SMART health and driver instability.

What it does

• System Diagnostics runs comprehensive scans across CPU, GPU, memory, storage, and network stacks to identify root causes.
• Background Monitoring configures systemd timers to watch for hardware errors, overheating, and service failures locally.
• Automated Remediation proposes specific fixes for detected problems and applies them only with explicit user approval.
• Transaction History maintains a record of every change, allowing for safe rollbacks of config edits or package modifications.
• State Snapshots captures the system state before and after scans to provide evidence-based reporting.

How it works

1. Health Check initiates a scan of hardware and software layers using tux-snapshot and tux-scan.
2. Investigation digs into logs and configs for any suspicious metrics or failed components.
3. Reporting delivers a prioritized list of problems, warnings, and healthy areas with proposed fixes.
4. Monitoring enables local background checks via tux-monitor that trigger desktop notifications on new failures.
5. Undo reverts specific changes by referencing a change ID from the tux-undo list.

Frameworks & tools

Built for Linux environments. Uses standard system utilities and systemd user timers for local monitoring.

Why this beats prompting it yourself

Generic LLMs lack the system-level context to know which logs to check or how to interpret specific kernel hardware errors. This skill uses dedicated local tools to gather raw evidence before the AI analyzes it, ensuring fixes are based on reality rather than hallucinated paths.

Use cases

• Diagnose why a machine is running slow or feeling unstable.
• Monitor laptop battery wear and hardware SMART status in the background.
• Roll back a configuration change that caused a service to stop starting.
• Perform a fresh audit of a new Linux installation for hardware compatibility.

Known limitations

Background monitoring is strictly local and requires systemd. Undoing changes might require manual intervention if files were edited externally after the agent's modification.