What problem does it solve? Locating how a web page generates API signatures, encryption parameters, and anti-fraud fields is slow and error-prone when done by guessing at minified source. This Skill provides a structured observe-capture-rebuild workflow that grounds every step in runtime evidence collected through js-reverse MCP or jshookmcp browser tooling. ## Core Features & Use Cases - Request and Signature Tracing: Use network request listing, initiator call stacks, and XHR breakpoints to find exactly which script and function generate a target parameter. - Runtime Sampling: Capture function arguments, return values, and WebSocket messages with minimally invasive breakpoints and script evaluation. - Local Node Reproduction: Rebuild the signing logic locally with evidence-driven environment shimming, patching one minimal gap at a time until output is reproducible. - Use Case: Given a target site whose login request carries an encrypted sign parameter, observe the request chain, break on the XHR call, identify the signing function, then reproduce the algorithm in Node with shims for only the browser objects the evidence proves are needed. ## Quick Start Use the js-reverse skill to open the target page, trace the initiator of the login request, and identify the function that generates its signature parameter.
