Server Ops Troubleshooter

The problem

Server failures and Docker deployment errors often lead to hours of "guess-and-check" troubleshooting. Blindly running remediation commands on production systems risks data loss and extended downtime.

What it does

• Executes a systematic 6-step diagnostic workflow to find the root cause before suggesting fixes.
• Generates copy-pasteable bash commands for Docker logs, system resource checks, and container status.
• Provides specialized remediation for Java JAR boot failures, PostgreSQL connection errors, and Jenkins pipeline blocks.
• Calculates risk levels and enforces mandatory warnings for destructive actions like volume deletion or service restarts.
• Automates remote server inspection using Python-based SSH clients when local tools are unavailable.

Frameworks & tools

Docker, Linux (Ubuntu/Debian/CentOS), Java (Spring Boot/JAR), PostgreSQL, Jenkins, and Paramiko for SSH automation.

Why this beats prompting it yourself

Standard LLMs often suggest dangerous commands without checking your environment first. This skill enforces a "diagnose-first" posture, distinguishes between local and production contexts, and includes a pre-built library of verified sysadmin commands that prevent common operator errors.

Use cases

• Troubleshooting "OOMKilled" or "Exit 137" errors in Docker containers.
• Fixing "Connection Refused" errors between application services and databases.
• Resolving disk-full or permission-denied issues on Linux production servers.
• Debugging failed Jenkins builds or Docker-in-Docker socket mounting issues.

Known limitations

Standard SSH binaries may require a custom Python script for non-interactive password authentication on Windows hosts.