- Home
- Skills
- DevOps & Cloud
- Server Ops Troubleshooter
More screenshots
Works with the AI Agents you already use
Server Ops Troubleshooter
Expert Docker and Linux systems diagnosis with a safety-first, copy-pasteable remediation workflow.
$7.77
Server Ops Troubleshooter
Example session with this skill installed
My docker container keeps crashing with an exit code 137 on the production server. I need to find out why and fix it.
- Read your context and instructions
- Compiled the server ops troubleshooter
🔍 Diagnosis
The container is likely being terminated by the Linux Out-Of-Memory (OOM) killer.
📋 Diagnostic commands
docker inspect <container_id> --format='{{.State.OomKilled}}'
dmesg | grep -i "oom-killer"
free -h
🛠️ Remediation
[Production] 1. Limit container memory in docker-compose.yml:
deploy:
resources:
limits:
memory: 512M
- Restart service...
Connects securely to your tools. The creator never sees your data.
About this skill
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.
SSH password auth requires paramiko via the managed Python environment. Native Windows pathing quirks may require forward slashes for file operations.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Requires
Permissions
Allowed Hosts