[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79F1T16JCK8P7592RGQDAH5":3,"skill-same:01M79F1T16JCK8P7592RGQDAH5":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M79F1T16JCK8P7592RGQDAH5","reverse-engineer-anything",null,"Reverse engineer native, managed, Electron\u002FJavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.","BumpyClock\u002Fagent-templates","BumpyClock","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1883824?v=4","01M79EW0FDP9MFXH1FKH800S7T","Aditya Sharma","01M79EW0G27TTKZWTFQ8W5HVB4",2,"MIT","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills\u002Freverse-engineer-anything\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: reverse-engineer-anything\ndescription: Reverse engineer native, managed, Electron\u002FJavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.\nmetadata:\n  version: \"34\"\n  tool_count: 139\n---\n\n# REA\n\nUse REA when a claim depends on a shipped binary or package, decompilation,\npassive application runtime evidence, or comparison with\nbehavior not established by available source. For ordinary analysis of a\ncomplete source repository, use normal repository tools and do not run REA\nreadiness or provider commands.\n\n## Connect only when needed\n\nInstalling this skill supplies instructions; it does not register the REA MCP\nserver, install analysis engines, or add tools to an already-running agent.\n\nIf REA tools are available and their registration is not known to be stale,\nproceed directly to the target. Do not run diagnostics or setup before every\ninvestigation. Use the connected server's actual tool list and input schemas;\na skill installed from repository main may describe capabilities absent from\nan older npm release. Keep complete inline Evidence when that server does not\nadvertise retained references.\n\nWhen tools are absent or registration is stale:\n\n1. Diagnose without changing files. For Codex, run\n   `npx -y rea-agents@latest doctor --client codex --json`. Substitute the current\n   supported client: `claude_code`, `claude_desktop`, `codex`, `cursor`,\n   `gemini_cli`, `windsurf`, `devin`, `opencode`, `antigravity`, `copilot_cli`,\n   `commandcode`, `vscode`, `grok_build`, or `grok_bot`. `grok_bot` has no local\n   file registration: doctor reports the Grok Bot chat step, and setup does not\n   write `mcp.json`. If the client is unknown, use `doctor --json` and\n   inspect its registration results before choosing a setup scope.\n2. Distinguish the reason. Missing, malformed, or stale registration needs a\n   scoped configuration repair. An aligned registration with no tools in the\n   active session needs a restart\u002Freconnection; doctor cannot prove that the\n   current agent has connected. A missing provider affects only tasks requiring\n   that provider: static JavaScript inspection needs neither Hopper nor Ghidra,\n   and Android inspection has separate bring-your-own JADX\u002FJava prerequisites.\n3. For a configuration repair, prepare the read-only plan:\n   `npx -y rea-agents@latest setup --client codex --dry-run --json`.\n   Use the current client's ID, show its exact proposed paths, backups, and\n   changes, and obtain approval before setup writes configuration or installs\n   Hopper. Setup normally installs the matching bundled skill too; include that\n   replacement in the reviewed plan. After approval, apply the same scope with\n   `npx -y rea-agents@latest setup --client codex --yes`. Add `--install-hopper`\n   only if that separate installation was needed and explicitly approved.\n4. Restart\u002Freconnect the affected agent. Verify that REA tools actually appear\n   in the session, then resume the original investigation. If they remain\n   absent, inspect the client's MCP launch error rather than repeating setup.\n\nREA setup never installs or upgrades Node.js, npm, Homebrew, Java, Ghidra, IDA,\nJADX, Binwalk, or Unblob. Use existing prerequisites; do not install unrelated\nsoftware to repair\nMCP registration. For an unsupported client, use manual stdio registration\nwith a version-pinned `rea-agents` package or continue through the CLI.\n\nA concrete CLI fallback for an operator-supplied JavaScript tree or ASAR is:\n\n```bash\nnpx -y rea-agents@latest analyze-javascript-application \u002Fabsolute\u002Fpath\u002Fto\u002Fapp --json\n```\n\nNo MCP registration or native engine is required. Read the returned Evidence,\ngraph, limitations, and unknowns with the same care as an MCP result; the CLI\nreturns the Evidence record directly. This fallback does not establish that\nMCP is configured. Native CLI tasks still require their selected engine.\n\n## Route the target first\n\nChoose the first tool from the target the user supplied. Use `open_binary` for\nactive-target native or archive workflows; target-free tools take their own\nexplicit path or endpoint and do not need it.\n\n- ASAR or extracted JavaScript\u002FElectron tree:\n  `analyze_javascript_application`.\n- Archive\u002Fpackage member inventory (ZIP\u002FAPK\u002FIPA\u002FMSIX\u002FAppX or DMG):\n  `open_binary` with the supplied local path; use `inspect_artifact` when its\n  graph and findings help answer the question.\n- Android APK code, classes, methods, or incoming references:\n  `inspect_android_package`, then focused Android tools when advertised.\n  Archive member inventory still uses the archive route above.\n- Managed PE\u002FCLI assembly: `inspect_managed_artifact`.\n- Firmware image: `inspect_firmware_regions` when advertised. Use\n  `extract_firmware` when extraction is requested, with a caller-selected new\n  absolute output directory. These tools use caller-supplied Binwalk\u002FUnblob on\n  Linux; see the [firmware guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Ffirmware-analysis.md).\n- .NET NativeAOT PE\u002FELF: native Ghidra analysis. Native code can yield pseudocode;\n  consult the NativeAOT workflow in `references\u002Fnative-and-artifacts.md` for\n  optional metadata recovery and its supported host\u002Flayout boundary.\n- User-owned browser page already open: `list_browser_targets`.\n- Retained HAR\u002Fnative mitmproxy capture: `inspect_web_network_capture`. Select\n  original record ordinals when useful; inspect producer fields and byte\u002Fnumber\n  sidecars without fetching recorded URLs or claiming live attribution. See\n  [historical captures](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fweb-network-captures.md) for the exact upstream\n  profile and credential exclusions.\n- User-owned Electron runtime already open: `list_electron_targets`.\n- Explicit local EVM bytecode carrier: `inspect_evm_interface` with caller-selected\n  `raw` or `hex` encoding. Preserve carrier\u002Fdecoded digests and treat selectors,\n  argument strings and mutability as inferred candidates; this performs no chain\n  lookup or target execution. See the\n  [EVM bytecode guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fevm-bytecode.md).\n- Explicit Linux ELF file for offline layout, symbols, relocations or static\n  mitigation evidence: `inspect_binary_layout`. This target-free operation uses\n  caller-supplied pwntools without opening a disassembler database. Preserve its\n  raw locations and inference\u002Fcoverage limits; see the\n  [offline binary guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fbinary-diagnostics.md).\n- Supplied Linux x86-64 ELF core: `inspect_recorded_crash`. Read every recorded\n  thread, raw note and source-bound register without opening a live target.\n  Historical PIDs do not select live processes. Request `include_debugger_context`\n  only when core-only mapping candidates help; see the\n  [recorded crash guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Frecorded-crashes.md).\n- Native executable, library, or analysis database: `open_binary`, then\n  use focused analysis tools directly; call `binary_overview` when metadata or\n  inventory context is useful and available from the selected provider.\n\nFor an existing IDA MCP configuration, use `open_binary` with the original\ninput binary and `provider_id: \"ida\"`; do not pass an `.idb` or `.i64` database.\nThe legacy attached profile binds the already-open GUI input by SHA-256 and\nleaves its database open. The modern headless profile creates and closes an\nowned private database without saving. Installation and registration reuse\n[mrexodia\u002Fida-pro-mcp](https:\u002F\u002Fgithub.com\u002Fmrexodia\u002Fida-pro-mcp); see the\n[IDA provider guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fida-provider.md).\nProceed directly to `analyze_function`, pseudocode, or function\u002Fstring searches\nafter opening; IDA does not supply `binary_overview`. Consult session availability\nwhen composing broader workflows. Modern direct callers and unsupported dossier\nfacets remain unknown; live IDA results are not replayed from snapshots.\n\nIf the app is missing, ask which app to inspect. Resolve a human-readable app\nname to one clear installed artifact when possible; ask only when matches are\nambiguous. Never choose an example app on the user's behalf.\n\nIn a target-free session, use `open_binary` to bind any archive\u002Fpackage or\nnative target whose analysis tool operates on the active target. Do not call an\nunadvertised tool; inspect `binary_session` with `{}` and its\n`result.tool_availability` for availability reasons and remediation. The tool\nlist stays complete; availability depends on the operation, target, and host.\n\n## Work summary-first\n\nStart with the default result and use its inline Evidence and graph context.\nDo not repeat an identical tool call. Make a focused follow-up only when the\nreturned result leaves a specific question unanswered.\n\nIf MCP reports `resource_constraint` with `details.resource: \"transport\"`, call\n`inspect_analysis_view` with its reported same-session Evidence reference for a\nsummary, one section\u002Fmodule, or a stable page. Use `trace_application_feature`\nonce a seed is known, or call `export_evidence_bundle` to write the complete\nsession to a selected path. The analysis remains complete in the ledger; avoid\nrepeating it merely to request the same oversized response. Complete CLI JSON\noutput also streams without a single MCP frame.\n\nEvery conclusion must distinguish observations, inferences, and unknowns. Cite\nEvidence IDs, preserve limitations and incomplete coverage, and never imply\nthat static analysis observed execution. Runtime requests execute the declared\ntarget and lifecycle; do not broaden the target or action beyond those fields.\n\nWithin the user's requested investigation, call available analysis tools\ndirectly. REA does not require permission grants or per-call approval flags.\nFollow the declared request scope and the host's actual access requirements.\n\n## Plan broader investigations\n\nFor requests that span multiple features or subsystems, use a staged workflow:\n\n1. Turn the request into a checklist of questions and the evidence each answer\n   needs. Resolve target identity and constraints from the conversation and\n   workspace before asking for information again.\n2. Inspect the current REA session, artifact identity, saved analysis database,\n   bookmarks, and prior evidence. Reuse matching state; do not open duplicate\n   sessions or repeat identical analysis.\n3. Start with the smallest useful overview or inventory. Follow each question\n   from its entry point through relevant data and state changes to its result.\n   Batch related operations around a specific hypothesis, then expand only when\n   the returned evidence leaves a concrete gap.\n4. Inspect relevant packaged resources and configuration alongside code when\n   they affect the question. Use format-aware inventory and parsers; do not\n   infer behavior from filenames, strings, or layout alone.\n5. Corroborate a conclusion with the evidence type it requires. Use runtime\n   observation only when static evidence cannot answer the question and the\n   required host runtime and OS access are available. For JavaScript behavior,\n   run probes against the actual app through the available browser, Electron,\n   or process capture workflow.\n6. Decompose work into independent questions. When parallel workers are\n   available and the questions do not depend on one another, assign distinct\n   scopes, point workers to existing evidence, and ask them to return sources,\n   conclusions, and unresolved gaps. Otherwise, work sequentially.\n7. Keep a concise finding ledger linking each conclusion to Evidence IDs,\n   confidence\u002Fevidence type, search boundary, and remaining unknowns. Update\n   the shared index or investigation report so later passes can reuse results.\n\nBefore finishing, revisit the original checklist. Mark each question as\nanswered, partially answered, or unresolved based on its evidence; keep\nbounded negative searches bounded, and do not describe a broad investigation\nas complete while required questions remain open.\n\n## Read only the relevant guide\n\n- Native binaries, managed assemblies, archives, and extraction:\n  [references\u002Fnative-and-artifacts.md](references\u002Fnative-and-artifacts.md)\n- ASARs, extracted JavaScript, feature tracing, and version comparison:\n  [references\u002Fjavascript-applications.md](references\u002Fjavascript-applications.md)\n- Android APK declarations, classes, methods, and static references:\n  [references\u002Fandroid-applications.md](references\u002Fandroid-applications.md)\n- Passive browser\u002FElectron observation and static\u002Fruntime reconciliation:\n  [references\u002Fruntime-observation.md](references\u002Fruntime-observation.md)\n- Evidence paging, comparisons, residual unknowns, and verification:\n  [references\u002Fevidence-workflows.md](references\u002Fevidence-workflows.md)\n\n## Finish the task\n\nExplain findings in plain language and tie them to returned evidence. When the\nuser asks to build something, use normal coding tools and separate observed\nbehavior from design choices. Close an opened native session with\n`close_binary` when the investigation is complete.\n","# REA\n\nUse REA when a claim depends on a shipped binary or package, decompilation,\npassive application runtime evidence, or comparison with\nbehavior not established by available source. For ordinary analysis of a\ncomplete source repository, use normal repository tools and do not run REA\nreadiness or provider commands.\n\n## Connect only when needed\n\nInstalling this skill supplies instructions; it does not register the REA MCP\nserver, install analysis engines, or add tools to an already-running agent.\n\nIf REA tools are available and their registration is not known to be stale,\nproceed directly to the target. Do not run diagnostics or setup before every\ninvestigation. Use the connected server's actual tool list and input schemas;\na skill installed from repository main may describe capabilities absent from\nan older npm release. Keep complete inline Evidence when that server does not\nadvertise retained references.\n\nWhen tools are absent or registration is stale:\n\n1. Diagnose without changing files. For Codex, run\n   `npx -y rea-agents@latest doctor --client codex --json`. Substitute the current\n   supported client: `claude_code`, `claude_desktop`, `codex`, `cursor`,\n   `gemini_cli`, `windsurf`, `devin`, `opencode`, `antigravity`, `copilot_cli`,\n   `commandcode`, `vscode`, `grok_build`, or `grok_bot`. `grok_bot` has no local\n   file registration: doctor reports the Grok Bot chat step, and setup does not\n   write `mcp.json`. If the client is unknown, use `doctor --json` and\n   inspect its registration results before choosing a setup scope.\n2. Distinguish the reason. Missing, malformed, or stale registration needs a\n   scoped configuration repair. An aligned registration with no tools in the\n   active session needs a restart\u002Freconnection; doctor cannot prove that the\n   current agent has connected. A missing provider affects only tasks requiring\n   that provider: static JavaScript inspection needs neither Hopper nor Ghidra,\n   and Android inspection has separate bring-your-own JADX\u002FJava prerequisites.\n3. For a configuration repair, prepare the read-only plan:\n   `npx -y rea-agents@latest setup --client codex --dry-run --json`.\n   Use the current client's ID, show its exact proposed paths, backups, and\n   changes, and obtain approval before setup writes configuration or installs\n   Hopper. Setup normally installs the matching bundled skill too; include that\n   replacement in the reviewed plan. After approval, apply the same scope with\n   `npx -y rea-agents@latest setup --client codex --yes`. Add `--install-hopper`\n   only if that separate installation was needed and explicitly approved.\n4. Restart\u002Freconnect the affected agent. Verify that REA tools actually appear\n   in the session, then resume the original investigation. If they remain\n   absent, inspect the client's MCP launch error rather than repeating setup.\n\nREA setup never installs or upgrades Node.js, npm, Homebrew, Java, Ghidra, IDA,\nJADX, Binwalk, or Unblob. Use existing prerequisites; do not install unrelated\nsoftware to repair\nMCP registration. For an unsupported client, use manual stdio registration\nwith a version-pinned `rea-agents` package or continue through the CLI.\n\nA concrete CLI fallback for an operator-supplied JavaScript tree or ASAR is:\n\n```bash\nnpx -y rea-agents@latest analyze-javascript-application \u002Fabsolute\u002Fpath\u002Fto\u002Fapp --json\n```\n\nNo MCP registration or native engine is required. Read the returned Evidence,\ngraph, limitations, and unknowns with the same care as an MCP result; the CLI\nreturns the Evidence record directly. This fallback does not establish that\nMCP is configured. Native CLI tasks still require their selected engine.\n\n## Route the target first\n\nChoose the first tool from the target the user supplied. Use `open_binary` for\nactive-target native or archive workflows; target-free tools take their own\nexplicit path or endpoint and do not need it.\n\n- ASAR or extracted JavaScript\u002FElectron tree:\n  `analyze_javascript_application`.\n- Archive\u002Fpackage member inventory (ZIP\u002FAPK\u002FIPA\u002FMSIX\u002FAppX or DMG):\n  `open_binary` with the supplied local path; use `inspect_artifact` when its\n  graph and findings help answer the question.\n- Android APK code, classes, methods, or incoming references:\n  `inspect_android_package`, then focused Android tools when advertised.\n  Archive member inventory still uses the archive route above.\n- Managed PE\u002FCLI assembly: `inspect_managed_artifact`.\n- Firmware image: `inspect_firmware_regions` when advertised. Use\n  `extract_firmware` when extraction is requested, with a caller-selected new\n  absolute output directory. These tools use caller-supplied Binwalk\u002FUnblob on\n  Linux; see the [firmware guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Ffirmware-analysis.md).\n- .NET NativeAOT PE\u002FELF: native Ghidra analysis. Native code can yield pseudocode;\n  consult the NativeAOT workflow in `references\u002Fnative-and-artifacts.md` for\n  optional metadata recovery and its supported host\u002Flayout boundary.\n- User-owned browser page already open: `list_browser_targets`.\n- Retained HAR\u002Fnative mitmproxy capture: `inspect_web_network_capture`. Select\n  original record ordinals when useful; inspect producer fields and byte\u002Fnumber\n  sidecars without fetching recorded URLs or claiming live attribution. See\n  [historical captures](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fweb-network-captures.md) for the exact upstream\n  profile and credential exclusions.\n- User-owned Electron runtime already open: `list_electron_targets`.\n- Explicit local EVM bytecode carrier: `inspect_evm_interface` with caller-selected\n  `raw` or `hex` encoding. Preserve carrier\u002Fdecoded digests and treat selectors,\n  argument strings and mutability as inferred candidates; this performs no chain\n  lookup or target execution. See the\n  [EVM bytecode guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fevm-bytecode.md).\n- Explicit Linux ELF file for offline layout, symbols, relocations or static\n  mitigation evidence: `inspect_binary_layout`. This target-free operation uses\n  caller-supplied pwntools without opening a disassembler database. Preserve its\n  raw locations and inference\u002Fcoverage limits; see the\n  [offline binary guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fbinary-diagnostics.md).\n- Supplied Linux x86-64 ELF core: `inspect_recorded_crash`. Read every recorded\n  thread, raw note and source-bound register without opening a live target.\n  Historical PIDs do not select live processes. Request `include_debugger_context`\n  only when core-only mapping candidates help; see the\n  [recorded crash guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Frecorded-crashes.md).\n- Native executable, library, or analysis database: `open_binary`, then\n  use focused analysis tools directly; call `binary_overview` when metadata or\n  inventory context is useful and available from the selected provider.\n\nFor an existing IDA MCP configuration, use `open_binary` with the original\ninput binary and `provider_id: \"ida\"`; do not pass an `.idb` or `.i64` database.\nThe legacy attached profile binds the already-open GUI input by SHA-256 and\nleaves its database open. The modern headless profile creates and closes an\nowned private database without saving. Installation and registration reuse\n[mrexodia\u002Fida-pro-mcp](https:\u002F\u002Fgithub.com\u002Fmrexodia\u002Fida-pro-mcp); see the\n[IDA provider guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fida-provider.md).\nProceed directly to `analyze_function`, pseudocode, or function\u002Fstring searches\nafter opening; IDA does not supply `binary_overview`. Consult session availability\nwhen composing broader workflows. Modern direct callers and unsupported dossier\nfacets remain unknown; live IDA results are not replayed from snapshots.\n\nIf the app is missing, ask which app to inspect. Resolve a human-readable app\nname to one clear installed artifact when possible; ask only when matches are\nambiguous. Never choose an example app on the user's behalf.\n\nIn a target-free session, use `open_binary` to bind any archive\u002Fpackage or\nnative target whose analysis tool operates on the active target. Do not call an\nunadvertised tool; inspect `binary_session` with `{}` and its\n`result.tool_availability` for availability reasons and remediation. The tool\nlist stays complete; availability depends on the operation, target, and host.\n\n## Work summary-first\n\nStart with the default result and use its inline Evidence and graph context.\nDo not repeat an identical tool call. Make a focused follow-up only when the\nreturned result leaves a specific question unanswered.\n\nIf MCP reports `resource_constraint` with `details.resource: \"transport\"`, call\n`inspect_analysis_view` with its reported same-session Evidence reference for a\nsummary, one section\u002Fmodule, or a stable page. Use `trace_application_feature`\nonce a seed is known, or call `export_evidence_bundle` to write the complete\nsession to a selected path. The analysis remains complete in the ledger; avoid\nrepeating it merely to request the same oversized response. Complete CLI JSON\noutput also streams without a single MCP frame.\n\nEvery conclusion must distinguish observations, inferences, and unknowns. Cite\nEvidence IDs, preserve limitations and incomplete coverage, and never imply\nthat static analysis observed execution. Runtime requests execute the declared\ntarget and lifecycle; do not broaden the target or action beyond those fields.\n\nWithin the user's requested investigation, call available analysis tools\ndirectly. REA does not require permission grants or per-call approval flags.\nFollow the declared request scope and the host's actual access requirements.\n\n## Plan broader investigations\n\nFor requests that span multiple features or subsystems, use a staged workflow:\n\n1. Turn the request into a checklist of questions and the evidence each answer\n   needs. Resolve target identity and constraints from the conversation and\n   workspace before asking for information again.\n2. Inspect the current REA session, artifact identity, saved analysis database,\n   bookmarks, and prior evidence. Reuse matching state; do not open duplicate\n   sessions or repeat identical analysis.\n3. Start with the smallest useful overview or inventory. Follow each question\n   from its entry point through relevant data and state changes to its result.\n   Batch related operations around a specific hypothesis, then expand only when\n   the returned evidence leaves a concrete gap.\n4. Inspect relevant packaged resources and configuration alongside code when\n   they affect the question. Use format-aware inventory and parsers; do not\n   infer behavior from filenames, strings, or layout alone.\n5. Corroborate a conclusion with the evidence type it requires. Use runtime\n   observation only when static evidence cannot answer the question and the\n   required host runtime and OS access are available. For JavaScript behavior,\n   run probes against the actual app through the available browser, Electron,\n   or process capture workflow.\n6. Decompose work into independent questions. When parallel workers are\n   available and the questions do not depend on one another, assign distinct\n   scopes, point workers to existing evidence, and ask them to return sources,\n   conclusions, and unresolved gaps. Otherwise, work sequentially.\n7. Keep a concise finding ledger linking each conclusion to Evidence IDs,\n   confidence\u002Fevidence type, search boundary, and remaining unknowns. Update\n   the shared index or investigation report so later passes can reuse results.\n\nBefore finishing, revisit the original checklist. Mark each question as\nanswered, partially answered, or unresolved based on its evidence; keep\nbounded negative searches bounded, and do not describe a broad investigation\nas complete while required questions remain open.\n\n## Read only the relevant guide\n\n- Native binaries, managed assemblies, archives, and extraction:\n  [references\u002Fnative-and-artifacts.md](references\u002Fnative-and-artifacts.md)\n- ASARs, extracted JavaScript, feature tracing, and version comparison:\n  [references\u002Fjavascript-applications.md](references\u002Fjavascript-applications.md)\n- Android APK declarations, classes, methods, and static references:\n  [references\u002Fandroid-applications.md](references\u002Fandroid-applications.md)\n- Passive browser\u002FElectron observation and static\u002Fruntime reconciliation:\n  [references\u002Fruntime-observation.md](references\u002Fruntime-observation.md)\n- Evidence paging, comparisons, residual unknowns, and verification:\n  [references\u002Fevidence-workflows.md](references\u002Fevidence-workflows.md)\n\n## Finish the task\n\nExplain findings in plain language and tie them to returned evidence. When the\nuser asks to build something, use normal coding tools and separate observed\nbehavior from design choices. Close an opened native session with\n`close_binary` when the investigation is complete.\n",{"name":5,"metadata":24,"description":7},{"version":25,"tool_count":26},"34",139,"main","e24b64bdac040ad169ed16b14853eff1b20cd726","skills\u002Freverse-engineer-anything",0,"https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates","https:\u002F\u002Fgithub.com\u002FBumpyClock","2026-11-14 03:12:06",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add BumpyClock\u002Fagent-templates --skill reverse-engineer-anything",{"tool":40,"command":41},"bunx","bunx skills add BumpyClock\u002Fagent-templates --skill reverse-engineer-anything",{"tool":43,"command":44},"pnpm","pnpm dlx skills add BumpyClock\u002Fagent-templates --skill reverse-engineer-anything","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills\u002Freverse-engineer-anything\u002FSKILL.md",true,[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fandroid-applications.md","REFERENCE","参考文档",1992,"https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills\u002Freverse-engineer-anything\u002Freferences\u002Fandroid-applications.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fevidence-workflows.md",2261,"https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills\u002Freverse-engineer-anything\u002Freferences\u002Fevidence-workflows.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fjavascript-applications.md",4317,"https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills\u002Freverse-engineer-anything\u002Freferences\u002Fjavascript-applications.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fnative-and-artifacts.md",7994,"https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills\u002Freverse-engineer-anything\u002Freferences\u002Fnative-and-artifacts.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fruntime-observation.md",1811,"https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills\u002Freverse-engineer-anything\u002Freferences\u002Fruntime-observation.md",[71,78,85,92,99,106],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79FEE6E257MWVEBY43X0NVN","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79FEB8GTJC6ZHDK67T40R20","workflow-from-chats","Extract preferences from agent chats → skills, rules, workflow docs. For learning preferences, mining feedback, personalizing workflows.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fworkflow-from-chats\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79FE7TMNGVZZ0M8NV4N0X6N","winui3-csharp-app","WinUI 3 \u002F Windows App SDK desktop apps in C#\u002FXAML. MVVM, bindings, navigation, Mica\u002FAcrylic, windowing, packaging, performance.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwinui3-csharp-app\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79FE31HY46BHN67CQGB7MVJ","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M79FE0N7MGWDG8SCD60FWTV5","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise status update.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M79FDYBJG9QNCQC0MMVBDT80","weekly-review","Produce a short weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fweekly-review\u002FSKILL.md",[],[]]