Update to reverse engineering anything

{
  "description": "Plan passive observation of a user-owned browser or Electron app and interpret retained HAR/mitmproxy captures without turning historical records into live network claims.",
  "included_files": [],
  "name": "rea-browser-and-network",
  "skill_md_contents": "---\nname: rea-browser-and-network\ndescription: Plan passive observation of a user-owned browser or Electron app and interpret retained HAR/mitmproxy captures without turning historical records into live network claims.\n---\n\n# Browser and network evidence\n\n## Browser/Electron observation\n\n- Prefer the already-open, user-owned page/runtime and the documented REA target-listing workflow.\n- Confirm the exact target and interaction. Avoid authentication changes, purchases, destructive actions, production mutations, or private account traversal.\n- Distinguish DOM/page structure, loaded scripts, observed requests, screenshots, and runtime effects. A screenshot or page snapshot covers only one state.\n- Do not open URLs discovered in a capture or replay requests. Do not claim a historical request came from the live page without fresh attribution evidence.\n\n## Retained HAR or mitmproxy capture\n\n- Confirm the user is authorized to analyze the supplied capture; it may contain cookies, authorization headers, personal data, internal endpoints, or private payloads.\n- Use the advertised capture-inspection workflow on the retained file. Treat it as historical evidence, not live traffic.\n- Preserve original record ordinals where useful and identify producer-specific fields/sidecars. Do not normalize away distinctions that affect interpretation.\n- Redact credentials, tokens, personal data, and unrelated hosts before sharing results. Never print secrets back in the report.\n- If capture evidence is incomplete, identify missing records or fields and the limited conclusion; do not fill gaps with assumptions.\n\nUse only read-only analysis unless the user explicitly requests an authorized, tightly scoped interaction. Captured requests must not be replayed against live services.\n"
}