Log Analyzer

Read a log file, extract ERROR/WARN/CRITICAL lines, group similar messages, and produce a concise summary report. Use when analyzing application logs, agent...

Security Scan

The skill does what it says — it reads a user-specified log file, extracts and groups WARN/ERROR/CRITICAL lines, and writes a Markdown report; there are no unexpected network calls, environment variable access, or installers.

Purpose & Capability

Name, description, SKILL.md, and index.js all align: the code reads an input log, extracts severity lines, groups similar messages, and writes a report. No unrelated credentials, binaries, or config paths are requested.

Instruction Scope

SKILL.md instructs running index.js with an --input path. The runtime code will read whatever file path the user supplies (and will write a report to the working directory by default). This is expected for a log analyzer, but the user should avoid pointing it at sensitive system files.

Install Mechanism

No install spec — instruction-only skill with a small included Node.js script. Nothing is downloaded or installed by the skill itself.

Credentials

The skill requests no environment variables or credentials and does not read other config paths. Its access to the filesystem is limited to the user-specified input path and a user-writable output path.

Persistence & Privilege

always:false and normal invocation. The script writes a report file (default ./out/log_analysis_report.md) and prints a small JSON result to stdout — no attempt to persist beyond that or modify other skills/settings.

Assessment

This tool appears coherent and contains no hidden network or credential access. Before running, confirm the input path points only to logs you want analyzed (do not point it at sensitive system files like /etc/shadow, SSH keys, or other secrets). The script writes a Markdown file (default ./out/log_analysis_report.md) in the current working directory. Run it in a controlled environment if you are unsure, and inspect the generated report and console output. If you need stricter isolation, run it inside a container or VM.

Read a target log file, isolate important severity lines, group similar messages, and emit a Markdown summary.

Workflow

1. Confirm the input log path.
2. Run index.js with --input <logfile> and optional --out <report.md>.
3. Review the grouped output for dominant error families.
4. Use the report as a triage artifact, not as the only source of truth.

Output

Always include:

• total scanned lines
• WARN / ERROR / CRITICAL counts
• grouped issue buckets
• sample lines
• suggested first checks