Skill Detail
Turn PostgreSQL logs into incident and tuning reports with pgBadger
Use pgBadger when an agent needs to convert raw PostgreSQL logs into readable evidence about slow queries, errors, and workload hotspots after an incident.
Runbooks & DiagnosticsMulti-Framework
Runbooks & Diagnostics
Multi-Framework
Security Reviewed
⭐ 4k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill turn-postgresql-logs-into-incident-and-tuning-reports-with-pgbadger
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
pgBadger, PostgreSQL logs with compatible log settings, and a shell environment for report generation.
Install & setup
Install pgBadger from your package manager or source, point it at PostgreSQL log files, and generate HTML or text reports during incident review or tuning sessions.
Author
darold
Publisher
Individual
Last updated
Apr 15, 2026
Quick brief
pgBadger gives an agent a concrete post-incident job: parse PostgreSQL logs, summarize what happened, and output reports that help humans spot slow queries, lock pain, error bursts, and tuning opportunities. Invoke it when the real need is evidence-driven diagnosis from logs, not when you just need a database client or generic monitoring dashboard. The boundary is tight and skill-shaped: PostgreSQL log analysis and reporting, not broad database administration or a plain product listing.