Not in the top 1,000 by GitHub stars
microsoft/win-dev-skills
Agent plugins for building Windows apps with GitHub Copilot, Claude Code, OpenAI Codex, and more.
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
plugins/windbg/skills/windbg-diagnostic-method/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Local scripts → After Local scripts
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Local scripts
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
plugins/windbg/skills/windbg-kernel-bugcheck-triage/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
plugins/windbg/skills/windbg-kernel-irp-lifecycle-triage/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
plugins/windbg/skills/windbg-kernel-lock-deadlock-triage/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
plugins/windbg/skills/windbg-kernel-verifier-triage/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
plugins/windbg/skills/windbg-user-exception-triage/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
plugins/windbg/skills/windbg-user-heap-corruption-investigation/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
plugins/windbg/skills/windbg-user-mutex-held-across-co-await/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
plugins/windbg/skills/windbg-user-ttd-reverse-debugging-triage/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
plugins/windbg/skills/windbg-user-virtual-memory-exhaustion/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
plugins/windbg/skills/windbg-user-wait-chain-analysis/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
scripts/tests/fixtures/local-plugin/plugins/sample/skills/sample-skill/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
5ce74fa89c49 → 5ce74fa89c49
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 5ce74fa89c49
No earlier version was observed for comparison.
Verified commit 5ce74fa89c49ca353c6ab03bd5889aa519aa9e5e
git clone --filter=blob:none --no-checkout https://github.com/microsoft/win-dev-skills.git .hotskills/microsoft-win-dev-skills && git -C .hotskills/microsoft-win-dev-skills checkout --detach 5ce74fa89c49ca353c6ab03bd5889aa519aa9e5e
# Copy each selected skill directory from .hotskills/microsoft-win-dev-skills into .claude/skills/<skill-name>/Heat
6.4- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
30-day change not yet available: not enough history.
Individual skills in this repository
- windbg-diagnostic-method
plugins/windbg/skills/windbg-diagnostic-method - windbg-kernel-bugcheck-triage
plugins/windbg/skills/windbg-kernel-bugcheck-triage - windbg-kernel-irp-lifecycle-triage
plugins/windbg/skills/windbg-kernel-irp-lifecycle-triage - windbg-kernel-lock-deadlock-triage
plugins/windbg/skills/windbg-kernel-lock-deadlock-triage - windbg-kernel-verifier-triage
plugins/windbg/skills/windbg-kernel-verifier-triage - windbg-user-exception-triage
plugins/windbg/skills/windbg-user-exception-triage - windbg-user-heap-corruption-investigation
plugins/windbg/skills/windbg-user-heap-corruption-investigation - windbg-user-mutex-held-across-co-await
plugins/windbg/skills/windbg-user-mutex-held-across-co-await - windbg-user-ttd-reverse-debugging-triage
plugins/windbg/skills/windbg-user-ttd-reverse-debugging-triage - windbg-user-virtual-memory-exhaustion
plugins/windbg/skills/windbg-user-virtual-memory-exhaustion - windbg-user-wait-chain-analysis
plugins/windbg/skills/windbg-user-wait-chain-analysis - sample-skill
scripts/tests/fixtures/local-plugin/plugins/sample/skills/sample-skill
How it works
windbg-diagnostic-method
When your agent uses it
Use with every WinDbg plugin investigation to apply evidence-first reasoning, confidence calibration, contrarian review, structured reporting, and deterministic validation. Not a bug-family-specific triage skill.
What it loads into context
Frontmatter
52 tokensAlways available to the agent
SKILL.md
1,730 tokensWhen the skill is activated
Reference documents
45 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Evidence ladder
- First-pass normalization
- Five-phase investigation
- Routing index
- Routing depth
- Trigger and fix gates
- Fix-confidence calibration
- Independent review
- Report contract
- Deterministic report validation
- Safety and privacy
- Feedback
Scripts executed separately
scripts/validate-diagnosis-output.ps1
Files
../../../../.claude-plugin/marketplace.jsonasset2,926 bytes../../.claude-plugin/plugin.jsonasset550 bytesSKILL.mdcore7,775 bytesSKILL.mdcore7,775 bytesSKILL.mdcore7,775 bytesSKILL.mdcore7,775 bytesSKILL.mdcore7,775 bytesscripts/validate-diagnosis-output.ps1runs4,958 bytes../../../../scripts/tests/fixtures/local-plugin/.claude-plugin/marketplace.jsonasset256 bytes../../../../scripts/tests/fixtures/local-plugin/plugins/sample/.claude-plugin/plugin.jsonasset86 bytes../../../../scripts/tests/fixtures/local-plugin/plugins/sample/plugin.jsonasset161 bytes../../../../scripts/tests/fixtures/local-plugin/plugins/sample/skills/sample-skill/SKILL.mddoc207 bytes
Read SKILL.md
# WinDbg Diagnostic Method
Apply this method alongside the bug-family-specific skill selected for an
investigation. Pattern matches route the investigation; they do not prove the
root cause.
## Evidence ladder
Prefer direct evidence in this order:
1. Faulting instruction/context, bugcheck or exception parameters, and resource
owners/waiters from the actual dump or trace.
2. Matching symbols and the user's authorized source for the involved build.
3. Allocation/free, Verifier, IRP, lock, ETW, WCT, or TTD history captured for
the same failure.View the complete source on GitHubwindbg-kernel-bugcheck-triage
When your agent uses it
Use when a kernel dump reports a Windows bugcheck; decode parameters and recover exception or trap context before investigating your driver. Not for user-mode process crashes or blaming a module from its name alone.
What it loads into context
Frontmatter
55 tokensAlways available to the agent
SKILL.md
1,245 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Scope
- Workflow
- Validation
- References
- Feedback
Files
SKILL.mdcore5,268 bytesSKILL.mdcore5,268 bytesSKILL.mdcore5,268 bytes
Read SKILL.md
# Kernel Bugcheck Triage
**Load `windbg-diagnostic-method` first** if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
## Scope
Use a kernel crash dump or authorized live kernel session. A process dump
captured after a reboot does not contain the earlier kernel fault. Confirm
the dump type with the debugger, not a filename or the user's visible symptom.
This skill includes exception-context and trap-frame recovery.
View the complete source on GitHubwindbg-kernel-irp-lifecycle-triage
When your agent uses it
Use when kernel evidence shows stalled I/O, a power IRP, or completion/cancellation misuse; inspect request state and driver ownership. Not for interpreting an empty IRP search in a limited dump as proof of healthy I/O.
What it loads into context
Frontmatter
63 tokensAlways available to the agent
SKILL.md
948 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Scope
- Workflow
- Validation
- References
- Feedback
Files
SKILL.mdcore4,324 bytesSKILL.mdcore4,324 bytes
Read SKILL.md
# IRP Lifecycle Triage
**Load `windbg-diagnostic-method` first** if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
## Scope
Investigate I/O Request Packets in a kernel dump or authorized live kernel
session. Examples include `0x9F` power failures and hangs where progress
depends on a driver request. Apply the parameter table for the specific
bugcheck subtype rather than assuming every `0x9F` identifies the same object.
View the complete source on GitHubwindbg-kernel-lock-deadlock-triage
When your agent uses it
Use when kernel threads block on driver synchronization or Verifier reports a lock-order violation; build an owner/waiter graph. Not for treating every watchdog stop as a deadlock or listing every lock type with !locks.
What it loads into context
Frontmatter
61 tokensAlways available to the agent
SKILL.md
912 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Detection
- Workflow
- Fix patterns
- Validation
- References
- Feedback
Files
SKILL.mdcore4,297 bytesSKILL.mdcore4,297 bytes
Read SKILL.md
# Kernel Lock and Deadlock Triage
**Load `windbg-diagnostic-method` first** if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
## Detection
Use kernel thread stacks, synchronization-object evidence, and Driver Verifier
deadlock records. A watchdog bugcheck can indicate CPU/DPC progress failures,
not necessarily a lock cycle. Establish the actual waits before choosing this
workflow.
View the complete source on GitHubwindbg-kernel-verifier-triage
When your agent uses it
Use when a kernel dump contains Driver Verifier violations; inspect flags, bugcheck subcodes, and available I/O shadow state. Not for Application Verifier user-mode stops or inferring a violation from enabled flags alone.
What it loads into context
Frontmatter
59 tokensAlways available to the agent
SKILL.md
972 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Scope
- Workflow
- Controlled repro
- Validation
- References
- Feedback
Files
SKILL.mdcore4,459 bytes
Read SKILL.md
# Driver Verifier Triage
**Load `windbg-diagnostic-method` first** if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
## Scope
Driver Verifier checks kernel driver contracts. Application Verifier is a
different user-mode facility; use `windbg-user-heap-corruption-investigation` for its heap
stops. Enabled Driver Verifier flags alone do not prove a contract violation.
Use this skill when a verifier-class bugcheck or analysis identifies an actualView the complete source on GitHubwindbg-user-exception-triage
When your agent uses it
Use when a native C/C++ app, service, or user-mode driver host (including UMDF) crashes with a structured exception in a dump or WinDbg session, including native faults inside managed processes. Not for managed .NET exceptions, WinUI/XAML app errors, or kernel bugchecks.
What it loads into context
Frontmatter
74 tokensAlways available to the agent
SKILL.md
1,142 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- When to use
- Workflow
- Validation
- References
- Feedback
Files
SKILL.mdcore5,132 bytesSKILL.mdcore5,132 bytesSKILL.mdcore5,132 bytes
Read SKILL.md
# User-Mode Exception Triage
**Load `windbg-diagnostic-method` first** if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
## When to use
Start here for access violations, heap corruption, stack overflow, fail-fast,
breakpoints, and other structured exceptions in a native application, service,
or user-mode driver host process dump. This includes UMDF driver failures that
occur in their user-mode host. Confirm
the dump type from WinDbg; the filename extension alone does not distinguishView the complete source on GitHubwindbg-user-heap-corruption-investigation
When your agent uses it
Use when an app, service, or user-mode driver host heap fails or Application Verifier detects corruption; inspect history and bounds. Not for kernel pool corruption or ordinary OOM.
What it loads into context
Frontmatter
51 tokensAlways available to the agent
SKILL.md
1,133 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Detection and limits
- Workflow
- Fix patterns
- Validation
- References
- Feedback
Files
SKILL.mdcore5,320 bytes
Read SKILL.md
# Heap Corruption Investigation
**Load `windbg-diagnostic-method` first** if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
## Detection and limits
Look for `STATUS_HEAP_CORRUPTION` (`0xC0000374`), Application Verifier stops,
or failures in heap allocate/free/reallocate paths in an application, service,
or user-mode driver host such as an UMDF host process. A crash inside the allocator
may be the first detection of an earlier bad write, not the faulty operation.
Distinguish corruption from allocation failure; for the latter useView the complete source on GitHubwindbg-user-mutex-held-across-co-await
When your agent uses it
Use when app, service, or user-mode driver C++ coroutine code holds a thread-affine lock across suspension and later hangs or fails. Not for all coroutine crashes or choosing lock performance.
What it loads into context
Frontmatter
54 tokensAlways available to the agent
SKILL.md
879 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Detection
- Workflow
- Fix pattern
- Validation
- References
- Feedback
Files
SKILL.mdcore4,245 bytesSKILL.mdcore4,245 bytes
Read SKILL.md
# Mutex Held Across co_await
**Load `windbg-diagnostic-method` first** if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
## Detection
This pattern can occur in native application, service, or user-mode driver
code, including UMDF components that use C++ coroutines. Look for a lock
acquired before `co_await` and released after resumption or
coroutine destruction. Mutex ownership belongs to the acquiring thread, not
the coroutine frame. A resumption on another thread can violate that contract.View the complete source on GitHubwindbg-user-ttd-reverse-debugging-triage
When your agent uses it
Use when an app, service, or user-mode driver host TTD recording is available and earlier calls, writes, or lifetimes matter. Not for kernel replay or history from a normal dump.
What it loads into context
Frontmatter
58 tokensAlways available to the agent
SKILL.md
959 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Requirements and scope
- Workflow
- Validation
- References
- Feedback
Files
SKILL.mdcore4,472 bytes
Read SKILL.md
# TTD Reverse Debugging Triage
**Load `windbg-diagnostic-method` first** if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
## Requirements and scope
Time Travel Debugging records a user-mode process for replay, including an
authorized application, service, or user-mode driver host process. A dump alone
contains no execution timeline. Confirm a valid recording and matching module
symbols before attempting timeline queries. It does not record kernel execution
or automatically include another process's server-side activity.View the complete source on GitHubwindbg-user-virtual-memory-exhaustion
When your agent uses it
Use when a native app, service, or user-mode driver host allocation fails; distinguish VA exhaustion, fragmentation, and commit pressure. Not for managed .NET heap growth, proving a leak from one snapshot, or corruption.
What it loads into context
Frontmatter
59 tokensAlways available to the agent
SKILL.md
1,085 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Detection
- Workflow
- Fix patterns
- Validation
- References
- Feedback
Files
SKILL.mdcore5,131 bytes
Read SKILL.md
# Virtual Memory Exhaustion
**Load `windbg-diagnostic-method` first** if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
## Detection
Investigate `E_OUTOFMEMORY` (`0x8007000E`), `STATUS_NO_MEMORY` (`0xC0000017`),
`bad_alloc`, or failed heap/virtual allocations in an application, service, or
user-mode driver host (including UMDF). Record the actual API, requested
size/alignment, architecture, flags, and error. Free physical RAM does not rule
out insufficient virtual address space, commit pressure, or applicable limits.View the complete source on GitHubwindbg-user-wait-chain-analysis
When your agent uses it
Use when an app, service, or user-mode driver host is unresponsive on locks, COM/RPC, I/O, or another process; follow the blocker chain. Not for a crash solely from an exception stack.
What it loads into context
Frontmatter
57 tokensAlways available to the agent
SKILL.md
1,066 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Detection
- Workflow
- Fix patterns and COM boundaries
- Validation
- References
- Feedback
Files
SKILL.mdcore4,973 bytesSKILL.mdcore4,973 bytes
Read SKILL.md
# Cross-Process Wait Chain Analysis
**Load `windbg-diagnostic-method` first** if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
## Detection
Look for blocked work in an application, service, or user-mode driver host
(including UMDF), and threads in wait, COM, RPC, or I/O paths.
The process displaying the symptom may not own the underlying defect.
Idle worker threads waiting normally are not evidence of a hang.
View the complete source on GitHubsample-skill
When your agent uses it
Sample skill used to test the catalog tooling. Use when testing CI. Not for real work.
What it loads into context
Frontmatter
27 tokensAlways available to the agent
SKILL.md
45 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
Files
SKILL.mdcore207 bytes
Read SKILL.md
# Sample skill
This skill exists only to exercise the catalog check and lint.View the complete source on GitHubSkills included
- windbg-diagnostic-method
- windbg-kernel-bugcheck-triage
- windbg-kernel-irp-lifecycle-triage
- windbg-kernel-lock-deadlock-triage
- windbg-kernel-verifier-triage
- windbg-user-exception-triage
- windbg-user-heap-corruption-investigation
- windbg-user-mutex-held-across-co-await
- windbg-user-ttd-reverse-debugging-triage
- windbg-user-virtual-memory-exhaustion
- windbg-user-wait-chain-analysis
- sample-skill
Repository facts
- License
- MIT
- Created
- Mar 3, 2026
- Last pushed
- Nov 3, 2026
- Forks
- 39
- Open issues
- 16
- Project activity
- Active
Before you install
Local scriptsAutomated signals, not a guarantee
Checked Nov 5, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 12 notes
plugins/windbg/skills/windbg-diagnostic-method/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedplugins/windbg/skills/windbg-diagnostic-method/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedplugins/windbg/skills/windbg-diagnostic-method/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedplugins/windbg/skills/windbg-diagnostic-method/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedplugins/windbg/skills/windbg-kernel-bugcheck-triage/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedplugins/windbg/skills/windbg-kernel-bugcheck-triage/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedplugins/windbg/skills/windbg-kernel-irp-lifecycle-triage/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedplugins/windbg/skills/windbg-kernel-lock-deadlock-triage/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedplugins/windbg/skills/windbg-user-exception-triage/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedplugins/windbg/skills/windbg-user-exception-triage/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedplugins/windbg/skills/windbg-user-mutex-held-across-co-await/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedplugins/windbg/skills/windbg-user-wait-chain-analysis/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- No broad tool permissions
- No dangerous shell commands
- 94 network referencesin 13 files: .claude-plugin/marketplace.json:3 windbg-kernel-bugcheck-triage/SKILL.md:118 windbg-user-virtual-memory-exhaustion/SKILL.md:102 and 10 more
- No hidden or obfuscated text
- No instruction overrides
- 1 executable scriptin 1 file: windbg-diagnostic-method/scripts/validate-diagnosis-output.ps1:1
- No access to secrets
- No requests to vote in Hot
Show all 95 signals by file
.claude-plugin/marketplace.json
- Network accessline 3
"owner": { "name": "Microsoft", "url": "https://github.com/microsoft/win-dev-skills" - Network accessline 4
"name": "Microsoft", "url": "https://github.com/microsoft/win-dev-skills" }, - Network accessline 5
"url": "https://github.com/microsoft/win-dev-skills" - Network accessline 15
"author": { "name": "Microsoft", "url": "https://github.com/microsoft/WinDbg-Feedback" - Network accessline 16
"name": "Microsoft", "url": "https://github.com/microsoft/WinDbg-Feedback" }, - Network accessline 17
"url": "https://github.com/microsoft/WinDbg-Feedback" - Network accessline 18
}, "homepage": "https://github.com/microsoft/WinDbg-Feedback", "repository": "https://github.com/microsoft/win-dev-skills" - Network accessline 19
"homepage": "https://github.com/microsoft/WinDbg-Feedback", - Network accessline 20
"repository": "https://github.com/microsoft/win-dev-skills" - Network accessline 26
"source": { "source": "git-subdir", "url": "https://github.com/microsoft/winappCli.git", - Network accessline 27
"source": "git-subdir", "url": "https://github.com/microsoft/winappCli.git", "path": "plugins/winui", - Network accessline 28
"url": "https://github.com/microsoft/winappCli.git", - Network accessline 43
"author": { "name": "Microsoft", "url": "https://github.com/microsoft/win-dev-skills" - Network accessline 44
"name": "Microsoft", "url": "https://github.com/microsoft/win-dev-skills" }, - Network accessline 45
"url": "https://github.com/microsoft/win-dev-skills" - Network accessline 46
}, "homepage": "https://github.com/microsoft/win-dev-skills", "repository": "https://github.com/microsoft/winappCli", - Network accessline 47
"homepage": "https://github.com/microsoft/win-dev-skills", - Network accessline 48
"repository": "https://github.com/microsoft/winappCli", - Network accessline 55
"source": { "source": "git-subdir", "url": "https://github.com/microsoft/winappCli.git", - Network accessline 56
"source": "git-subdir", "url": "https://github.com/microsoft/winappCli.git", "path": "plugins/winapp", - Network accessline 57
"url": "https://github.com/microsoft/winappCli.git", - Network accessline 75
"author": { "name": "Microsoft", "url": "https://github.com/microsoft/winappCli" - Network accessline 76
"name": "Microsoft", "url": "https://github.com/microsoft/winappCli" }, - Network accessline 77
"url": "https://github.com/microsoft/winappCli" - Network accessline 78
}, "homepage": "https://github.com/microsoft/winappCli", "repository": "https://github.com/microsoft/winappCli", - Network accessline 79
"homepage": "https://github.com/microsoft/winappCli", - Network accessline 80
"repository": "https://github.com/microsoft/winappCli",
plugins/windbg/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "Microsoft", "url": "https://github.com/microsoft/WinDbg-Feedback" - Network accessline 6
"name": "Microsoft", "url": "https://github.com/microsoft/WinDbg-Feedback" }, - Network accessline 7
"url": "https://github.com/microsoft/WinDbg-Feedback" - Network accessline 8
}, "homepage": "https://github.com/microsoft/WinDbg-Feedback", "repository": "https://github.com/microsoft/win-dev-skills", - Network accessline 9
"homepage": "https://github.com/microsoft/WinDbg-Feedback", - Network accessline 10
"repository": "https://github.com/microsoft/win-dev-skills",
plugins/windbg/skills/windbg-diagnostic-method/scripts/validate-diagnosis-output.ps1
- Executable scriptline 1
Executable file
plugins/windbg/skills/windbg-kernel-bugcheck-triage/SKILL.md
- Network accessline 118
- [Bugcheck reference](https://learn.microsoft.com/windows-hardware/drivers/debugger/bug-check-code-reference2) - Network accessline 119
- [0x3B SYSTEM_SERVICE_EXCEPTION](https://learn.microsoft.com/windows-hardware/drivers/debugger/bug-check-0x3b--system-service-exception) - Network accessline 120
- [0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED](https://learn.microsoft.com/windows-hardware/drivers/debugger/bug-check-0x7e--system-thread-exception-not-handled) - Network accessline 121
- [Context record](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-cxr--display-context-record-) - Network accessline 122
- [Trap frame](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-trap--display-trap-frame-) - Network accessline 126
Follow `FEEDBACK.md` and submit only reviewed, sanitized feedback to [WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues). - Network accessline 127
[WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues).
plugins/windbg/skills/windbg-kernel-irp-lifecycle-triage/SKILL.md
- Network accessline 91
- [IRP inspection](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-irp) - Network accessline 92
- [IRP search](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-irpfind) - Network accessline 93
- [0x9F power-state failure](https://learn.microsoft.com/windows-hardware/drivers/debugger/bug-check-0x9f--driver-power-state-failure) - Network accessline 94
- [Canceling IRPs](https://learn.microsoft.com/windows-hardware/drivers/kernel/canceling-irps) - Network accessline 98
Follow `FEEDBACK.md` and report only reviewed, sanitized feedback to [WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues). - Network accessline 99
[WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues).
plugins/windbg/skills/windbg-kernel-lock-deadlock-triage/SKILL.md
- Network accessline 95
- [ERESOURCE locks extension](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-locks) - Network accessline 96
- [Deadlock extension](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-deadlock) - Network accessline 97
- [Driver Verifier deadlock detection](https://learn.microsoft.com/windows-hardware/drivers/devtest/deadlock-detection) - Network accessline 98
- [Thread inspection](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-thread) - Network accessline 102
Follow `FEEDBACK.md` and report reviewed, sanitized feedback to [WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues). - Network accessline 103
[WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues).
plugins/windbg/skills/windbg-kernel-verifier-triage/SKILL.md
- Network accessline 97
- [Driver Verifier](https://learn.microsoft.com/windows-hardware/drivers/devtest/driver-verifier) - Network accessline 98
- [Verifier extension](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-verifier) - Network accessline 99
- [I/O verifier IRP extension](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-iovirp) - Network accessline 100
- [0xC4 verifier violation](https://learn.microsoft.com/windows-hardware/drivers/debugger/bug-check-0xc4--driver-verifier-detected-violation) - Network accessline 104
Follow `FEEDBACK.md` and submit reviewed, sanitized feedback to [WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues). - Network accessline 105
[WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues).
plugins/windbg/skills/windbg-user-exception-triage/SKILL.md
- Network accessline 89
- [Exception context](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-ecxr--display-exception-context-record-) - Network accessline 90
- [Exception record](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-exr--display-exception-record-) - Network accessline 91
- [Controlling exceptions and events](https://learn.microsoft.com/windows-hardware/drivers/debugger/controlling-exceptions-and-events) - Network accessline 95
For this skill, follow the plugin's `FEEDBACK.md` and report a reviewed, sanitized issue to [WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues). - Network accessline 96
issue to [WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues).
plugins/windbg/skills/windbg-user-heap-corruption-investigation/SKILL.md
- Network accessline 114
- [Application Verifier stop definitions](https://learn.microsoft.com/windows-hardware/drivers/devtest/application-verifier-stop-codes-and-definitions) - Network accessline 115
- [Heap extension](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-heap) - Network accessline 116
- [Application Verifier extension](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-avrf) - Network accessline 117
- [GFlags and Page Heap](https://learn.microsoft.com/windows-hardware/drivers/debugger/gflags-and-pageheap) - Network accessline 121
Follow `FEEDBACK.md` and report reviewed, sanitized feedback to [WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues). - Network accessline 122
[WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues).
plugins/windbg/skills/windbg-user-mutex-held-across-co-await/SKILL.md
- Network accessline 77
- [Holding a lock across coroutine suspension](https://devblogs.microsoft.com/oldnewthing/20210707-00/?p=105417) - Network accessline 78
- [C++/WinRT concurrency and asynchronous operations](https://learn.microsoft.com/windows/uwp/cpp-and-winrt-apis/concurrency) - Network accessline 79
- [Slim reader/writer locks](https://learn.microsoft.com/windows/win32/sync/slim-reader-writer--srw--locks) - Network accessline 83
Follow `FEEDBACK.md` and report reviewed, sanitized feedback to [WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues). - Network accessline 84
[WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues).
plugins/windbg/skills/windbg-user-ttd-reverse-debugging-triage/SKILL.md
- Network accessline 95
- [Time Travel Debugging overview](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/time-travel-debugging-overview) - Network accessline 96
- [TTD data-model queries](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/time-travel-debugging-object-model) - Network accessline 97
- [TTD extension commands](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/time-travel-debugging-extension-commands) - Network accessline 101
Follow `FEEDBACK.md` and report a reviewed summary to [WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues). - Network accessline 102
[WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues).
plugins/windbg/skills/windbg-user-virtual-memory-exhaustion/SKILL.md
- Network accessline 102
- [Address extension](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-address) - Network accessline 103
- [Heap extension](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-heap) - Network accessline 104
- [Windows memory limits](https://learn.microsoft.com/windows/win32/memory/memory-limits-for-windows-releases) - Network accessline 105
- [Large-address-aware linker option](https://learn.microsoft.com/cpp/build/reference/largeaddressaware-handle-large-addresses) - Network accessline 106
- [VirtualFree](https://learn.microsoft.com/windows/win32/api/memoryapi/nf-memoryapi-virtualfree) - Network accessline 110
Follow `FEEDBACK.md` and submit reviewed, sanitized feedback to [WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues). - Network accessline 111
[WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues).
plugins/windbg/skills/windbg-user-wait-chain-analysis/SKILL.md
- Network accessline 105
- [Wait Chain Traversal](https://learn.microsoft.com/windows/win32/debug/wait-chain-traversal) - Network accessline 106
- [Processes, threads, and COM apartments](https://learn.microsoft.com/windows/win32/com/processes--threads--and-apartments) - Network accessline 107
- [Process inspection](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-process) - Network accessline 108
- [Thread inspection](https://learn.microsoft.com/windows-hardware/drivers/debuggercmds/-thread) - Network accessline 112
Follow `FEEDBACK.md` and submit only reviewed, sanitized feedback to [WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues). - Network accessline 113
[WinDbg-Feedback](https://github.com/microsoft/WinDbg-Feedback/issues).
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
Signal confidence: 60 facts
- Executable script in code of a file that runswindbg-diagnostic-method/scripts/validate-diagnosis-output.ps1:1High confidence
- Network access in prose of the SKILL.mdwindbg-kernel-bugcheck-triage/SKILL.md:118Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-bugcheck-triage/SKILL.md:119Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-bugcheck-triage/SKILL.md:120Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-bugcheck-triage/SKILL.md:121Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-bugcheck-triage/SKILL.md:122Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-bugcheck-triage/SKILL.md:126Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-bugcheck-triage/SKILL.md:127Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-irp-lifecycle-triage/SKILL.md:91Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-irp-lifecycle-triage/SKILL.md:92Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-irp-lifecycle-triage/SKILL.md:93Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-irp-lifecycle-triage/SKILL.md:94Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-irp-lifecycle-triage/SKILL.md:98Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-irp-lifecycle-triage/SKILL.md:99Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-lock-deadlock-triage/SKILL.md:95Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-lock-deadlock-triage/SKILL.md:96Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-lock-deadlock-triage/SKILL.md:97Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-lock-deadlock-triage/SKILL.md:98Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-lock-deadlock-triage/SKILL.md:102Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-lock-deadlock-triage/SKILL.md:103Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-verifier-triage/SKILL.md:97Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-verifier-triage/SKILL.md:98Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-verifier-triage/SKILL.md:99Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-verifier-triage/SKILL.md:100Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-verifier-triage/SKILL.md:104Low confidence
- Network access in prose of the SKILL.mdwindbg-kernel-verifier-triage/SKILL.md:105Low confidence
- Network access in prose of the SKILL.mdwindbg-user-exception-triage/SKILL.md:89Low confidence
- Network access in prose of the SKILL.mdwindbg-user-exception-triage/SKILL.md:90Low confidence
- Network access in prose of the SKILL.mdwindbg-user-exception-triage/SKILL.md:91Low confidence
- Network access in prose of the SKILL.mdwindbg-user-exception-triage/SKILL.md:95Low confidence
- Network access in prose of the SKILL.mdwindbg-user-exception-triage/SKILL.md:96Low confidence
- Network access in prose of the SKILL.mdwindbg-user-heap-corruption-investigation/SKILL.md:114Low confidence
- Network access in prose of the SKILL.mdwindbg-user-heap-corruption-investigation/SKILL.md:115Low confidence
- Network access in prose of the SKILL.mdwindbg-user-heap-corruption-investigation/SKILL.md:116Low confidence
- Network access in prose of the SKILL.mdwindbg-user-heap-corruption-investigation/SKILL.md:117Low confidence
- Network access in prose of the SKILL.mdwindbg-user-heap-corruption-investigation/SKILL.md:121Low confidence
- Network access in prose of the SKILL.mdwindbg-user-heap-corruption-investigation/SKILL.md:122Low confidence
- Network access in prose of the SKILL.mdwindbg-user-mutex-held-across-co-await/SKILL.md:77Low confidence
- Network access in prose of the SKILL.mdwindbg-user-mutex-held-across-co-await/SKILL.md:78Low confidence
- Network access in prose of the SKILL.mdwindbg-user-mutex-held-across-co-await/SKILL.md:79Low confidence
- Network access in prose of the SKILL.mdwindbg-user-mutex-held-across-co-await/SKILL.md:83Low confidence
- Network access in prose of the SKILL.mdwindbg-user-mutex-held-across-co-await/SKILL.md:84Low confidence
- Network access in prose of the SKILL.mdwindbg-user-ttd-reverse-debugging-triage/SKILL.md:95Low confidence
- Network access in prose of the SKILL.mdwindbg-user-ttd-reverse-debugging-triage/SKILL.md:96Low confidence
- Network access in prose of the SKILL.mdwindbg-user-ttd-reverse-debugging-triage/SKILL.md:97Low confidence
- Network access in prose of the SKILL.mdwindbg-user-ttd-reverse-debugging-triage/SKILL.md:101Low confidence
- Network access in prose of the SKILL.mdwindbg-user-ttd-reverse-debugging-triage/SKILL.md:102Low confidence
- Network access in prose of the SKILL.mdwindbg-user-virtual-memory-exhaustion/SKILL.md:102Low confidence
- Network access in prose of the SKILL.mdwindbg-user-virtual-memory-exhaustion/SKILL.md:103Low confidence
- Network access in prose of the SKILL.mdwindbg-user-virtual-memory-exhaustion/SKILL.md:104Low confidence
and 10 more
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Manifest .claude-plugin/marketplace.json | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md plugins/windbg/skills/windbg-diagnostic-method/SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md plugins/windbg/skills/windbg-diagnostic-method/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md plugins/windbg/skills/windbg-diagnostic-method/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md plugins/windbg/skills/windbg-diagnostic-method/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md plugins/windbg/skills/windbg-diagnostic-method/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.