windbg-preview
Use when triaging Windows crash dumps, inspecting threads, exceptions, modules, memory, or debugger commands against dump files such as .dmp artifacts before deeper disassembler work.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- windbg-preview
- description
- Use when triaging Windows crash dumps, inspecting threads, exceptions, modules, memory, or debugger commands against dump files such as .dmp artifacts before deeper disassembler work.
02 资源文件 2
- 参考文档agents/openai.yaml228 B
- 参考文档references/upstream.md477 B
03 SKILL.md 正文
WinDbg Preview
Overview
Use WinDbg Preview as the first tool for normal Windows dump triage. It is the fastest way to answer: what crashed, which thread matters, which modules were loaded, and what addresses are worth carrying into a disassembler.
Quick Workflow
- Launch
windbg-previewand open the target dump. - Start with exception context, stack, active threads, and loaded modules before exploring raw memory.
- Copy the exact module names, offsets, and thread IDs that look interesting.
- Move those addresses into IDA Pro, Binary Ninja, or Ghidra only after the dump-side evidence is stable.
- Use Volatility 3 only when you specifically need a memory-forensics workflow instead of a normal debugger-centric dump review.
Common Mistakes
- Jumping to static analysis before confirming the exception and owning thread.
- Treating WinDbg as a decompiler replacement instead of a triage front-end.
- Using Volatility first for a normal Windows application dump.
Reference Map
Read references/upstream.md for the local launch command and the SWFOC dump path already staged on this workstation.
04 同仓库更多 Skills
clarify-requirements
Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.
openmm-md
Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein / protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.
visual-review
Take screenshots of web pages and UI using Playwright for visual review and iteration
status
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
start
Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work
setup
Interactive project setup — detects your project, configures metaswarm, writes project-local files