skills.rest
jmcmullen
jmcmullenCOMMUNITY
Explore all skills by this author →
GitHub

analyze-logs

Analyze NDJSON event logs to identify errors, slow requests, and behavioral patterns.

1|Updated Jun 14, 2025
Search Tags:#performance#debugging#monitoring#logs#analyze#ndjson#request-patterns
One-click install
npx skills add https://github.com/jmcmullen/sharehouse-bills --skill analyze-logs-jmcmullen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-logs
Source: https://github.com/jmcmullen/sharehouse-bills/tree/main/.agents/skills/analyze-logs
Command: npx skills add https://github.com/jmcmullen/sharehouse-bills --skill analyze-logs-jmcmullen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read and analyze structured wide-event logs from the local .evlog/logs directory to debug errors, investigate performance issues, and understand application behavior.

Core Features & Use Cases

  • Read NDJSON and pretty-printed wide-event logs from .evlog/logs to identify errors, slow requests, and anomalous patterns.
  • Analyze by path, status, duration, and error details to surface root causes.
  • Provide actionable guidance for debugging, optimization, and monitoring.

Quick Start

Run the analyze-logs skill on your local logs directory to produce a diagnostic report.

Frequently Asked Questions about analyze-logs

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

FAQPage Schema
How do I analyze NDJSON logs to find application errors and slow requests?▼

You can analyze NDJSON logs by parsing wide-event log files to identify and summarize errors, slow requests, and behavioral patterns using fields like path, status, duration, and error data.

Can I parse pretty-printed JSON event logs or only standard NDJSON lines?▼

You can parse both standard NDJSON lines and pretty-printed JSON event logs. The analysis supports reading structured log files from the local directory to surface root causes across development and production environments.

What is the best way to debug performance bottlenecks using request duration logs?▼

Debugging performance bottlenecks involves analyzing request duration fields within structured event logs to surface slow requests, delivering actionable insights with context and suggested fixes for optimization.

How do I explore request patterns across development and production environments?▼

Exploring request patterns involves reading and analyzing structured wide-event logs to understand application behavior. It focuses on request-path exploration and anomalous patterns across both development and production contexts.

Does this log analysis approach require a specific directory structure for log files?▼

Yes, this log analysis approach requires reading structured wide-event logs specifically from the local .evlog/logs directory to produce diagnostic reports and deliver actionable debugging insights.

Related Skills

Explore More Software Engineering Skills→
rongarederongarede
4

codex-parser

Parse Codex CLI NDJSON logs to extract execution summaries and failure details.

Community
Intermediate
SpandanM110SpandanM110
1

code-review

Review code for correctness, security vulnerabilities, and performance issues.

Community
Intermediate
Himanshu040604Himanshu040604

sentry-go-sdk

Integrate the Sentry Go SDK for error tracking, tracing, and logging.

Community
Intermediate
dralgorhythmdralgorhythm
111

observability

Implement centralized logging, metrics, and distributed tracing with OpenTelemetry.

Community
Advanced