report-app-down

Name: report-app-down
Availability: InStock
Author: Promaker

Diagnoses a specified application and outputs a structured report.

Updated Apr 19, 2026

Search Tags:#diagnose #incident-response #logs-analysis #deploy-history #app-health

Ready to run

npx skills add https://github.com/PromakerDev/promaker-plugin --skill report-app-down

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: report-app-down
Source: https://github.com/PromakerDev/promaker-plugin/tree/main/plugins/promaker/skills/report-app-down
Command: npx skills add https://github.com/PromakerDev/promaker-plugin --skill report-app-down

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnostic-only deep status report for a Dokploy app. Engineering-facing — pulls status + deploy-history + runtime-logs and presents a structured summary with the raw error messages, stack traces and run URLs you'd need to escalate or write a postmortem. Does NOT take any actions. Use when the engineer says "diagnose X", "what's wrong with X", "why is X failing", "give me the full picture on X" — or when fix-app escalates here.

Core Features & Use Cases

Mirror of the operator's report-site-down but technical and exhaustive — surfaces every piece of context a debugging engineer (or an oncall taking the escalation) needs in one place. This skill never takes actions. For fixes, use fix-app. For start/stop, use the dedicated skills. For onboarding, use onboard-app / move-app.

Quick Start

Request a full diagnostic report for a Dokploy app by supplying its identifier.

Frequently Asked Questions about report-app-down

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose a Dokploy app that is failing or unresponsive?▼

To diagnose a failing Dokploy app, you compile its status, deploy history, and runtime logs into a single report. This provides a comprehensive, read-only diagnostic snapshot to troubleshoot incidents or perform postmortems.

How do I compile runtime logs and deploy history for an incident postmortem?▼

Compiling runtime logs and deploy history for an incident postmortem requires aggregating data from workflows and logs. The process preserves raw error messages, stack traces, and run URLs to output a structured summary suitable for escalation.

Can I use a diagnostic snapshot to fix app health issues directly?▼

A diagnostic snapshot cannot fix app health issues directly because it is strictly read-only and takes no actions. You must use a separate fix-app skill to resolve issues after reviewing the compiled status, deploy history, and runtime logs.

Does the app health report include raw error messages and stack traces?▼

The app health report includes raw error messages, stack traces, and run URLs. It aggregates data from workflows and logs to preserve the original context needed for escalation or writing a postmortem.

What is the best way to get a full picture of app health before escalating an incident?▼

The best way to get a full picture of app health before escalating is to request a complete diagnostic snapshot. This aggregates status, deploy history, and runtime logs into one structured summary for the oncall engineer.

Why does the diagnostic report not start or stop my Dokploy app?▼

The diagnostic report does not start or stop your Dokploy app because it is designed purely for read-only troubleshooting. You must use dedicated start/stop skills to manage app lifecycle actions separately from the reporting process.