analyze-logs

Read NDJSON logs from `.evlog/logs/` and filter for specific errors.

Updated Aug 23, 2026

Search Tags:#debugging #log analysis #error diagnosis #performance monitoring #NDJSON

Ready to run

npx skills add https://github.com/memorysaver/SIBYL --skill analyze-logs-memorysaver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-logs
Source: https://github.com/memorysaver/SIBYL/tree/main/.agents/skills/analyze-logs
Command: npx skills add https://github.com/memorysaver/SIBYL --skill analyze-logs-memorysaver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Analyze application logs quickly to identify and understand issues in debugging errors, slow requests, or performance issues.

Core Features & Use Cases

Error Diagnosis: Detect and analyze error logs for root causes and debugging information.
Performance Monitoring: Monitor slow requests and pinpoint performance bottlenecks.
Log Review: Summarize log information and track trends or specific incidents.

Quick Start

Use the analyze-logs skill to check for errors in the .evlog/logs/ directory related to 'timeout' errors over the past week.

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 application logs to diagnose errors?▼

To analyze NDJSON application logs for error diagnosis, the Skill reads structured log events from the `.evlog/logs/` directory, filters for specific issues, and presents the root causes in a readable format.

Can I monitor slow requests and performance bottlenecks from .evlog logs?▼

Yes, you can monitor slow requests and pinpoint performance bottlenecks by filtering the structured NDJSON log events stored in your `.evlog/logs/` directory for performance-related incidents.

What is the best way to filter structured NDJSON logs for specific timeout errors?▼

The best way to filter structured NDJSON logs for timeout errors is to query the `.evlog/logs/` directory and isolate specific error events over a defined time range, such as the past week.

Does this log analysis approach work with NDJSON files stored in custom directories?▼

This log analysis approach is optimized for NDJSON files specifically stored in the `.evlog/logs/` directory, meaning logs must be placed there to be read and filtered effectively.

How do I summarize log information and track trends for specific incidents?▼

To summarize log information and track trends, the Skill reads structured NDJSON events from `.evlog/logs/`, filters for targeted incidents, and presents the findings in a readable format.