Log Analyzer

Parse and analyze structured JSON pipeline logs with Rich tables.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill eliminates the confusion of reading raw JSON logs by automatically parsing, analyzing, and explaining pipeline execution data in plain English.

Core Features & Use Cases

  • Log Analysis: Scan and parse structured JSON logs from pipeline runs to identify errors, warnings, and patterns.
  • Pipeline Monitoring: Track which scripts ran successfully, detect API issues, and monitor performance metrics.
  • Use Case: When your sports data pipeline completes, use this Skill to automatically check if all components ran without errors and identify any rate limiting or slow API calls that need attention.

Quick Start

Use the log analyzer skill to check for errors in the last 24 hours of pipeline logs.

Frequently Asked Questions about Log Analyzer

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

FAQPage Schema
How do I parse and analyze JSON logs from pipeline runs?

Parse JSON logs by using the log analyzer to scan structured JSONL entries from your pipeline logs directory. The Skill automatically parses each log entry with timestamp handling in ET timezone, gracefully handles malformed JSON, and formats results into readable Rich tables so you can quickly identify errors, warnings, API issues, and performance bottlenecks across recent runs.

Can I filter logs by script, error level, or time window?

Yes, the log analyzer supports filtering by sport, script name, log level, and time window so you can narrow analysis to specific components or recent time periods. This lets you focus on particular pipeline stages or recent activity without scanning all logs.

What should I do before using the log analyzer on my pipeline?

Ensure your pipeline logs are stored in structured JSON format in the logs/ directory and use ET timezone for timestamp consistency. The Skill reads logs as read-only, so no special permissions are needed beyond access to the logs directory.

How do I detect API rate limiting and slow operations in my pipeline?

Run the log analyzer on your recent pipeline logs to automatically detect API retries, rate limiting events, and slow operations. The Skill parses these patterns from your JSON logs and surfaces them in formatted tables so you can identify performance bottlenecks and API issues needing attention.

What happens if my logs contain malformed JSON entries?

The log analyzer gracefully handles malformed JSON without failing the entire analysis. It continues parsing valid entries and formats readable results, so occasional formatting issues in logs won't block your pipeline monitoring.

Can I use the log analyzer to verify all pipeline components ran successfully?

Yes, scan your pipeline logs with the log analyzer to verify script execution status, identify errors and warnings across all components, and confirm successful runs. This gives you a clear overview of whether all pipeline stages completed without issues.