write-vtable-as-yaml

Extract vtable information from binaries and persist it as YAML using IDA Pro MCP.

60|11|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/HLND2T/CS2_VibeSignatures --skill write-vtable-as-yaml-hlnd2t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-vtable-as-yaml
Source: https://github.com/HLND2T/CS2_VibeSignatures/tree/main/.claude/skills/write-vtable-as-yaml
Command: npx skills add https://github.com/HLND2T/CS2_VibeSignatures --skill write-vtable-as-yaml-hlnd2t

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write a tool to persist vtable analysis results to a YAML file beside the target binary, enabling easy documentation and versioned comparison across builds.

Core Features & Use Cases

  • Persist vtable data to a YAML file next to the analyzed binary, capturing vtable class, address, size, and entries.
  • Platform-aware analysis: supports Windows and Linux binaries and adapts vtable handling (including Linux RTTI handling) automatically.
  • Use Case: Reverse engineers can snapshot vtable layouts after locating a vtable to compare across game updates or shared libraries.

Quick Start

Locate the target vtable address in the binary, then run IDA Pro MCP with this skill to generate a YAML file named <Class>_vtable.<platform>.yaml in the same directory as the binary.

Frequently Asked Questions about write-vtable-as-yaml

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist vtable analysis results from IDA Pro to a YAML file?

You can persist vtable analysis results by running IDA Pro MCP with this skill to generate a YAML file capturing the vtable class, address, size, and entries next to the analyzed binary.

Can I extract vtable data from both Windows and Linux binaries?

Yes, vtable extraction supports both Windows and Linux binaries, automatically adapting vtable handling including Linux RTTI handling for accurate YAML documentation.

What is the best way to document and compare vtable layouts across different binary builds?

The best way to compare vtable layouts is generating a YAML file for each build, capturing vtable class, address, size, and entries to enable versioned comparison across updates.

Do I need IDA Pro MCP to automate vtable extraction and save it as YAML?

Yes, you need IDA Pro MCP and a scripting environment capable of reading binary memory and writing YAML to automate vtable extraction and generate the output file.

How does this approach handle Linux RTTI when extracting vtables?

For Linux binaries, the vtable extraction automatically adapts its handling to account for Linux RTTI structures, ensuring accurate capture of vtable entries in the output YAML.

What information is captured when persisting vtable data as YAML?

When persisting vtable data as YAML, the file captures the vtable class, address, size, and entries, providing a complete snapshot of the binary interface layout.