# Debugview

> Debugview is an open-source agent skill. Sysinternals DebugView CLI (DbgViewCli) for capturing and analyzing usermode and kernel-mode Windows debug output from the command line. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.

- **Kind:** Skill
- **Pricing:** Open source
- **Platforms:** Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- **Website:** https://github.com/microsoft/skills/tree/main/.github/skills/debugview
- **Repository:** https://github.com/microsoft/skills
- **GitHub stars:** 3,214
- **License:** MIT
- **Skill name:** debugview
- **Collection:** https://github.com/microsoft/skills
- **Listing updated:** 2026-11-17

## About

Sysinternals DebugView CLI (DbgViewCli) for capturing and analyzing usermode and kernel-mode Windows debug output from the command line.
USE FOR: capturing OutputDebugString output, kernel DbgPrint/KdPrint capture, boot-time debug logging, remote debug monitoring, filtering debug output by PID or process name, crash dump analysis, automated debug capture with bounded execution.
DO NOT USE FOR: non-Windows platforms, application-level logging frameworks (log4j, serilog), Azure Monitor or cloud telemetry, ETW tracing (use WPR/xperf instead), user-mode crash dumps (use WinDbg).
Triggers: "debug output", "DbgView", "DebugView", "kernel debug", "capture debug logs", "boot logging", "OutputDebugString", "DbgPrint", "KdPrint", "remote debug monitor", "debug capture CLI".

## When your agent uses it

> Sysinternals DebugView CLI (DbgViewCli) for capturing and analyzing usermode and kernel-mode Windows debug output from the command line. USE FOR: capturing OutputDebugString output, kernel DbgPrint/KdPrint capture, boot-time debug logging, remote debug monitoring, filtering debug output by PID or process name, crash dump analysis, automated debug capture with bounded execution. DO NOT USE FOR: non-Windows platforms, application-level logging frameworks (log4j, serilog), Azure Monitor or cloud telemetry, ETW tracing (use WPR/xperf instead), user-mode crash dumps (use WinDbg). Triggers: "debug output", "DbgView", "DebugView", "kernel debug", "capture debug logs", "boot logging", "OutputDebugString", "DbgPrint", "KdPrint", "remote debug monitor", "debug capture CLI".

## What it can access

From a static check of the files on GitHub; nothing was run.

- [Runs PowerShell scripts](https://github.com/microsoft/skills/tree/HEAD/.github/skills/debugview)
- [No network calls found in its scripts](https://github.com/microsoft/skills/tree/HEAD/.github/skills/debugview)
- [License: MIT](https://github.com/microsoft/skills/tree/HEAD/.github/skills/debugview)

## Install

### Claude Code

Copy the skill folder to `~/.claude/skills/debugview` to use it in all your projects:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/microsoft/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/debugview &&
cp -R "$tmp/.github/skills/debugview" ~/.claude/skills/debugview &&
rm -rf "$tmp"
```

For one project only, put the folder in `.claude/skills/debugview` inside it instead.

### Codex

Copy the skill folder to `~/.agents/skills/debugview` to use it in every repository:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/microsoft/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/debugview &&
cp -R "$tmp/.github/skills/debugview" ~/.agents/skills/debugview &&
rm -rf "$tmp"
```

For one repository only, put the folder in `.agents/skills/debugview` inside it instead.

### Cursor

Copy the skill folder to `~/.cursor/skills/debugview` to use it in every project:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/microsoft/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/debugview &&
cp -R "$tmp/.github/skills/debugview" ~/.cursor/skills/debugview &&
rm -rf "$tmp"
```

For one project only, put the folder in `.cursor/skills/debugview` inside it instead.

### Gemini CLI

Run in a terminal (add `--scope workspace` to install it for the current workspace only):

```sh
gemini skills install https://github.com/microsoft/skills.git --path .github/skills/debugview
```

Or copy the folder to `~/.gemini/skills/debugview` yourself.

### VS Code

For GitHub Copilot in VS Code, copy the skill folder to `~/.copilot/skills/debugview`:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/microsoft/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/debugview &&
cp -R "$tmp/.github/skills/debugview" ~/.copilot/skills/debugview &&
rm -rf "$tmp"
```

For one project only, put the folder in `.github/skills/debugview` inside it instead.

### Other agents

Get the folder:

```sh
git clone --depth 1 https://github.com/microsoft/skills.git
```

Then copy `skills/.github/skills/debugview` into your agent's skills folder as `debugview`. Agents that support SKILL.md read one folder per skill.

## FAQ

### How do I install Debugview in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/debugview to use it in all your projects, or to .claude/skills/debugview in one project.

### Does Debugview run scripts?

Yes. It runs PowerShell scripts. No network calls were found in its scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

### Which AI agents can use Debugview?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

---
Source: https://ai-powered.com/skills/debugview
