make-signature

Generate durable byte signatures to locate functions across binary updates.

15|4|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/vzco/arc-probe --skill make-signature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-signature
Source: https://github.com/vzco/arc-probe/tree/main/plugins/arc-probe/skills/make-signature
Command: npx skills add https://github.com/vzco/arc-probe --skill make-signature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate robust byte signatures to locate functions after binary updates by capturing stable byte patterns with wildcards for changing offsets and addresses.

Core Features & Use Cases

  • Disassemble the function start to identify stable behavior and unique bytes.
  • Auto-generate and test signatures that remain unique across builds and patches.
  • Manual refinement options when auto-generation is ambiguous or non-unique.
  • Use Case: maintain reliable function references in patch scenarios for tooling, debugging, and reverse-engineering workflows.

Quick Start

Disassemble a target function, generate a 32-byte signature, and verify it against the target module.

Frequently Asked Questions about make-signature

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

FAQPage Schema
How do I generate byte signatures to locate functions after a binary update?

To generate byte signatures for binary updates, disassemble the target function start to identify stable bytes, auto-generate a signature with wildcards for changing offsets, and test it for uniqueness across builds.

Why do my pattern scans fail to find functions after applying a patch?

Pattern scans often fail after patches because hardcoded addresses and offsets change. Generating durable byte signatures with wildcards for these variable offsets ensures functions remain locatable across binary updates.

What is the best way to disassemble a function start for reverse engineering?

The best way to disassemble a function start for reverse engineering is to use probe_disassemble to identify stable behavior and unique bytes, which are then used to auto-generate durable byte signatures.

What should I do when an auto-generated byte signature is not unique?

When an auto-generated byte signature is not unique, you should use manual refinement options to adjust the pattern. You can then test the signature again to ensure it remains unique across builds.

Can I test byte signatures against a specific target module?

Yes, you can test byte signatures against a target module. The workflow uses probe_test_signature and probe_pattern_scan to verify that the generated pattern remains unique and correctly locates the function.