skills.rest
NlightNFotis
NlightNFotisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reverse-engineering

Probe opaque systems to build confidence-rated behavioral models.

2|Updated Apr 30, 2026
Search Tags:#api integration#reverse engineering#legacy systems#differential analysis#behavioral analysis#black-box testing#clean-room
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill reverse-engineering-nlightnfotis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reverse-engineering
Source: https://github.com/NlightNFotis/skills/tree/main/reverse-engineering
Command: npx skills add https://github.com/NlightNFotis/skills --skill reverse-engineering-nlightnfotis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand software or services that lack trustworthy documentation, source code, or tests by building a disciplined model from observed behavior instead of guesswork.

Core Features & Use Cases

  • Behavioral characterization: Map inputs, outputs, state changes, and edge cases for black-box, gray-box, white-box, or runtime-controlled systems.
  • Evidence-based modeling: Separate observed facts from inferred rules and assumptions, then assign confidence to each claim.
  • Differential analysis and decision support: Compare versions or implementations, establish golden references, and decide whether to keep probing, rewrite, or use a clean-room reimplementation approach.
  • Use cases: Investigating a legacy component with no tests, integrating with an API whose docs are unreliable, validating a refactor when no formal spec exists, or characterizing a closed-source dependency before replacing it.

Quick Start

Ask the reverse-engineering skill to characterize a target system by defining its boundary, capturing a golden reference, and building a confidence-rated behavioral model from observed inputs and outputs.

Frequently Asked Questions about reverse-engineering

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

FAQPage Schema
How do I model a legacy system with no documentation or source code?▼

To model a legacy system without documentation, you derive a behavioral model through structured probing and observation tagging. This process maps inputs, outputs, and edge cases while explicitly separating observed facts from inferred rules with assigned confidence levels.

What is differential analysis when characterizing an opaque system?▼

Differential analysis for an opaque system compares observed behaviors against versions or implementations using golden references. This structured probing establishes reliable boundaries and confidence-marked rules to decide whether to keep probing, rewrite, or plan a clean-room reimplementation.

Can I use black-box testing to integrate with an unreliable third-party API?▼

Yes, black-box testing can integrate with an unreliable third-party API by capturing golden references and mapping boundary behaviors. This structured probing produces a confidence-rated behavioral model that separates actual observed outputs from assumed integration rules.

Does reverse engineering an opaque system require white-box access?▼

No, reverse engineering an opaque system does not require white-box access. You can apply structured probing across black-box, gray-box, white-box, or translucent access levels to build a behavioral model from observed inputs and outputs.

When should I choose a clean-room reimplementation over refactoring a closed-source dependency?▼

You should choose a clean-room reimplementation when differential analysis and confidence-marked rules reveal the closed-source dependency is too unreliable. Establishing golden references and bill-of-materials mapping helps determine whether to keep probing, rewrite, or reimplement.

Related Skills

Explore More Software Engineering Skills→
polsegupolsegu

create-architecture

Consolidate GDDs, ADRs, and engine references into a master architecture document.

Community
Advanced
whywaitawhywaita

code-simplifier

Refactor complex or duplicated code while preserving behavior.

Community
Intermediate
Q16GQ16G
83

graybox-p0

Orchestrate gray-box testing by combining white-box candidate discovery with black-box request validation.

Community
Intermediate
wvs-financewvs-finance
4

type-driven-development

Enforce type-driven development for Solidity smart contracts with formal verification.

Official
Advanced