Parse application logs, surface error clusters, and summarize failure patterns.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Log Analyzer
Parse application log files, group recurring errors, and produce a
summary of failure patterns.
## When to Use This Skill
Use when the user asks to analyze logs, find recurring errors, or
summarize failures from a log file.
## Implementation Steps
### Step 1: Run the Analyzer
Run the bundled analyzer against the log file:
```bash
python scripts/analyze.py --input app.log --format json
```
### Step 2: Classify Failures
Match each error cluster against the known failure patterns documented
in [the pattern reference](references/patterns.md).
### Step 3: Summarize
Report the top error clusters with counts, first/last occurrence
timestamps, and the matched pattern name.
The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_3o5rjm52qvzsbcue
GET https://markdownregistry.com/api/v1/resolve?ref=stbenjam/skillsaw/log-analyzer
GET https://markdownregistry.com/api/v1/blob/b79d3a6fa30a4d3efb1ca436f33813f81d38d687b3b41a99806ef42d83b37d3d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
stbenjam/skillsaw · .agents/skills/skillsaw-issue-solver/SKILL.md · Pick up open GitHub issues from collaborators and create PRs to solve them. Use when triaging and resolving reported…
stbenjam/skillsaw · .agents/skills/skillsaw-issue/SKILL.md · Use when skillsaw reports a likely false positive, misses an edge case, behaves incorrectly, or needs an RFE. Gather a…
stbenjam/skillsaw · .agents/skills/skillsaw-lint/SKILL.md · Use when modifying agentic contextual building blocks like skills (SKILL.md), slash commands, agents, hooks, plugins…
stbenjam/skillsaw · .agents/skills/skillsaw-onboard/SKILL.md · Onboard a repository to skillsaw — run the linter, triage the findings by rule, apply autofixes, manually fix what…
stbenjam/skillsaw · .agents/skills/skillsaw-pr-followup/SKILL.md · Follow up on open PRs in skillsaw — fix failing CI, address reviewer feedback, push updates, and validate backward…
stbenjam/skillsaw · .agents/skills/skillsaw-release-ready/SKILL.md · Audit skillsaw for release readiness — test new rules against real repositories, audit core architectural dimensions…
stbenjam/skillsaw · .agents/skills/skillsaw-release/SKILL.md · Bump the version, generate release notes, and publish a new skillsaw release to PyPI. Use when cutting a new release.
jpcaparas/skills · skills/agents/skill-creator-advanced/evals/files/unrelated-repo/.agents/skills/log-analyzer/SKILL.md · Analyze application logs, debug log problems, inspect output, and help with anything related to logs.
lethe044/agentskill-kit · skills/log-analyzer/SKILL.md · Summarizes application log files by severity, time range and the most frequent error messages. Use when the user shares…
ncaq/konoka · plugins/log-analyzer/skills/log-analyzer/SKILL.md · Extract key information from verbose command output. Use when you want to keep main conversation context lean.
