Agent Skill · Qovery

qovery-troubleshoot

Diagnoses and fixes deployment failures, application crashes, build errors, connectivity problems, stuck deployments, and cluster issues on Qovery. Uses a systematic 8-layer diagnosis with MCP Server integration, CLI, and API, and generates runbooks for recurring issues. Use when the user reports a Qovery deployment that is failing, broken, stuck, or crashing. (For slow deployments use qovery-speedup; for cost optimization use qovery-optimize.)

View SKILL.md on GitHub → Source repository Provider profile
Provider: Qovery Path in repo: qovery-troubleshoot/SKILL.md

Skill body

Qovery Troubleshoot Skill

This skill diagnoses and fixes infrastructure and application issues on Qovery — crashes, build failures, connectivity problems, stuck deployments, or cluster errors. It systematically narrows the root cause, applies the fix, and writes a runbook to prevent recurrence.

For slow-but-working deployments use qovery-speedup. For cost-driven optimization use qovery-optimize.

When to Use This Skill

Trigger phrases:

Workflow checklist

Troubleshooting Progress:
- [ ] Phase 1 — Context gathering (auth, service overview, problem identification)
- [ ] Phase 2 — Systematic 8-layer diagnosis
- [ ] Phase 3 — Apply matching playbook
- [ ] Phase 4 — Fix & redeploy
- [ ] Phase 5 — Verify the fix worked
- [ ] Phase 6 — Generate runbook
- [ ] Phase 7 — Prevention recommendations

Reference materials (load on demand)

Phase File Purpose
Console URL reference/console-url-detection.md Extract IDs from a Qovery Console URL
Auth reference/auth.md API token flow
MCP reference/mcp-server-integration.md When to prefer MCP over CLI/API; how to set up MCP
Phase 1 reference/phase1-context-gathering.md Service inventory, problem identification, log fetching
Phase 2 reference/phase2-8-layer-diagnosis.md Cluster → Kubernetes → image → container → app → connectivity → config → cost
Phase 3 reference/phase3-playbooks.md Build failure, OOM, port mismatch, health check, stuck deploy, DB connectivity, etc.
Phase 4 reference/phase4-fix-redeploy.md Apply config fix, code fix, infra fix, redeploy
Phase 5 reference/phase5-verification.md Confirm the issue is gone end-to-end
Phase 6 reference/phase6-runbook.md Generate a reusable runbook for recurring issues
Phase 7 reference/phase7-prevention.md Recommend monitoring, health checks, deployment stages, etc.

8-layer diagnosis (overview)

When triaging an issue, walk top-down through these layers in reference/phase2-8-layer-diagnosis.md:

  1. Cluster — Is the K8s cluster healthy and ready?
  2. Kubernetes — Are pods scheduled? Running? In CrashLoopBackOff?
  3. Image — Did the build succeed? Is the image pullable?
  4. Container — Is the entrypoint correct? Is the port right? Is the user non-root?
  5. Application — Does the app start? Are the secrets present? Are env vars correct?
  6. Connectivity — Can the app reach its DB? Can it be reached from outside?
  7. Configuration — Health checks, deployment stages, resource limits, autoscaling
  8. Cost — Is anything hitting a quota or cost cap that is causing failures?

Quick reference

MCP queries

# Status & Health
"Is everything healthy?"
"Show failing services"
"What's the status of all services?"
"Is the cluster healthy?"

# Logs & Diagnostics
"Show error logs from the last hour for {service}"
"Why is my deployment failing?"
"Analyze failed build logs for {service}"
"Why is the health check failing?"

# Connectivity
"Why can't my app connect to the database?"
"Is the database running?"
"Show database connection info"

# Resources
"Show CPU usage across all services"
"Why is my service out of memory?"

# Actions
"Restart the API service"
"Redeploy the backend"
"Cancel the ongoing deployment"
"Scale the API to 5 replicas"
"Rollback the API to previous version"

CLI commands

# Context and status
qovery context set
qovery service list
qovery status --watch

# Logs (use the flag matching the service type, or --service for any type)
qovery log --application "name" --since 1h
qovery log --container "name" --since 1h
qovery log --database "name" --since 1h
qovery log --job "name" --since 1h
qovery log --service "name" --follow
qovery log --service "name" --filter "ERROR"
qovery log --service "name" --tail 100

# Environment variables
qovery application env list
qovery environment env list

# Connectivity testing
qovery port-forward --service "name" --port 8080:8080
qovery shell --service "name"

# Cluster
qovery cluster list

API endpoints

# Base URL: https://api.qovery.com   Auth: Authorization: Token $QOVERY_API_TOKEN

# Status & Config
GET  /environment/{envId}/statuses               All service statuses
GET  /application/{appId}                        Service config
GET  /application/{appId}/deploymentHistory      Deployment history
GET  /application/{appId}/environmentVariable    Environment variables
GET  /organization/{orgId}/cluster               Cluster list and status

# Service logs (last 1000 lines)
GET  /application/{applicationId}/log
GET  /container/{containerId}/log
# Note: jobs / helms / databases have no API log endpoint — use `qovery log` CLI.

# Deployment logs
GET  /environment/{environmentId}/log            v1
GET  /environment/{environmentId}/logs           v2 (richer — includes error details, stages, hints)

# Actions
PUT  /application/{appId}                        Update service config (fix)
POST /application/{appId}/restart
POST /environment/{envId}/deploy
POST /environment/{envId}/cancelDeployment       Cancel stuck deployment

Skill frontmatter

license: MIT compatibility: opencode metadata: {"audience"=>"developers", "workflow"=>"troubleshooting"}