log-analyzer
Skill907 starsChanged 4 months agoMITView on GitHub
日志分析助手 — 智能解析日志文件，识别异常模式，定位问题根因
13 other projects use a version of this.
Adopted by
Most recently taken up by
- Lethe044/agentskill-kittheir own version, first seen Nov 1, 2026
- nek1987/auto-agent-harnesstheir own version, first seen Oct 11, 2026
- sirius-db/siriustheir own version, first seen Oct 8, 2026
- BryceYuuu/open-workflow-skillstheir own version, first seen Sep 5, 2026
- trac3r00/agent-skillstheir own version, first seen Aug 26, 2026
- THEROCKSSS/hermes-skills-portfoliotheir own version, first seen Aug 3, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- sirius-db/sirius★ 1.1ksame name
- zrt-ai-lab/opencode-skills★ 277same name
- Lethe044/agentskill-kit★ 48same name
- johnqtcg/awesome-skills★ 30same name
- nek1987/auto-agent-harness★ 4same name
- digitaldreams/tuhin★ 3same name
- albertdobmeyer/openskill-forge★ 1same name
- BryceYuuu/open-workflow-skills★ 1same name
- skyvanguard/infra-ops★ 1same name
- THEROCKSSS/hermes-skills-portfolio★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- docs/llms.txtllms.txt
- api-testerSkill
- changelog-genSkill
- db-migratorSkill
- dep-auditorSkill
- ds-mapperSkill
- env-managerSkill
- error-translatorSkill
- eslint-fixSkill
- github-actions-genSkill
- git-workflowSkill
- i18n-helperSkill
- perf-profilerSkill
- refactor-advisorSkill
- security-auditSkill
- skill-curatorSkill
- test-generatorSkill
- zh-code-reviewerSkill
- zh-docgenSkill
- zh-readmeSkill
The file
Files
📋 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、手机号等）
- 大文件分块处理，避免内存溢出
- 时区统一处理
- 不要臆造日志中不存在的信息
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.