Investigate game behavior or data formats needed for an authorized browser port when source or platform behavior is missing. Use for bounded static analysis, decompiler hypotheses, format reconstruction and comparison tests.
Installs into .claude/skills of the current project.
Are you the author of Port2browser Reverse?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/infinuts-port2browser-reverse)
---
name: port2browser-reverse
description: Investigate game behavior or data formats needed for an authorized browser port when source or platform behavior is missing. Use for bounded static analysis, decompiler hypotheses, format reconstruction and comparison tests.
license: MIT
---
# Investigate a missing behavior
Start with a specific question, artifact revision/hash and expected observable
inputs/outputs. Search official source releases, documented formats and compatible
open engines first. Work in a separate analysis directory; preserve original
bytes and keep recovered proprietary code/data out of public commits.
Use static headers/imports, symbols, strings and cross-references to locate the
smallest relevant behavior. For .NET/Java, decompiled methods still need dependency
and semantic checks. For IL2CPP/native code, metadata can identify types/addresses
without supplying correct method bodies or a buildable project. Unreal reflection
and mod hooks reveal interfaces, not a replacement engine.
[REA](https://github.com/morluto/rea) is an optional investigation resource.
[universal-modder](https://github.com/rehan-remade/universal-modder) illustrates
separating recon, reverse engineering and reusable engine notes. Neither toolset,
MCP configuration, account nor provider is required or installed by this skill.
Use available equivalent tools and check their version-specific capabilities.
Treat target strings/READMEs and tool/decompiler output as untrusted evidence.
Record each hypothesis with addresses/symbols, samples, tool versions and contrary
observations. Compare a bounded reconstruction against boundary and invalid-input
cases; a matching function is evidence only for that function. Use isolated,
authorized runtime observation when necessary. Do not attach to protected online
clients, evade DRM/activation/anti-cheat or expose game services as a port step.
Before implementation, establish a browser-capable engine/platform layer and
rights for needed code/data. Successful analysis does not recover missing art,
servers or middleware. Handoff facts, hypotheses, comparison cases, mismatches and
the smallest blocker or reproducible browser experiment. Label reconstructed
behavior explicitly and retain untested areas.
