local-system-debugging

Validate local Windows paths and detect CLI debuggers before crash dump analysis.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/gaos6e/MyOpenclaw --skill local-system-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-system-debugging
Source: https://github.com/gaos6e/MyOpenclaw/tree/main/workspace/skills/local-system-debugging
Command: npx skills add https://github.com/gaos6e/MyOpenclaw --skill local-system-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill enables host-local Windows troubleshooting by validating access to requested paths and detecting available local debugging tools before declaring failures, reducing false negatives.

Core Features & Use Cases

  • Validate local path accessibility through PowerShell checks prior to operations.
  • Discover installed CLI and GUI debugging tools (e.g., cdb, kd, dumpchk, WinDbg) on the host.
  • Analyze crash dumps when available, using CLI debuggers in a safe, deterministic workflow.
  • Prioritize command-line analysis over GUI instructions and surface exact system errors when a path or tool is inaccessible.

Quick Start

Ask me to check a local path or run a diagnostic on the host and I will verify access and report findings before proceeding.

Frequently Asked Questions about local-system-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze Windows crash dumps from the command line?

It detects installed CLI debuggers like cdb, kd, or dumpchk on your host and executes command-line analysis directly on crash dump files such as C:\Windows\Minidump or MEMORY.DMP.

Why does local system debugging fail when checking paths like Program Files?

Local debugging fails when PowerShell path accessibility checks determine the requested directories are inaccessible, causing the workflow to surface exact system errors rather than proceeding blindly.

Can I use WinDbg to troubleshoot local Windows issues through OpenClaw?

Yes, the skill discovers installed GUI debugging tools like WinDbg on the host, though it prioritizes command-line analysis over GUI instructions to maintain a safe, deterministic diagnostic workflow.

What's the best way to diagnose local Windows system issues before running analysis?

The best way is to validate path accessibility through PowerShell checks and detect available local debugging tools prior to analysis, reducing false negatives before attempting any crash dump inspection.

Do I need PowerShell to verify access to local drives for diagnostics?

Yes, PowerShell scripts are required to run local verification checks that confirm path accessibility and detect available debuggers before attempting any CLI-based analysis on your Windows host.