log-analyzer

Analyze application logs to identify errors, exceptions, and frequency patterns.

171|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/ntygod/ZhiWei --skill log-analyzer-ntygod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-analyzer
Source: https://github.com/ntygod/ZhiWei/tree/main/src/main/resources/skills/log-analyzer
Command: npx skills add https://github.com/ntygod/ZhiWei --skill log-analyzer-ntygod

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users analyze application logs to identify errors, exceptions, and patterns in log data, enabling faster incident investigation and trends discovery while ensuring sensitive information is redacted in reports.

Core Features & Use Cases

  • Scans multiple log sources to surface errors, exceptions, and anomalous events.
  • Extracts key events like startup/shutdown, failures, and high-frequency error patterns for reporting.
  • Use cases include debugging, incident investigation, and trend reporting across time windows.
  • Data privacy: sensitive fields are redacted before sharing the report.

Quick Start

Run the provided log-redact.py script to process a log file and output a desensitized report.

Frequently Asked Questions about log-analyzer

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

FAQPage Schema
How do I analyze application logs to identify errors and exceptions?

To analyze application logs for errors and exceptions, you can run workflows that scan log sources to surface anomalous events and extract key failures for incident investigation. This process uses deterministic scripts to read files and process data.

What is the best way to detect high-frequency error patterns in log data?

The best way to detect high-frequency error patterns is to scan multiple log sources to extract anomalous events and count failures across time windows. This enables faster trend reporting and incident investigation.

How does log desensitization work for incident reports?

Log desensitization works by redacting sensitive fields in log data before generating a report. Running a dedicated script processes the log file and outputs a desensitized version, ensuring data privacy during sharing.

Can I scan remote log sources for stack traces and failures?

Yes, you can scan remote log sources for stack traces and failures. The analysis applies to debugging and incident investigation across both local and remote log sources using shell execution and file reading capabilities.

Do I need specific scripts to extract startup and shutdown events from logs?

You need to run the provided scripts to extract startup and shutdown events from logs. These scripts implement deterministic workflows that identify key events and surface errors for trend reporting.

What are the limitations of using shell_exec for log analysis?

A limitation of using shell_exec for log analysis is that it requires appropriate execution permissions and environments to read files and run scripts. It operates deterministically, so complex non-text logs may require preprocessing.