alibabacloud-ecs-windows-online-troubleshooting
Use this skill whenever the user reports a problem with a Windows system, Windows Server, or Windows ECS instance, or asks to check, diagnose, inspect, or troubleshoot anything Windows-related. Covers network issues (ping, DNS, DHCP, firewall, SMB), RDP/remote desktop (connection failures, authentication, black screen, lag), storage/disk, system activation, Windows Update, performance slowdowns, user accounts/permissions, drivers, app crashes, security/certificate/TLS, scheduled tasks, or vague requests like 'check the system' or 'something is wrong.' Load this skill even if the user does not
npx skills add aliyun/alibabacloud-ecs-troubleshoot-skills --skill alibabacloud-ecs-windows-online-troubleshooting --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Windows ECS 在线诊断 Skill ## 何时使用本技能 当用户报告 Windows 实例的故障现象，或要求对 Windows 实例进行问题排查、状态检查时，加载本技能。覆盖范围包括： - 网络问题：ping、DNS、DHCP、防火墙、SMB - RDP/远程桌面：连接失败、认证、黑屏、卡顿 - 存储/磁盘、系统激活、Windows Update、性能问题 - 用户账户/权限、驱动、应用崩溃、安全/证书/TLS、计划任务 - 模糊描述如“检查一下系统”或“系统有问题” 诊断能力清单和问题路由表存放在 `references/REFERENCE.md` 中，在路径规划阶段加载。 --- ## 诊断执行流程 ### 用户呈现通用规则 执行过程中向用户呈现进度、排查路径、当前步骤等信息时，**禁止暴露 Skill 内部标记**，必须用自然语言描述该步骤所对应的诊断功能。需隐藏的内部标记包括但不限于： - **内部文件名 / 路径**：如 `references/REFERENCE.md`、`references/rdp-service.md`、`references/networking-tcpip.md` 等 - **内部术语**：如「路由表」「reference」「推测性排查」「动态规划」「step 集合」「事件日志预诊断」 等 Skill 设计概念 - **内部编号 / 标签**：如 `Step 1`、`Step 2` 等机械编号，以及 `Direct/Contributing/Unrelated`、`Critical/Warning/Info`、`MUST` 等词汇的原始字样 - **工具调用详情**：如「调用 ReadReference / 加载 xxx 文件」之类的实现描述 **示例**： - 不要说：「现在执行 rdp-service.md 的步骤」「本问题为 Direct + Critical」 - 改为说：「现在检查 TermService 服务状态与 RDP 监听端口配置」「此问题是直接根因且严重影响连接」 内部标记仅用于工具调用、日志与模型内部推理，**不进入**对话面向用户的文本。 ### 问题理解 1. 提取用户问题中的核心现象（错误代码、提示信息、用户操作） 2. 确认关键上下文：系统能否启动？当前执行环境（控制台/RDP/云助手）？ 3. **信息不足时 MUST 先向用户追问**（具体现象、错误提示、操作时机等），收集到足够信息后再进入路径规划阶段 4. 记录原始问题描述，后续所有分析 MUST 围绕此问题 ### 路径规划 1. **加载诊断能力与路由表**：读取 `references/REFERENCE.md`，获取诊断能力清单和问题路由表 2. **事件日志预诊断**（可选）： - 采集用户报告时间段内的关键事
- 何时使用本技能
- 诊断执行流程
- 用户呈现通用规则
- 问题理解
- 路径规划
- 逐步执行
- 因果链分析
- 修复方案
- 因果链输出规范
- 因果链示例
- 修复脚本模板
- 诊断结论输出模板
- Gotchas（易错点）
- 诊断阶段
What does the alibabacloud-ecs-windows-online-troubleshooting skill do?
Use this skill whenever the user reports a problem with a Windows system, Windows Server, or Windows ECS instance, or asks to check, diagnose, inspect, or troubleshoot anything Windows-related. Covers network issues (ping, DNS, DHCP, firewall, SMB), RDP/remote desktop (connection failures, authentication, black screen, lag), storage/disk, system activation, Windows Update, performance slowdowns, user accounts/permissions, drivers, app crashes, security/certificate/TLS, scheduled tasks, or vague requests like 'check the system' or 'something is wrong.' Load this skill even if the user does not
How do I install it?
Run `npx skills add aliyun/alibabacloud-ecs-troubleshoot-skills --skill alibabacloud-ecs-windows-online-troubleshooting --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aliyun/alibabacloud-ecs-troubleshoot-skills, a repository with 160 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.