analyze-logs

Analyze NDJSON application logs to identify errors and performance issues.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/balkhaev/bank --skill analyze-logs-balkhaev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-logs
Source: https://github.com/balkhaev/bank/tree/main/.agents/skills/analyze-logs
Command: npx skills add https://github.com/balkhaev/bank --skill analyze-logs-balkhaev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the difficulty of manually parsing through scattered, complex application logs to identify the root cause of errors or performance bottlenecks.

Core Features & Use Cases

  • Automated Log Parsing: Automatically detects and parses NDJSON or pretty-printed log files from standard project directories.
  • Error and Performance Analysis: Identifies recurring error patterns, slow endpoints, and specific request failures using structured log data.
  • Use Case: When a user reports a 500 error on a specific checkout page, this skill can scan the recent logs to pinpoint the exact stack trace and the associated request context.

Quick Start

Use the analyze-logs skill to find all error-level events in the most recent log file and suggest a fix for the most frequent issue.

Frequently Asked Questions about analyze-logs

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

FAQPage Schema
How do I analyze application logs to find the root cause of a 500 error?

To analyze application logs for a 500 error, this skill scans structured NDJSON log streams to pinpoint the exact stack trace and associated request context. It identifies specific request failures by mapping error stack traces against defined service and environment contexts.

What is the best way to debug performance bottlenecks using NDJSON log files?

Debugging performance bottlenecks using NDJSON logs is done by scanning local .evlog/logs/ directories to identify slow endpoints. The analysis maps request metadata and status codes against defined service contexts to isolate recurring performance issues.

How do I parse structured NDJSON logs to identify recurring error patterns?

Parsing structured NDJSON logs to identify recurring error patterns is handled by scanning local log directories and extracting error-level events. The skill operates by parsing JSON-formatted streams to detect and correlate request failures and stack traces.

Does log analysis work with pretty-printed files or only structured NDJSON streams?

Log analysis works with both structured NDJSON and pretty-printed log files. The skill automatically detects and parses these formats from standard project directories to extract request metadata and map them against service contexts.

Can I use this for troubleshooting request failures in a specific environment?

Yes, you can use this for troubleshooting request failures in a specific environment by mapping structured log data against defined service and environment contexts. It correlates status codes and stack traces to identify the exact request context of failures.