MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Trace execution (into or over calls) for N steps or until a condition, then analyze the recorded instruction log
MITAuto-check: notes
Install Tracealyzer
$ npx skills add dariushoule/x64dbg-skills --skill tracealyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dariushoule/x64dbg-skills tracealyzer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dariushoule/x64dbg-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tracealyzer .claude/skills/tracealyzer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "tracealyzer" agent skill from https://github.com/dariushoule/x64dbg-skills/tree/main/skills/tracealyzer into .claude/skills/tracealyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracealyzer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dariushoule/x64dbg-skills/tree/main/skills/tracealyzerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dariushoule/x64dbg-skills --skill tracealyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dariushoule/x64dbg-skills tracealyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dariushoule/x64dbg-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tracealyzer .agents/skills/tracealyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tracealyzer" agent skill from https://github.com/dariushoule/x64dbg-skills/tree/main/skills/tracealyzer into .agents/skills/tracealyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracealyzer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dariushoule/x64dbg-skills --skill tracealyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dariushoule/x64dbg-skills tracealyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dariushoule/x64dbg-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tracealyzer .cursor/skills/tracealyzer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tracealyzer" agent skill from https://github.com/dariushoule/x64dbg-skills/tree/main/skills/tracealyzer into .cursor/skills/tracealyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracealyzer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dariushoule/x64dbg-skills.git --path skills/tracealyzer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dariushoule/x64dbg-skills --skill tracealyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dariushoule/x64dbg-skills tracealyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dariushoule/x64dbg-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tracealyzer .gemini/skills/tracealyzer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tracealyzer" agent skill from https://github.com/dariushoule/x64dbg-skills/tree/main/skills/tracealyzer into .gemini/skills/tracealyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracealyzer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dariushoule/x64dbg-skills tracealyzerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dariushoule/x64dbg-skills --skill tracealyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dariushoule/x64dbg-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tracealyzer .github/skills/tracealyzer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tracealyzer" agent skill from https://github.com/dariushoule/x64dbg-skills/tree/main/skills/tracealyzer into .github/skills/tracealyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracealyzer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dariushoule/x64dbg-skills --skill tracealyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dariushoule/x64dbg-skills tracealyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dariushoule/x64dbg-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tracealyzer .opencode/skills/tracealyzer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tracealyzer" agent skill from https://github.com/dariushoule/x64dbg-skills/tree/main/skills/tracealyzer into .opencode/skills/tracealyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracealyzer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
tracealyzer- GitHub stars
- 209
- Token cost
- ~1k tokens
- SKILL.md length
- 484 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Trace execution (into or over calls) for N steps or until a condition, then analyze the recorded instruction log
- Works in 6 steps: Verify debugger connection → Gather trace parameters → Capture starting context → …
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Tracealyzer is an agent skill from dariushoule/x64dbg-skills. Trace execution (into or over calls) for N steps or until a condition, then analyze the recorded instruction log
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Model Context Protocol. The repository describes itself as: Claude Code plugin providing skills for x64dbg debugger automation. The licence is MIT.
Example prompts
- “/tracealyzer”
Requirements
- Pre-approved tools (allowed-tools): mcp__x64dbg__get_debugger_status, mcp__x64dbg__pause, mcp__x64dbg__trace_into, mcp__x64dbg__trace_over, mcp__x64dbg__eval_expression, mcp__x64dbg__get_symbol, mcp__x64dbg__disassemble, mcp__x64dbg__get_all_registers, mcp__x64dbg__set_comment, mcp__x64dbg__set_label, Read, Bash
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 0409f53. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
mcp__x64dbg__get_debugger_statusmcp__x64dbg__pausemcp__x64dbg__trace_intomcp__x64dbg__trace_overmcp__x64dbg__eval_expressionmcp__x64dbg__get_symbolmcp__x64dbg__disassemblemcp__x64dbg__get_all_registersmcp__x64dbg__set_commentmcp__x64dbg__set_label
…and 2 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Tracealyzer loads about 1k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 484 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: mcp__x64dbg__get_debugger_status, mcp__x64dbg__pause, mcp__x64dbg__trace_into, mcp__x64dbg__trace_ov
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dariushoule/x64dbg-skills at commit 0409f53, republished under its MIT licence (© dariushoule). 484 words, ~1,018 tokens.
Download SKILL.mdSave it as
.claude/skills/tracealyzer/SKILL.md (or your agent's skills folder).- name
- tracealyzer
- description
- Trace execution (into or over calls) for N steps or until a condition, then analyze the recorded instruction log
- allowed-tools
- mcp__x64dbg__get_debugger_status, mcp__x64dbg__pause, mcp__x64dbg__trace_into, mcp__x64dbg__trace_over, mcp__x64dbg__eval_expression, mcp__x64dbg__get_symbol, mcp__x64dbg__disassemble, mcp__x64dbg__get_all_registers, mcp__x64dbg__set_comment, mcp__x64dbg__set_label, Read, Bash
tracealyzer
Trace debuggee execution — stepping into or over calls — for a specified number of instructions or until a condition is met. The full instruction log is captured to a file and then analyzed.
Instructions
Follow these steps exactly:
1. Verify debugger connection
Call mcp__x64dbg__get_debugger_status to confirm the debugger is connected and a debuggee is loaded and paused. If it is running, call mcp__x64dbg__pause. If no debuggee is loaded, tell the user and stop.
2. Gather trace parameters
Ask the user for the following if not already provided:
- Trace mode: trace into calls or trace over calls (default: over)
- Stop condition — one of:
- A maximum number of instructions (e.g.
1000) - An x64dbg expression that stops when true (e.g.
cip == 0x7FF6A0001000,rax != 0) - Both (whichever triggers first)
- A maximum number of instructions (e.g.
If the user provides a symbol or address for the stop condition, resolve it with mcp__x64dbg__eval_expression and build the break_condition expression (e.g. cip == <resolved_addr>).
When the user only specifies a step count N and no explicit break condition, use break_condition 0 (never true — the trace runs until max_steps is hit).
3. Capture starting context
Call mcp__x64dbg__get_all_registers and mcp__x64dbg__disassemble at the current instruction pointer to record the starting state. Note the starting address.
4. Run the trace
Prepare the output log path: ./traces/trace_<timestamp>.log (create the traces directory if it doesn't exist via Bash).
Call the appropriate trace tool (mcp__x64dbg__trace_into or mcp__x64dbg__trace_over) with:
| Parameter | Value |
|---|---|
break_condition | The user's condition, or 0 if only a step count was given |
max_steps | The user's step count, or 50000 if only a condition was given |
log_text | `{p:cip} {i:cip} |
log_file | The output log path from above |
wait_timeout | Scale with max_steps — use max(60, max_steps // 500) seconds |
Show full SKILL.md (209 more words)Show less
5. Read and analyze the trace log
Read the trace log file. The log contains one line per executed instruction in the format:
<address> <disassembly> | Label=<label> Comment=<comment>Ignore when Labels or Comments say [Formatting Error], it just means there is no label or comment at that instruction.
Analyze the trace and present a summary to the user:
- Trace overview: total instructions executed, start address → end address, trace mode used
- Execution flow: describe the high-level behavior — what the code did, which functions were called, loops observed, and notable control-flow patterns
- Hot spots: addresses or regions that appear most frequently (loops, repeated calls)
- Key observations: interesting register manipulations, memory accesses, syscalls, API calls, string operations, or anything else that stands out
Use mcp__x64dbg__get_symbol to resolve notable addresses to symbol names where possible.
If the trace log is very large (>2000 lines), read it in chunks and summarize progressively.
6. Follow-up actions
After presenting the summary, ask the user if they would like any follow-up actions such as:
- Annotate: add comments/labels in x64dbg at key addresses using
mcp__x64dbg__set_comment/mcp__x64dbg__set_label - Deeper analysis: re-trace a specific sub-region, or focus on a particular function
- Deobfuscation: identify and explain obfuscated patterns found in the trace
- Export: the trace log is already saved to disk at the path from step 4
© dariushoule, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/tracealyzer of dariushoule/x64dbg-skills.
Open the folder on GitHubat commit 0409f53
Compare with similar skills
Tracealyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tracealyzer this skilldariushoule/x64dbg-skills | 209 | — | ~1k | Automated safety check: Notes | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Figma use_figma Plugin API Ruleswarpdotdev/warp | 65k | 4 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills | 8.4k | 6 repos | ~3.2k | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
- Official
MCP Integration for Plugins
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
- Official
Stitch to Remotion Walkthrough Videos
google-labs-code/stitch-skills
Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.
MCP Development
coollabsio/coolify
A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.
More from dariushoule/x64dbg-skills
Decompile
dariushoule/x64dbg-skills
Decompile a function to C-like pseudocode using angr. An agent skill from dariushoule/x64dbg-skills.
State Diff
dariushoule/x64dbg-skills
Compare two state snapshots to identify register and memory changes between two points in time
State Snapshot
dariushoule/x64dbg-skills
Capture a full debuggee state snapshot (all committed memory regions + processor state) to disk for offline analysis
Vuln Hunter
dariushoule/x64dbg-skills
Hunt for vulnerabilities in a running debuggee by analyzing imports/exports, triaging attack surface, and iteratively testing for bugs with PoC generation.
Yara Sigs
dariushoule/x64dbg-skills
Scan a state snapshot's memory dumps with YARA signatures to detect packers, crypto constants, malware, and more
Find Oep
dariushoule/x64dbg-skills
Smart trace-based OEP finder for packed/protected PE executables.
Related
Works with
Questions about Tracealyzer
What does Tracealyzer do?
Trace execution (into or over calls) for N steps or until a condition, then analyze the recorded instruction log. Tracealyzer is an agent skill from dariushoule/x64dbg-skills.
How do I install Tracealyzer in Claude Code?
Run `npx skills add dariushoule/x64dbg-skills --skill tracealyzer -a claude-code`. Or copy the skill folder (skills/tracealyzer in dariushoule/x64dbg-skills) into .claude/skills/tracealyzer in your project. Claude Code loads it when a task matches its description.
How do I install Tracealyzer in Codex?
Run `npx skills add dariushoule/x64dbg-skills --skill tracealyzer -a codex`. Or copy the skill folder (skills/tracealyzer in dariushoule/x64dbg-skills) into .agents/skills/tracealyzer in your project. Codex loads it when a task matches its description.
Can I use Tracealyzer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dariushoule/x64dbg-skills --skill tracealyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tracealyzer, .gemini/skills/tracealyzer, .github/skills/tracealyzer and .opencode/skills/tracealyzer in your project.
What does Tracealyzer need to run?
SKILL.md names no scripts, command-line tools or credentials: Tracealyzer is instructions for the agent only. Its frontmatter pre-approves these tools: mcp__x64dbg__get_debugger_status, mcp__x64dbg__pause, mcp__x64dbg__trace_into, mcp__x64dbg__trace_over, mcp__x64dbg__eval_expression, mcp__x64dbg__get_symbol, mcp__x64dbg__disassemble, mcp__x64dbg__get_all_registers, mcp__x64dbg__set_comment, mcp__x64dbg__set_label, Read, Bash.
Does Tracealyzer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Tracealyzer safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Tracealyzer use?
Tracealyzer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Tracealyzer use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Tracealyzer?
Skills that share tags, products or a category with Tracealyzer: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tracealyzer?
dariushoule (a GitHub user) maintains it in dariushoule/x64dbg-skills, which has 209 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on March 13, 2026.
Source: dariushoule/x64dbg-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.