x64dbg
Use when live-debugging a Windows process, tracing code paths, setting breakpoints, or pairing with ret-sync and a disassembler. NOT for crash-dump debugging (use windbg-preview).
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- x64dbg
- description
- Use when live-debugging a Windows process, tracing code paths, setting breakpoints, or pairing with ret-sync and a disassembler. NOT for crash-dump debugging (use windbg-preview).
02 资源文件 3
- 参考文档agents/openai.yaml224 B
- 参考文档references/api-endpoints.md19.6 KB
- 参考文档references/upstream.md478 B
03 SKILL.md 正文
x64dbg
Overview
Use x64dbg for fast user-mode debugging on Windows before you commit to heavier static-analysis cleanup. It is the best first live debugger in this stack for breakpoints, stepping, register inspection, and quick attach loops.
Quick Workflow
- Launch
x64dbgand open or attach to the target process. - Set one or two coarse breakpoints first (module entry, hot imports, obvious routines) instead of blanketing the process.
- Capture module bases, interesting addresses, and short notes as soon as you confirm a path.
- Add
$ret-synconly when you already know which code region matters and want disassembler synchronization. - Hand decompiler cleanup or signature generation off to the static-analysis skill that matches the active disassembler.
Common Mistakes
- Treating x64dbg traces as the final artifact instead of copying findings into static notes.
- Starting with too many breakpoints before understanding the module layout.
- Forgetting to capture module base deltas before comparing separate runs.
Reference Map
Read references/upstream.md for local install notes, launch commands, and the expected companion tools in this environment.
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