health-check
Skill2 starsChanged 3 months agoMITView on GitHub
This skill should be used when the user asks to perform a comprehensive health check / inspection on Huawei VRP network devices (routers, switches, firewalls), including version, CPU, memory, interface, routing, log, and environment status. Use when the user says "巡检某台设备", "做个体检", "查一下设备状态", "health check", "inspection report".
21 other projects use a version of this.
Adopted by
Most recently taken up by
- codewithmukesh/dotnet-claude-kittheir own version, first seen Nov 8, 2026
- telerik/observability-skillstheir own version, first seen Oct 22, 2026
- allanninal/claude-code-skillstheir own version, first seen Oct 17, 2026
- hosaypeng/claude-skillstheir own version, first seen Oct 13, 2026
- Resgrid/Coretheir own version, first seen Oct 8, 2026
- kubehan/PromAItheir own version, first seen Oct 8, 2026
Used with
Projects with it also use testing.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
NVIDIASkilltesting
Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.
Also in 3 projects that use this
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- zylos-ai/zylos-core★ 1.2ksame name
- codewithmukesh/dotnet-claude-kit★ 808same name
- bitwize-music-studio/claude-ai-music-skills★ 589same name
- Resgrid/Core★ 238same name
- kubehan/PromAI★ 129same name
- hoangsonww/AI-Agents-Orchestrator★ 83same name
- fagemx/edda★ 36same name
- weklund/fiduciary★ 10same name
- aws-samples/sample-aws-ops-skills-for-agents★ 8same name
- link7373/agentic-bi-team★ 4same name
11 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 repository16 other files it gives its agents.
- aaa-auth-configSkill
- attack-defenseSkill
- bgp-configSkill
- ha-hrpSkill
- interface-configSkill
- ipsec-vpnSkill
- mirrorSkill
- nat-configSkill
- ospf-configSkill
- security-policySkill
- ssl-vpnSkill
- stack-istackSkill
- static-routeSkill
- vlan-configSkill
- vrrpSkill
- wlan-ac-configSkill
The file
Files
华为设备综合巡检技能 (health-check)
本技能对华为 VRP 设备执行一键综合体检，覆盖系统层、硬件层、接口层、路由层、安全层、日志层六大维度，自动采集 display 命令输出、分析关键指标、生成结构化巡检报告。
适用：路由器（AR/NE 系列）、交换机（S/CE 系列）、防火墙（USG 系列）。
触发场景
用户描述以下任一需求时加载此技能：
- "帮我巡检一下序号为 X 的设备"
- "对 LL-xcsyy-FW 做个体检"
- "看下这台设备健康状况"
- "device health check / inspection"
- "生成设备巡检报告"
- "查一下 CPU/内存/接口/日志"（综合查询时）
不适用： 单一协议排错（OSPF 邻居不通 → 用 ospf-config）、配置变更（→ 对应配置技能）。
工作流程
Step 1：确认目标设备
需要用户提供：
- 设备序号（对应 user.txt）或设备名/IP
- 巡检深度：快速（5 分钟）/ 标准（10 分钟）/ 深度（含日志分析）
- 输出形式：终端摘要 / Markdown 报告 / 两者
Step 2：登录设备
使用封装脚本 bin/hwssh.sh <序号> '<命令>'，禁止在命令行明文传密。
Step 3：按维度采集
执行 references/inspection-commands.md 中对应深度的命令集，逐条采集输出。
Step 4：分析与判定
对照 references/health-criteria.md 的健康阈值，给每项打 ✓ / ⚠ / ✗。
Step 5：生成报告
按 templates/report-template.md 输出 Markdown 报告，关键项前置告警。
巡检维度（六大类）
1. 系统层
- 设备型号、VRP 版本、运行时长、Patch 状态
- 主控/备控状态、主备一致性
- 时间同步（NTP）
2. 硬件层
- CPU 利用率（5s/1min/5min）
- 内存利用率
- 风扇、电源、温度
- 单板状态、光模块状态
3. 接口层
- 物理 up/down 状态
- 速率/双工/带宽利用率
- CRC/Input Error/Drop 计数
- 光模块收发光功率（阈值告警）
4. 路由层
- 路由表规模（IPv4/IPv6）
- 各协议邻居数（OSPF/BGP/ISIS）
- 默认路由是否存在
5. 安全层（防火墙专属）
- 会话表大小、新建速率
- 安全策略命中统计
- 攻击防范日志
6. 日志层
- 最近 24h ERROR/CRIT 日志数
- 异常事件（接口频繁 up/down、CPU 抖动）
健康判定原则
| 等级 | 标记 | 含义 | 触发条件示例 |
| 健康 | ✓ | 全部正常 | CPU<60%, 内存<70%, 无错包, 无关键日志 |
| 警告 | ⚠ | 需关注 | CPU 60-80%, 接口少量 CRC, 光功率边缘 |
| 异常 | ✗ | 立即处理 | CPU>80%, 接口 down, 风扇故障, 大量 CRIT |
快速入口
| 需求 | 入口 |
| 一键巡检（推荐） | scripts/full_inspection.sh <序号> [--depth quick|standard|deep] |
| 命令清单参考 | references/inspection-commands.md |
| 健康阈值定义 | references/health-criteria.md |
| 报告模板 | templates/report-template.md |
输出示例（摘要）
=== LL-xcsyy-FW 巡检报告 ===
时间: 2026-05-21 21:50:00
型号: USG6307E VRP: V600R007C20SPC600 运行: 43w6d
[✓] 系统层 版本正常, 主备一致, NTP 同步
[✓] 硬件层 CPU 12%, 内存 45%, 温度 38°C, 风扇正常
[⚠] 接口层 GE0/0/3 CRC 错包递增 (近1h +234)
[✓] 路由层 OSPF 邻居 3/3 Full, BGP 邻居 2/2 Established
[✓] 安全层 会话 12k/500k, 无攻击事件
[✓] 日志层 近 24h 无 CRIT 日志
总体: ⚠ 警告 (1 项)
建议: 检查 GE0/0/3 物理链路 / 光模块注意事项
- 巡检命令只读，全部
display/show，不修改设备配置 - 部分命令华为不同型号有差异，脚本会自动适配（USG/S/AR）
- 大表输出（路由表/会话表）只统计数量，不全量拉取
- 深度模式才采集日志，避免大量 IO
关联技能
- 配置变更 →
network-huawei/<协议>-config/ - 设备登录 → 本仓库
bin/hwssh.sh - 跨厂商对比 →
network-cisco/、network-h3c/（规划中）
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.