Skill Detail
Triage production log spikes and incidents from the terminal with lnav
Open raw logs, jump to error clusters, query structured fields, and summarize incident clues without shipping data to a separate platform.
Runbooks & DiagnosticsMulti-Framework
Runbooks & Diagnostics
Multi-Framework
Security Reviewed
⭐ 10.2k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill triage-production-log-spikes-and-incidents-from-the-terminal-with-lnav
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
lnav, local or remote log files, terminal access
Install & setup
Install lnav from your system package manager or build it from source, then open one or more log files with
lnav /path/to/log* and use its built-in SQL, filters, and timeline views for triage.Author
tstack
Publisher
Individual
Last updated
Apr 15, 2026
Quick brief
Use lnav when an agent needs to investigate raw log files during an incident instead of guessing from `tail` output. The agent can open mixed log sources, pivot on structured fields, jump straight to error bursts, and summarize what changed around the spike. The scope is terminal-first incident triage on existing logs, not generic observability hosting or log-platform administration.