Log Analyzer Skill

Parse JSONL pipeline logs and display errors, warnings, and retries as tables.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fstr21/sportsbot --skill log-analyzer-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Log Analyzer Skill
Source: https://github.com/fstr21/sportsbot/tree/main/.claude/skills/log-analyzer
Command: npx skills add https://github.com/fstr21/sportsbot --skill log-analyzer-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rich, and includes scripts (resource) components.

What problem does it solve?

Sifting through raw log files to find errors, warnings, or performance bottlenecks is a tedious and time-consuming task. This Skill automates log analysis, providing clear summaries and actionable insights, so you can quickly understand pipeline health.

Core Features & Use Cases

  • Structured Log Parsing: Scans and parses structured JSON logs from all pipeline runs, making complex log data easy to digest.
  • Error & Warning Identification: Quickly identifies and summarizes error, warning, and info messages across scripts, highlighting critical issues.
  • Performance & Retry Metrics: Tracks API retry patterns, identifies slow operations, and flags rate-limiting issues, helping you optimize performance.
  • Use Case: After a pipeline run, use this Skill to verify successful completion, check for any errors or warnings, or investigate why a script might have failed.

Quick Start

Analyze logs from the last 24 hours

python .claude/skills/log-analyzer/scripts/analyze_logs.py --hours 24

Show only error-level log entries

python .claude/skills/log-analyzer/scripts/analyze_logs.py --level error

Frequently Asked Questions about Log Analyzer Skill

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

FAQPage Schema
How do I analyze pipeline logs to find errors and performance issues?

Log analysis scans structured JSON logs from pipeline runs to identify errors, warnings, and performance bottlenecks. This Skill parses JSONL files, detects failures, tracks API retries and slow calls, and displays results as readable tables with plain-English summaries so you can quickly understand pipeline health and pinpoint root causes.

Can I filter logs by severity level or time range?

Yes. The Skill supports filtering by log level (error, warning, info) and time windows. Use the --level flag to show only specific severity levels and --hours to analyze logs from recent runs, letting you focus on the issues most relevant to your investigation.

What log format does this tool work with?

The Skill parses structured JSON logs stored as JSONL (JSON Lines) files in the logs/ directory, one JSON object per line. It handles malformed entries gracefully, normalizes timestamps to ET timezone, and reconstructs complete pipeline history from per-script log files.

How do I identify rate-limiting and API retry patterns in my logs?

The Skill automatically detects and highlights API retries and rate-limiting events within your logs, presenting metrics that help you spot performance bottlenecks. This lets you optimize retry strategies and understand whether external services are throttling your pipeline.

Do I need special setup or dependencies to run log analysis?

The Skill requires the Rich library for tabular display and read-only access to your logs/ directory. No database or complex environment configuration is needed—run the analysis script directly from your pipeline's .claude/skills/ directory.