log-analyzer

log-analyzer is a skill for Claude Code, Codex from laolaoshiren/claude-code-skills-zh. It costs 24 tokens per session (749 once invoked), scanned A, original, MIT.

A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.

In plain words
What is it for?
Use it to filter logs by time, level, source, or service; group similar errors; analyze stack traces and HTTP status codes; and report response-time, memory, or CPU patterns. It supports sources such as files, Docker and Kubernetes logs, journalctl, and cloud logging.
Why use it?
It reduces large volumes of repeated messages into useful groups and connects errors with timing, deployments, traffic peaks, or other events. This makes it easier to investigate incidents and distinguish symptoms from likely root causes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to filter logs by time, level, source, or service; group similar errors; analyze stack traces and HTTP status codes; and report response-time, memory, or CPU patterns. It supports sources such as files, Docker and Kubernetes logs, journalctl, and cloud logging.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/laolaoshiren/claude-code-skills-zh/log-analyzer
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add laolaoshiren/claude-code-skills-zh --skill log-analyzer
Clone the repo
git clone --depth 1 https://github.com/laolaoshiren/claude-code-skills-zh

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for log-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/skills/laolaoshiren/claude-code-skills-zh/log-analyzer/github.svg)](https://agentmods.dev/skills/laolaoshiren/claude-code-skills-zh/log-analyzer)
Your own site
<a href="https://agentmods.dev/skills/laolaoshiren/claude-code-skills-zh/log-analyzer"><img src="https://agentmods.dev/badge/skills/laolaoshiren/claude-code-skills-zh/log-analyzer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for log-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/skills/laolaoshiren/claude-code-skills-zh/log-analyzer"><img src="https://agentmods.dev/badge/skills/laolaoshiren/claude-code-skills-zh/log-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 749 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00749
Opus 5 $0.00012 $0.00375
Sonnet 5 $0.00005 $0.00150
Haiku 4.5 $0.00002 $0.00075

Measured 11d ago against content hash edc38a3a85f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

log-analyzer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/log-analyzer/SKILL.md · 80 lines

What it actually says

📋 log-analyzer — 日志分析助手

触发条件

当用户要求以下操作时激活此技能:

  • 分析应用日志文件(.log, .txt, journalctl 输出等)
  • 排查线上问题和异常
  • 从日志中提取统计信息
  • 生成日志分析报告

工作流程

1. 日志格式识别

自动检测日志格式:

  • 结构化: JSON logs, Logfmt
  • 常见格式: Nginx/Apache access log, Spring Boot, Django, Rails
  • 系统日志: syslog, journalctl, Windows Event Log
  • 自定义格式: 根据正则提取字段

2. 日志预处理

  • 按时间范围过滤(如「最近 1 小时」「今天」)
  • 按日志级别筛选(ERROR, WARN, INFO, DEBUG)
  • 按来源/模块/服务过滤
  • 去重和聚合相似错误

3. 异常模式检测

  • 错误聚类: 将相似错误归为一组,避免重复分析
  • 频率分析: 识别高频错误和突发异常
  • 时间关联: 发现错误是否与特定事件(部署、流量高峰)相关
  • 因果链追踪: 从根因错误到最终表现

4. 关键信息提取

  • 错误堆栈分析(定位源码位置)
  • HTTP 状态码分布(4xx/5xx 比例)
  • 响应时间统计(P50/P95/P99)
  • 内存/CPU 异常指标

5. 生成分析报告

## 📊 日志分析报告

### 概览
- 时间范围: 2024-01-15 10:00 ~ 12:00
- 总日志量: 12,847 条
- 错误数: 234 (1.8%)
- 警告数: 567 (4.4%)

### Top 5 异常
| 排名 | 错误类型 | 次数 | 首次出现 | 最近出现 |
|------|---------|------|---------|---------|
| 1 | NullPointerException | 89 | 10:15 | 11:42 |
| 2 | ConnectionTimeout | 67 | 10:23 | 11:58 |

### 根因分析
最可能的原因:数据库连接池耗尽(线索:连续出现 ConnectionTimeout 后跟大量 NullPointerException)

### 建议
1. 检查数据库连接池配置(当前可能 maxActive 太小)
2. 排查是否存在连接泄漏
3. 添加连接池监控告警

支持的日志来源

  • 文件系统日志(*.log)
  • Docker/Kubernetes 容器日志
  • journalctl 系统日志
  • AWS CloudWatch / GCP Logging
  • ELK Stack (Elasticsearch 查询结果)
  • 应用直接输出的文本

注意事项

  • 敏感信息脱敏(密码、token、手机号等)
  • 大文件分块处理,避免内存溢出
  • 时区统一处理
  • 不要臆造日志中不存在的信息
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 80 lines · 24 tokens per session scan A edc38a3a85f9

Subscribe to this mod's changes

log-analyzer is a skill published in the GitHub repository laolaoshiren/claude-code-skills-zh (828 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 749 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

postmortem-solo

Run a lightweight, blame-free postmortem after an incident, failed launch, or missed deadline — for one person. Use when the user says "that didn't go well", "the launch flopped", "we had an outage", "I missed my deadline", or wants to learn from a recent failure.

rockscy/solo-skills · 68 tokens

bug-from-user

Convert a vague user complaint into a reproducible bug report a solo dev can act on. Use when the user pastes a confusing customer message, says "user says it's broken but I can't repro", "this email makes no sense", or wants to triage a bug report.

rockscy/solo-skills · 60 tokens

tool-calling-tutor

Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.

WenyuChiou/awesome-agentic-ai-zh · 62 tokens

audit

Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to "audit the project", "run a full audit", "project health check", "audit my code", "codebase audit", or "comprehensive review".

tobihagemann/turbo · 71 tokens

investigate

Systematically investigate bugs, test failures, build errors, performance issues, or unexpected behavior by cycling through characterize-isolate-hypothesize-test steps. Use when the user asks to "investigate this bug", "debug this", "figure out why this fails", "find the root cause", "why is this broken"…

tobihagemann/turbo · 107 tokens

consult-oracle

Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches. Use when stuck on a very hard problem, when standard approaches have failed, when multiple debugging attempts haven't worked, or when the user says "ask the oracle", "consult oracle", "consult chatgpt", "I'm completely…

tobihagemann/turbo · 78 tokens