import-export-resolver

Resolve PE import and export relationships across analyzed modules.

17|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/marcosd4h/DeepExtractRuntime --skill import-export-resolver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: import-export-resolver
Source: https://github.com/marcosd4h/DeepExtractRuntime/tree/main/skills/import-export-resolver
Command: npx skills add https://github.com/marcosd4h/DeepExtractRuntime --skill import-export-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires helpers.import_export_index, skills._shared, and includes /scripts (resource) components.

What problem does it solve?

Resolve PE-level import and export relationships across all analyzed modules in a DeepExtractIDA workspace. Answers which module exports a given function, which modules import it, builds PE-level module dependency graphs, and follows forwarded export chains. Use when the user asks which DLL exports a function, who imports a function, what a module depends on at the loader level, wants PE import/export tables (not code xrefs), asks about forwarded exports, needs cross-module dependency mapping from import tables, or wants to know all consumers of a given DLL.

Core Features & Use Cases

  • Identify exporters and importers for a given function across workspace modules.
  • Build and inspect PE-level module dependency graphs and forwarded export chains.
  • Support workflows to answer "who exports/depends on what" across DLLs and modules.

Quick Start

Query the workspace to resolve a function's exporters and importers or to generate a full dependency graph.

Frequently Asked Questions about import-export-resolver

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

FAQPage Schema
How do I find which DLL exports a function across all analyzed modules?

To find which DLL exports a function, resolve PE-level export relationships across analyzed modules. The resolver reads PE export data from file_info.exports and identifies the specific exporters for a given function.

What is the best way to map cross-module dependencies using PE import tables?

Mapping cross-module dependencies using PE import tables involves resolving loader-level relationships across modules. It reads file_info.imports data and builds per-module dependency graphs showing what each module requires.

How do I trace forwarded export chains in PE modules?

Tracing forwarded export chains in PE modules requires resolving forwarded export relationships across the workspace. The resolver follows forwarder chains to identify the final target module and function.

Can I identify all importers of a specific function from a DeepExtractIDA workspace?

Yes, you can identify all importers of a specific function from a DeepExtractIDA workspace. The resolver queries the analyzed_files.db tracking DB and cross-references file_info.imports to output all consuming modules.

Does this resolve PE import and export relationships or code-level cross references?

This resolves PE import and export relationships, not code-level cross references. It strictly reads loader-level PE import and export tables from file_info data to map cross-module dependencies and forwarded export chains.