Log Analyzer

Detect anomalous patterns and cluster error groups in application, system, and access logs.

110|18|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/TravisLeeeeee/awesome-openclaw-personas --skill log-analyzer-travisleeeeee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Log Analyzer
Source: https://github.com/TravisLeeeeee/awesome-openclaw-personas/tree/main/personas/devops/log-analyzer
Command: npx skills add https://github.com/TravisLeeeeee/awesome-openclaw-personas --skill log-analyzer-travisleeeeee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning high-volume, cryptic log streams into clear, prioritized findings so teams can understand what changed, why errors are happening, and what to do next.

Core Features & Use Cases

  • Anomaly and spike detection: identify error spikes, unusual request patterns, and newly appearing error types across application, system, and access logs.
  • Error clustering and summarization: group similar errors to reduce noise and include counts over a specified time window.
  • Distributed correlation and investigation guidance: reconstruct likely cause chains across services by correlating timestamps and dependencies, then recommend next checks.

Quick Start

Ask: "What's happening in the logs for the last hour, and group new versus recurring errors by service with counts?"

Frequently Asked Questions about Log Analyzer

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

FAQPage Schema
How do I detect anomaly spikes and new error types in application logs?

Anomaly detection in application logs identifies error spikes and newly appearing error types within a specified time window. It groups similar errors into clustered groups with occurrence counts, reducing noise and highlighting behavioral changes for investigation.

How do I group similar errors in system logs to reduce noise during incident triage?

Error clustering and summarization groups similar system log errors to reduce noise during incident triage. It produces clustered error groups with occurrence counts over a specified time window, turning high-volume cryptic log streams into clear, prioritized findings.

Can I reconstruct cause chains across services using distributed tracing logs?

Distributed correlation reconstructs likely cause chains across services by correlating timestamps and dependencies in tracing logs. It generates correlation narratives and recommends next checks to guide investigation workflows for elevated failures.

What is the best way to turn messy access logs into alert-ready outputs?

Turning messy access logs into alert-ready outputs involves detecting anomalous request patterns and grouping new versus recurring errors by service. This produces clustered error groups with counts and log-summary outputs without fabricating data.

Does log analysis work for investigating behavioral changes across application, system, and access logs?

Log analysis works for investigating behavioral changes across application, system, and access logs by detecting anomalous patterns and new error types. It applies to incident triage and distributed correlation, explaining what changed and why errors are happening.