Agent skill · Audited from source
Log Analyzer
skill · laolaoshiren/claude-code-skills-zhMIT licenceAudited 19 Oct 2026 · source 7d69626375c6
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 7d69626375c6 and found no filesystem, network or shell access and no hard-coded secrets. What it does: 日志分析助手 — 智能解析日志文件,识别异常模式,定位问题根因
Cite
Cite this page
ModelsAtlas. “Log Analyzer (laolaoshiren/claude-code-skills-zh)”. Retrieved 19 Oct 2026. https://modelsatlas.com/skills/laolaoshiren/log-analyzer
Trust audit
Audit 0.4.1 · source read 19 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 7d69626375c6 · 19 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherlaolaoshiren GitHub userOwner of the repository this skill is read from
- Source folderlaolaoshiren/claude-code-skills-zh/skills/log-analyzerThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict7d69626375c6A new audit runs when the source changes
- Repository statusNot archivedPushed today
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: 日志分析助手 — 智能解析日志文件,识别异常模式,定位问题根因
--- name: log-analyzer description: 日志分析助手 — 智能解析日志文件,识别异常模式,定位问题根因 --- # 📋 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. 生成分析报告 ```markdown ## 📊 日志分析报告 ### 概览 - 时间范围: 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、手机号等) - 大文件分块处理,避免内存溢出 - 时区统一处理 - 不要臆造日志中不存在的信息
Excerpt, first 1,418 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 7d69626
git clone https://github.com/laolaoshiren/claude-code-skills-zh git -C claude-code-skills-zh checkout 7d69626375c6
The author documents no install command, so this uses the repository directly. Our verdict covers commit 7d69626375c6 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
7d69626375c6
Similar skills
All coding & review skills →laolaoshiren/claude-code-skills-zh
依据真实 OpenAPI、路由实现和现有测试生成并验证 API 测试。用于用户要求测试接口、补集成测试、验证 API 契约、生成回归用例或排查接口兼容性时;区分“生成测试”和“执行请求”的授权,不猜测状态码、响应结构或 SLA,不在未确认环境中发送写请求。
laolaoshiren/claude-code-skills-zh
Changelog 生成器 - 从 Git 历史自动生成 CHANGELOG
laolaoshiren/claude-code-skills-zh
数据库迁移助手 - Schema 对比、迁移脚本生成
laolaoshiren/claude-code-skills-zh
审计 Node.js、Python、Go、Rust、JVM、Ruby 项目的依赖漏洞、版本健康度与许可证事实;当用户要求检查 package.json、lockfile、requirements、go.mod、Cargo.toml、pom.xml、Gemfile.lock,或生成不改依赖的中文审计报告时使用
laolaoshiren/claude-code-skills-zh
项目目录结构地图 - 生成带说明的可视化目录树,快速理解任意代码库
laolaoshiren/claude-code-skills-zh
环境变量管理器:扫描、校验、同步 .env 文件,生成安全配置模板
Questions about Log Analyzer
What does the Log Analyzer skill do?
Is Log Analyzer safe to install?
What can Log Analyzer access on my machine?
How current is this page?
Sources
- github.com/laolaoshiren/claude-code-skills-zh/tree/main/skills/l — the audited source at commit 7d69626375c6 and every finding aboveObserved · 19 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Log Analyzer skill do?
- Is Log Analyzer safe to install?
- What can Log Analyzer access on my machine?