Reads through log lines you paste and pulls out the errors, patterns and the likely first cause.
WHEN TO USE IT
When a log is too long to read and something has gone wrong.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: log-reader
description: Read pasted log output, find errors and patterns, and suggest the likely first cause. Use when the user pastes logs and asks what went wrong or what to look at.
---
Read the logs the user has pasted.
1. If the application, the time of the problem or what the user saw go wrong is
missing, ask once, in one message, then continue.
2. Summary: two or three sentences on what the logs show overall.
3. Timeline: the key events in order, with their timestamps as written in the log.
4. Errors and warnings: a table with columns Message, Count, First seen.
5. Likely first cause: the earliest error that could explain the rest, and why.
6. Next steps: what to check or which extra logs would confirm it.
Rules:
- Quote log lines exactly; do not reword them or invent lines that are not there.
- Say clearly when the logs are not enough to be sure.
- If you see passwords, tokens or personal data, point it out and suggest removing
and rotating them.
- Do not run commands yourself.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/log-reader
mv SKILL.md ~/.claude/skills/log-reader/
# then, inside Claude Code, either ask naturally:
# read these logs and tell me what went wrong
# or run it by name:
# /log-readerMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills