deep-analysis

Trace cross-references and edit decompiler databases during binary behavior investigations.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/faithleysath/DamageMeter --skill deep-analysis-faithleysath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-analysis
Source: https://github.com/faithleysath/DamageMeter/tree/main/docs/skills/deep-analysis
Command: npx skills add https://github.com/faithleysath/DamageMeter --skill deep-analysis-faithleysath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep-analysis helps reverse engineers answer focused, specific questions about binary behavior by guiding an iterative, evidence-based investigation and making incremental, reversible improvements to the decompiler database to improve readability and reproducibility.

Core Features & Use Cases

  • Iterative Investigation Loop: Read decompiled code, analyze operations and assumptions, apply small database edits (renames, type fixes, prototypes), verify improvements, and follow new evidence threads.
  • Question-Focused Strategies: Prescribed workflows for "What does this function do?", "Does this use cryptography?", "What is the C2 address?", and "Fix types in this function", each with discovery, investigation, improvement, verification, and tracking steps.
  • Evidence & Documentation: Emphasizes exact-address evidence, decompilation snippets, documented assumptions with confidence ratings, and actionable follow-up threads for handoff or continued analysis.
  • Use Case: Triaged suspicious function flagged for potential crypto can be investigated end-to-end to confirm algorithm type, locate key material, and create precise bookmarks and comments for reviewers.

Quick Start

Investigate function 0x401234 to determine whether it performs AES encryption and update the decompiler database with descriptive renames, corrected types, and decompilation comments.

Frequently Asked Questions about deep-analysis

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

FAQPage Schema
How do I investigate a suspicious function in Ghidra to determine its behavior?

To investigate suspicious functions in Ghidra, follow an iterative reverse engineering loop: read decompiled code, analyze operations, apply small database edits like renames and type fixes, verify improvements, and trace cross-references for evidence-based conclusions.

What is the best way to identify cryptographic routines during binary analysis?

Identifying cryptographic routines during binary analysis involves a question-focused strategy to discover indicators, investigate algorithm types, locate key material, and document findings with exact addresses and decompilation snippets for reviewer handoff.

Can I fix decompiler types and prototypes to improve decompilation readability?

Yes, you can fix decompiler types and prototypes by applying incremental, reversible database edits within your workflow to correct type recovery, update function prototypes, and improve overall decompilation readability and reproducibility.

How do I trace cross-references to find network indicators like a C2 address?

Tracing cross-references to find network indicators like a C2 address requires following an evidence-driven investigation workflow that reads decompiled code, tracks cross-references, and documents exact addresses and code snippets to confirm the indicator.

Does this reverse engineering workflow support documenting assumptions and bookmarks?

Yes, this reverse engineering workflow supports documenting assumptions with confidence ratings, creating precise bookmarks, and adding decompilation comments to track evidence threads and ensure actionable handoff for continued analysis.