OpenParable
Skip to content
← Back to skills

Skylv Log Analyzer

DevOps & Security
skylv-log-analyzer

Skylv Log Analyzer is an Agent Skill for devops & security published in the LeoYeAI/openclaw-master-skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Parses and summarizes log files. Extracts errors, warnings, patterns, and insights from server logs and debug output. Triggers: analyze logs, parse log file, error summary, log analysis, debug logs.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/LeoYeAI/openclaw-master-skills/blob/HEAD/skills/skylv-system-log-analyzer/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/skylv-log-analyzer, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Log Analyzer

Overview

Parses and analyzes log files to extract errors, warnings, patterns, and actionable insights.

When to Use

  • User asks to "analyze these logs" or "check the error log"
  • Debugging session needs pattern analysis

How It Works

Step 1: Read log file

Windows: type server.log or Get-Content error.log -Tail 100 macOS/Linux: tail -n 100 app.log

Step 2: Detect log format

[2024-01-15 14:30:45] -> Timestamp bracketed ERROR 2024-01-15 -> Level + timestamp { "level": "error" } -> JSON structured

Step 3: Extract key information

Level: ERROR, WARN, INFO, DEBUG Timestamp: when it happened Source: which component/module Message: what happened

Step 4: Generate analysis report

Output Format

Total lines: 1,247 Time range: 10:00 -> 18:00

Errors: 23 Warnings: 67 Info: 892

Top Errors by frequency:

  1. Connection timeout (x12) - API calls to external service
  2. Auth failure (x6) - Failed login from IP xxx

Anomaly: Unusual spike at 16:00-17:00 (18 errors in 1 hour)

Recommendations:

  1. Check external service connectivity
  2. Review failed logins for security
  3. Add retry logic to DB writes