Analyze NDJSON wide-event logs to diagnose application behavior.
npx skills add https://github.com/JKc66/whats_recall --skill analyze-logs-jkc66
Please help me install this Agent Skill. Skill: analyze-logs Source: https://github.com/JKc66/whats_recall/tree/main/.agents/skills/analyze-logs Command: npx skills add https://github.com/JKc66/whats_recall --skill analyze-logs-jkc66
Analyze NDJSON wide-event logs from the local .evlog/logs directory to diagnose application behavior.
Analyze the latest logs in the local .evlog/logs directory to surface errors and slow requests.
High-intent search queries and answers about installing and using this skill.
You can analyze NDJSON logs from the local .evlog/logs directory by reading wide-event lines to surface key fields like timestamp, level, path, status, and duration, which helps diagnose errors and slow requests.
NDJSON wide-event logs are structured newline-delimited records containing application event data. You need to analyze them to debug errors, investigate slow endpoints, and understand request patterns.
Yes, you can parse both compact and pretty NDJSON formats. The log analysis reads structured lines from the local .evlog/logs directory and provides structured insights per event.
The best way to investigate slow endpoints is to analyze NDJSON logs by surfacing the duration field from wide-event records in the local .evlog/logs directory to identify performance bottlenecks.
To audit application activity, analyze NDJSON wide-event logs from the local .evlog/logs directory to understand request patterns by surfacing key fields like path, status, and timestamp per event.
rongaredeParse Codex CLI NDJSON logs to extract execution summaries and failure details.
nist0Query, visualize, and alert on ELK stack data with KQL.
saeed-vayghanCorrelate logs, traces, and metrics to diagnose root causes in distributed systems.
Prompt-or-Die-LabsConfigure centralized logging with ELK, Loki, or Splunk across services and environments.
