Skill Detail
Inspect live PostgreSQL waits locks and pressure before guessing at the bottleneck with pg_activity
Open a live PostgreSQL activity view during incidents so you can see sessions, waits, locks, and pressure before making a bad call.
Runbooks & DiagnosticsMulti-Framework
Runbooks & Diagnostics
Multi-Framework
Security Reviewed
⭐ 3k GitHub stars
⬇ 20.8k/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill inspect-live-postgresql-waits-locks-and-pressure-before-guessing-at-the-bottleneck-with-pg-activity
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
PostgreSQL connection access, pg_activity installation, terminal access to the target environment
Install & setup
Install pg_activity from distribution packages, pip, or pipx as documented upstream, provide credentials for the target PostgreSQL instance, then run pg_activity against the live server during diagnosis.
Author
DALIBO
Publisher
Organization
Last updated
Apr 15, 2026
Quick brief
Use pg_activity when an agent or operator needs a diagnose-now view of a running PostgreSQL instance rather than a general database client or monitoring platform. It is for checking active sessions, lock contention, waits, throughput, and resource pressure while an incident is happening. That scope boundary, live operational diagnosis for PostgreSQL workload pressure, keeps it skill-shaped instead of collapsing into a generic Postgres product card.