[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AT6MYBW2JZSWFS4GDNV1CW":3,"skill-same:01M7AT6MYBW2JZSWFS4GDNV1CW":79},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7AT6MYBW2JZSWFS4GDNV1CW","rea",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. Not on the default Load line until Java is installed.","mahik504\u002Forchestra-workflow","mahik504","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184419817?v=4","01M7ASS7EBZ4GXTN2C42N8CJ8T","Mahaveer Singh Gehlot","01M7ASS7EYYYXDMCST6D918XPS",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Frea\u002FLICENSE.rea","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Frea\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rea\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. Not on the default Load line until Java is installed.\nmetadata:\n  version: \"46\"\n---\n\n# REA\n\nAuthorised targets only. The task must say own app, client contract, CTF, or open source. Otherwise stop. APKLab is not ready until Java is installed. Until then the Load line says `not ready`.\n\n# REA\n\nUse REA when a claim depends on a shipped binary or package, decompilation,\nrequested 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\nIf tools are absent, a call is blocked by the client, or a required provider is\nunavailable, read [connection and recovery](references\u002Fconnection-and-recovery.md).\nDiagnose the observed blocker, continue useful supported work, and resume the\noriginal task after repair. Client approval, shell PATH, registration and engine\navailability have different remedies; avoid repeating setup for all of them.\nIf the host times out without a REA result, do not repeat the unchanged call or\nassume work stopped. Read the recovery guide's deadline distinction before retrying.\nIf the MCP connection drops, retry that call once only when it is safe to\nrepeat or known not to have started. If it may already have changed the\ntarget, or it fails again, tell the user and ask them to restart the MCP\nclient. If REA could not start its connection, retry once, then tell the user\nand ask them to restart the MCP client. Do not retry a startup failure that\nreturns the same unchanged result. Run `rea doctor` when REA could not start\nor tools stay missing after that restart. For `cleanup_incomplete`, a retryable\ncapacity limit, or `configuration_invalid`, follow the recovery guide's ladder\nbefore asking for a restart. Read that guide before a second repair attempt.\n\n1. Diagnose without changing REA or client configuration. `npx` may download\n   the package and write to npm's cache. 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`, `omp`, 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, Kuna, Binwalk, or Unblob. Use existing prerequisites; do not install unrelated\nsoftware to repair MCP registration. For an unsupported client, use manual stdio\nregistration with 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.\nPrefer an existing `rea` CLI. When none is installed and REA package acquisition\nis within the authorized scope, use `npx -y rea-agents@latest` in its place.\nConfiguration repair starts with a read-only setup plan; show paths, backups and\nskill replacement before applying authorized changes. Preserve existing approval\nand target-execution boundaries.\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, DMG, or a PyInstaller\n  executable): `open_binary` with the supplied local path; use `inspect_artifact`\n  when its graph and findings help answer the question. A PyInstaller CArchive\n  is the application layer; the bootloader is only the native prefix. Start with\n  `detail: \"summary\"` for large inventories, then use retained inventory views\n  for selected member fields\u002Fpages. A complete small inventory can cost less\n  than extra calls and schemas. Runtime options are metadata, not files.\n  Compact delivery still inventories and hashes members. See the\n  [Python packaged applications guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fpython-packaged-applications.md).\n- Apple app plist, Interface Builder, asset catalog, or keyed archive resources:\n  `open_bundle_resources`, then the selected resource tool. This does not\n  require `CFBundleExecutable` or a deep provider. Resource sessions have no\n  executable digest or binary snapshot; use `open_binary` for native code.\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- Native program behavior, live calls, instrumentation, or command-run effects:\n  choose the matching [native runtime workflow](references\u002Fruntime-observation.md#native-runtime-questions).\n  `open_binary` and `trace_native_values` establish static facts; they do not\n  observe execution. Runtime tools have distinct launch, attach, mutation and\n  cleanup effects, and do not require a preliminary static session unless their\n  own contract says so.\n- User-owned browser page already open: `list_browser_targets`.\n- Browser action the agent must perform (click, type, navigate):\n  `capture_browser_scenario` with declared actions. See\n  [runtime observation](references\u002Fruntime-observation.md) for connect\u002Flaunch\n  and the focused follow-up browser tools.\n- Fiddler Everywhere traffic or a native `.saz` capture: read the\n  [Fiddler workflow](references\u002Fruntime-observation.md#fiddler-everywhere-traffic-debugging).\n  Inspect saved SAZ with `inspect_web_network_capture` and `format: \"saz\"`;\n  connect Everywhere's separate MCP server for live traffic.\n- Retained HAR\u002FSAZ\u002Fnative mitmproxy\u002Faioquic qlog 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. HAR\u002FSAZ\u002Fqlog\n  old-generation heap is `REA_CAPTURE_DECODER_OLD_GENERATION_MIB` (default 192 MiB,\n  floor 8, maximum 16384), set where REA starts. Host memory and `NODE_OPTIONS` do not\n  raise it. 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. Qlog support starts with aioquic 1.5.0\n  JSON 0.3; stream coverage and endpoint loss declarations do not recover bodies\n  or establish network loss. Prefer detail summary, then kind qlog trace\u002Fstream\n  pages; select one trace, stream ID and direction for contribution\u002Frange pages.\n  Facts retain all-recorded-events-before-selection scope. Other qlog layouts\n  and PCAP correlation are unsupported.\n- User-owned Electron runtime already open: `list_electron_targets`. Before an electron-main Inspector attempt, check packaged fuses with `inspect_electron_fuses`; disabled `EnableNodeCliInspectArguments` means the app ignores `--inspect`.\n- Packet-field discovery: `inspect_packet_fields` searches installed protocols\n  and field names\u002Ftypes before choosing fields for `inspect_packet_capture`.\n  Query\u002Fpage the relevant records; registrations do not establish observed traffic.\n- Recorded packet captures: `inspect_packet_capture` with selected TShark fields,\n  display filters and decode-as rules. Requires Linux, util-linux prlimit and `REA_TSHARK_COMMAND`; see\n  [capture guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fpacket-captures.md).\n  Packet limits count input packets before filtering. Output defaults to 50 matching\n  frames; use `match_offset` \u002F `match_limit` for later pages, or explicit null\n  limit for complete matching output. Preserve the source digest across pages.\n  This does not perform live capture.\n  For address\u002FDNS\u002FSNI\u002Fprotocol summaries use `inspect_pcap_capture` with MCP\n  detail summary, then retained kind pcap pages. Requires Wireshark 4.x tshark\n  and capinfos, with Linux prlimit or Windows Job Objects; see\n  [packet summaries](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fpcap-analysis.md).\n  Select an exact DNS question for address pages; page exhaustion does not prove\n  network completeness. This reads recordings and does not acquire traffic.\n- Decoder discovery: `inspect_signal_decoders` searches installed decoder IDs\n  or selected decoder help, including channels and options. Query and page the\n  relevant details before choosing settings; this does not scan hardware.\n- Recorded logic\u002Fsignal traces: `decode_signal_recording` with explicit decoder,\n  channel and protocol settings. On Linux with util-linux prlimit, supply sigrok-cli 0.7.2 through\n  `REA_SIGROK_COMMAND`; see [recording guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fsignal-recordings.md).\n  Output defaults to 50 literal lines; select annotation classes and page with\n  `line_offset` \u002F `line_limit`, or explicit null for all remaining output.\n  Window counts are display lines, not annotations or samples. Preserve source digests across pages.\n  This reads existing files; it does not acquire hardware signals.\n- Explicit local WebAssembly artifact: `inspect_wasm_artifact`. Supply WABT 1.0.42\n  through `REA_WABT_BIN_DIRECTORY`; retain exact byte\u002Ftool identity and decoded WAT.\n  Select JavaScript glue and candidate paths explicitly and preserve URL\u002Fpath\n  ambiguity. No implicit fetch or target execution; WAT is not original source.\n  See the [WASM guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fwasm-artifacts.md).\n- Explicit local Android APK (or ZIP\u002FAAB) signing: `inspect_apk_signature`.\n  Prefer its summary or selected signer\u002Fdigest\u002Flineage page; retain complete\n  Evidence and use `inspect_analysis_view` kind `apk-signature` for follow-ups.\n  Reports which schemes are present (v1 JAR, v2, v3, v3.1), each signer's\n  certificate SHA-256 fingerprint (v1 included, from its PKCS#7 block), v3 key-rotation lineage, source stamp, and\n  whether each signed digest still matches the bytes (self-consistency). This\n  is identity and integrity, not a trust or authenticity verdict.\n  See the [APK signature guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fapk-signature.md).\n- Explicit local EVM bytecode carrier: `inspect_evm_interface` with caller-selected\n  `raw` or `hex` encoding. The owned worker deadline is `timeout_ms` (default\n  30000 ms, range 1..2147483647, next call). It does not raise the fixed byte,\n  address-space, or CPU allowances. Preserve carrier\u002Fdecoded digests and treat selectors,\n  argument strings and mutability as inferred candidates; this performs no chain\n  lookup or target execution. For the complete inferred interface without hex or\n  duplicate stdout, discover support and select `detail: \"summary\"`; complete\n  Evidence stays retained under its original identity. Use the returned\n  `parent_evidence_id` for exact function or `bytecode_hex`\u002Fstdout\u002Fstderr pages.\n  Candidate coverage does not establish interface completeness. See the\n  [EVM bytecode guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fevm-bytecode.md).\n- Embedded Go compiler, module or build-setting metadata: `inspect_go_binary`\n  with the explicit local file. This built-in target-free inspection requires no\n  Go installation or disassembler. Preserve raw module bytes and source ranges;\n  absent metadata does not prove a binary is not Go, and unparsed text records\n  remain explicit. See the\n  [Go binary guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fgo-binaries.md).\n- Embedded CUDA\u002FHIP code objects: `inspect_gpu_code_objects`; inventory targets\n  first, then decode selected payloads and query retained GPU Evidence.\n- Bundled GGUF or safetensors model declarations: `inspect_model_artifact`\n  with the explicit local file. Default header hashing leaves full-file identity\n  unknown; `hash: \"full\"` additionally reads all weights for SHA-256. MCP returns\n  retained summaries; optional `view` selects one page in the initial call. Use\n  `inspect_analysis_view` kind `model-artifact` for\n  batched metadata keys, tensor names or type totals, selected fields and pages.\n  Preserve header-scoped indices and array preview omissions; do not infer model\n  behavior from declared architecture or tensor types. See the\n  [model file guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fmodel-artifacts.md).\n- Unity IL2CPP names, member owners and string literals from `global-metadata.dat`:\n  `inspect_il2cpp_metadata` with the explicit local file; MCP defaults to compact\n  counts. Query sections, images, types, methods, fields, properties, events,\n  parameters or string_literals through `inspect_analysis_view`\n  with the returned `parent_evidence_id`, using exact filters, batch indices and\n  selected fields. Parameters accept `method_indices`, avoiding a scan of all\n  parameter pages. Missing collections in historical Evidence remain unknown.\n  Versions 24, 27, 29, 31 and 39; no Unity, IL2CPP\n  binary or disassembler is run. Unrecognized magic (possibly encrypted) and\n  other versions are unsupported. Optional matching `binary_path` enables static native addresses and type references; query `method_addresses` with indices or addresses\u002Fstates, preserving every shared-body method and both artifact identities. Without a linked binary native counts remain unknown. Byte-pattern fallback is inferred; no runtime behavior or same-build pairing is proved. See the\n  [IL2CPP metadata guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fil2cpp-metadata.md).\n- Embedded cargo-auditable Rust dependency metadata: `inspect_rust_binary`\n  with the explicit local ELF, PE, or thin Mach-O file. This built-in\n  target-free inspection requires no Rust installation or disassembler. Preserve\n  package order, dependency indices, and the section file range. A missing\n  `.dep-v0` section is null metadata, not proof the binary has no dependencies.\n  A rustc commit hash is an inference from a read-only `\u002Frustc\u002F\u003C40-hex>\u002F` path.\n  For selected crates, use `view: {collection: \"packages\", names: [...],\n  fields: [\"name\", \"version\", \"source\"]}` on the first call; explicitly include\n  `dependencies` for direct index references. Use `detail: \"summary\"` for counts\n  and ranges, or retained `inspect_analysis_view` Rust package\u002Fedge pages for\n  subsequent filters. Keep the complete parent Evidence accessible; CLI compact\n  delivery requires `--evidence_output`.\n  See the\n  [Rust binary guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Frust-binaries.md).\n- PE Authenticode certificate table: `inspect_pe_certificates` with the explicit\n  local PE32\u002FPE32+ file. This built-in target-free inspection requires no\n  Windows SDK. Preserve WIN_CERTIFICATE ranges, types, payload SHA-256, and\n  PKCS#7 signer\u002FX.509 identity fields, including `subject_key_identifier_hex`\n  when the signer uses that form. A missing security directory is observed\n  absence of that table, not proof the image is unsigned in every catalog sense.\n  Signatures are not verified. See the\n  [PE certificate guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fpe-certificates.md).\n- ELF note tables: `inspect_elf_notes` with the explicit local ELF32\u002FELF64\n  file. This built-in target-free inspection requires no disassembler. Preserve\n  PT_NOTE and SHT_NOTE ranges, owners, types, descriptor SHA-256, and GNU\n  build-id or ABI-tag fields. A missing table is observed absence of those\n  declarations, not proof the image never carried notes. See the\n  [ELF notes guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Felf-notes.md).\n- CPython 3.7–3.13 `.pyc` header, nested marshal code objects and bytecode\n  identity: `inspect_python_pyc` with the explicit local file. This built-in\n  target-free inspection requires no Python installation. Preserve magic,\n  PEP 552 hash or mtime\u002Fsize, nested names, and bytecode SHA-256. Bytecode is\n  not decompiled, and a decoded header does not prove the matching `.py` is\n  present. See the\n  [CPython pyc guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fpython-pyc.md).\n- Erlang BEAM IFF container: `inspect_erlang_beam` with the explicit local\n  `.beam` file. This built-in target-free inspection requires no Erlang\n  installation. Preserve chunk names, atom order, export\u002Fimport\u002Flambda tables,\n  and the Code header. Missing optional tables stay null. Bytecode is not\n  executed. See the\n  [Erlang BEAM guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Ferlang-beam.md).\n\n- Explicit local SQLite database snapshot: `inspect_sqlite_database`. Inspect\n  with Node.js 24.x >=24.15 or 26+ providing native SQLite limits. Read schema\n  first (compact inventory by default), or select an exact ordinary table\n  and `columns` when rows are needed. Defaults are selected-table schema and\n  20 rows; request `schema_scope: \"database\"` for the complete stored schema. Preserve both database and existing sibling WAL identity; row samples\n  report truncation and have unspecified order. Use a quiescent snapshot rather\n  than assuming a live database\u002FWAL pair was copied atomically. See the\n  [SQLite guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fsqlite-databases.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- PE resource type\u002Fname\u002Flanguage trees and static icon group references:\n  `inspect_pe_resources` with an explicit path. This portable operation requires\n  no active target or engine; opaque payloads retain file ranges and SHA-256.\n- PE export directories and ELF dynamic-symbol exports: `inspect_native_exports`\n  with an explicit path; portable, no active target or engine.\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\nWith `REA_KUNA_COMMAND` configured, `provider_id: \"kuna\"` answers procedure\nlists, lookups, pseudocode, assembly and `analyze_function` from Kuna's cached\nwhole-program export. Callers\u002Fcallees use a separate body-free graph shared by\nthe session; `xrefs` returns exact-address incoming sites and filters forwarding\naliases. These queries and inventory lookups do not trigger a C export. Indirect\ntargets remain unknown and can make relationship coverage partial. Reference\ncaches expire on close; a fresh CLI process repeats the native reference walk.\nTyped references, CFG, raw-memory tools and annotations remain unsupported. A cold first\nanswer can come from a single-function run (its limitations say so); assembly\nwaits for the export. For pseudocode and assembly, `raw_result.source` names the\ncached `.c`\u002F`.asm` file and byte span, which you may search directly instead of\ncalling per function. See the\n[Kuna provider guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fkuna-provider.md).\n\nIf the user says only \"my app\" without a name, path, or target already selected\nfor this task, ask which app before searching for artifacts. Paths in unrelated\nsaved reports and nearby test fixtures do not select the user's target. Resolve\nan actual human-readable app name to one clear installed artifact when possible;\nask when matches are ambiguous. 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. Expand each\ngroup's `names` into entries, inheriting the inventory-level client requirements\nunless the group overrides them. In its closed effect and annotation vocabularies,\nlisted flags are true and omitted known flags are false. The grouped name union\nis the complete tool inventory; use `tools\u002Flist` for canonical tool schemas.\nProvider candidate facts describe possible providers, while top-level session\ncapabilities describe the current route and `analysis_provider_binding` names the\nselected provider. Do not treat those scopes as interchangeable.\n\nFor a Ghidra startup timeout on a large native target, follow\n[deadline recovery](references\u002Fnative-and-artifacts.md#ghidra-startup-deadline-recovery)\nbefore abandoning deep analysis or repeating the same cold import. The default\n330 seconds is configurable; changing the server's environment requires a new\nREA process.\n\n## Work summary-first\n\nStart with the default result and use its inline Evidence and graph context.\nFor a JavaScript application or ELF layout whose size is unknown or large,\ncall `analyze_javascript_application` or `inspect_binary_layout` with\n`\"detail\": \"summary\"`, then inspect the retained `parent_evidence_id` with\n`inspect_analysis_view`.\nPage module identities and select the returned `node_id` before requesting an\nitem; a single file path can represent several graph roles. Do not repeat an\nidentical analysis or rejected call without a changed input or resolved blocker.\nRecheck session state when a lifecycle change makes that status useful.\nMake 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\nWhen the retained parent ID is unknown, use `get_evidence_bundle` with\n`detail: \"summary\"` and exact filters for operation, target SHA-256,\nanalysis-profile digest or canonical procedure address. Select its returned\nEvidence ID for the next view instead of requesting the complete bundle.\n`retention: \"complete-record\"` means the whole record is stored; native\nvalue-flow truncation and unknown metadata remain separate. For an exported\nportable bundle, use `rea inspect-evidence-bundle` with JSON containing `path`,\n`detail: \"summary\"` and the same `filters`. Reading that file still requires\nvalidating its full contents within the local memory budget.\n\nA client can also truncate a successful tool result without a REA transport\nerror. Treat that preview as incomplete; use the retained parent ID for smaller\nviews or export when the full record is needed. Do not parse the preview as\ncanonical JSON or repeat the producer. For JavaScript, read the\n[module-view and trace recipes](references\u002Fjavascript-applications.md) before\ndrilling into a large graph; a broad bidirectional trace can expand unrelated\ncontainment relationships even after summary analysis.\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.\nThe agent client can independently require approval. Follow the declared request\nscope and the host's actual access requirements; use the recovery guide for an\nobserved client-policy rejection.\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- Native instrumentation, debugger and process capture; browser\u002FElectron\n  observation; static\u002Fruntime comparison:\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\nAuthorised targets only. The task must say own app, client contract, CTF, or open source. Otherwise stop. APKLab is not ready until Java is installed. Until then the Load line says `not ready`.\n\n# REA\n\nUse REA when a claim depends on a shipped binary or package, decompilation,\nrequested 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\nIf tools are absent, a call is blocked by the client, or a required provider is\nunavailable, read [connection and recovery](references\u002Fconnection-and-recovery.md).\nDiagnose the observed blocker, continue useful supported work, and resume the\noriginal task after repair. Client approval, shell PATH, registration and engine\navailability have different remedies; avoid repeating setup for all of them.\nIf the host times out without a REA result, do not repeat the unchanged call or\nassume work stopped. Read the recovery guide's deadline distinction before retrying.\nIf the MCP connection drops, retry that call once only when it is safe to\nrepeat or known not to have started. If it may already have changed the\ntarget, or it fails again, tell the user and ask them to restart the MCP\nclient. If REA could not start its connection, retry once, then tell the user\nand ask them to restart the MCP client. Do not retry a startup failure that\nreturns the same unchanged result. Run `rea doctor` when REA could not start\nor tools stay missing after that restart. For `cleanup_incomplete`, a retryable\ncapacity limit, or `configuration_invalid`, follow the recovery guide's ladder\nbefore asking for a restart. Read that guide before a second repair attempt.\n\n1. Diagnose without changing REA or client configuration. `npx` may download\n   the package and write to npm's cache. 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`, `omp`, 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, Kuna, Binwalk, or Unblob. Use existing prerequisites; do not install unrelated\nsoftware to repair MCP registration. For an unsupported client, use manual stdio\nregistration with 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.\nPrefer an existing `rea` CLI. When none is installed and REA package acquisition\nis within the authorized scope, use `npx -y rea-agents@latest` in its place.\nConfiguration repair starts with a read-only setup plan; show paths, backups and\nskill replacement before applying authorized changes. Preserve existing approval\nand target-execution boundaries.\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, DMG, or a PyInstaller\n  executable): `open_binary` with the supplied local path; use `inspect_artifact`\n  when its graph and findings help answer the question. A PyInstaller CArchive\n  is the application layer; the bootloader is only the native prefix. Start with\n  `detail: \"summary\"` for large inventories, then use retained inventory views\n  for selected member fields\u002Fpages. A complete small inventory can cost less\n  than extra calls and schemas. Runtime options are metadata, not files.\n  Compact delivery still inventories and hashes members. See the\n  [Python packaged applications guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fpython-packaged-applications.md).\n- Apple app plist, Interface Builder, asset catalog, or keyed archive resources:\n  `open_bundle_resources`, then the selected resource tool. This does not\n  require `CFBundleExecutable` or a deep provider. Resource sessions have no\n  executable digest or binary snapshot; use `open_binary` for native code.\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- Native program behavior, live calls, instrumentation, or command-run effects:\n  choose the matching [native runtime workflow](references\u002Fruntime-observation.md#native-runtime-questions).\n  `open_binary` and `trace_native_values` establish static facts; they do not\n  observe execution. Runtime tools have distinct launch, attach, mutation and\n  cleanup effects, and do not require a preliminary static session unless their\n  own contract says so.\n- User-owned browser page already open: `list_browser_targets`.\n- Browser action the agent must perform (click, type, navigate):\n  `capture_browser_scenario` with declared actions. See\n  [runtime observation](references\u002Fruntime-observation.md) for connect\u002Flaunch\n  and the focused follow-up browser tools.\n- Fiddler Everywhere traffic or a native `.saz` capture: read the\n  [Fiddler workflow](references\u002Fruntime-observation.md#fiddler-everywhere-traffic-debugging).\n  Inspect saved SAZ with `inspect_web_network_capture` and `format: \"saz\"`;\n  connect Everywhere's separate MCP server for live traffic.\n- Retained HAR\u002FSAZ\u002Fnative mitmproxy\u002Faioquic qlog 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. HAR\u002FSAZ\u002Fqlog\n  old-generation heap is `REA_CAPTURE_DECODER_OLD_GENERATION_MIB` (default 192 MiB,\n  floor 8, maximum 16384), set where REA starts. Host memory and `NODE_OPTIONS` do not\n  raise it. 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. Qlog support starts with aioquic 1.5.0\n  JSON 0.3; stream coverage and endpoint loss declarations do not recover bodies\n  or establish network loss. Prefer detail summary, then kind qlog trace\u002Fstream\n  pages; select one trace, stream ID and direction for contribution\u002Frange pages.\n  Facts retain all-recorded-events-before-selection scope. Other qlog layouts\n  and PCAP correlation are unsupported.\n- User-owned Electron runtime already open: `list_electron_targets`. Before an electron-main Inspector attempt, check packaged fuses with `inspect_electron_fuses`; disabled `EnableNodeCliInspectArguments` means the app ignores `--inspect`.\n- Packet-field discovery: `inspect_packet_fields` searches installed protocols\n  and field names\u002Ftypes before choosing fields for `inspect_packet_capture`.\n  Query\u002Fpage the relevant records; registrations do not establish observed traffic.\n- Recorded packet captures: `inspect_packet_capture` with selected TShark fields,\n  display filters and decode-as rules. Requires Linux, util-linux prlimit and `REA_TSHARK_COMMAND`; see\n  [capture guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fpacket-captures.md).\n  Packet limits count input packets before filtering. Output defaults to 50 matching\n  frames; use `match_offset` \u002F `match_limit` for later pages, or explicit null\n  limit for complete matching output. Preserve the source digest across pages.\n  This does not perform live capture.\n  For address\u002FDNS\u002FSNI\u002Fprotocol summaries use `inspect_pcap_capture` with MCP\n  detail summary, then retained kind pcap pages. Requires Wireshark 4.x tshark\n  and capinfos, with Linux prlimit or Windows Job Objects; see\n  [packet summaries](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fpcap-analysis.md).\n  Select an exact DNS question for address pages; page exhaustion does not prove\n  network completeness. This reads recordings and does not acquire traffic.\n- Decoder discovery: `inspect_signal_decoders` searches installed decoder IDs\n  or selected decoder help, including channels and options. Query and page the\n  relevant details before choosing settings; this does not scan hardware.\n- Recorded logic\u002Fsignal traces: `decode_signal_recording` with explicit decoder,\n  channel and protocol settings. On Linux with util-linux prlimit, supply sigrok-cli 0.7.2 through\n  `REA_SIGROK_COMMAND`; see [recording guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fsignal-recordings.md).\n  Output defaults to 50 literal lines; select annotation classes and page with\n  `line_offset` \u002F `line_limit`, or explicit null for all remaining output.\n  Window counts are display lines, not annotations or samples. Preserve source digests across pages.\n  This reads existing files; it does not acquire hardware signals.\n- Explicit local WebAssembly artifact: `inspect_wasm_artifact`. Supply WABT 1.0.42\n  through `REA_WABT_BIN_DIRECTORY`; retain exact byte\u002Ftool identity and decoded WAT.\n  Select JavaScript glue and candidate paths explicitly and preserve URL\u002Fpath\n  ambiguity. No implicit fetch or target execution; WAT is not original source.\n  See the [WASM guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fwasm-artifacts.md).\n- Explicit local Android APK (or ZIP\u002FAAB) signing: `inspect_apk_signature`.\n  Prefer its summary or selected signer\u002Fdigest\u002Flineage page; retain complete\n  Evidence and use `inspect_analysis_view` kind `apk-signature` for follow-ups.\n  Reports which schemes are present (v1 JAR, v2, v3, v3.1), each signer's\n  certificate SHA-256 fingerprint (v1 included, from its PKCS#7 block), v3 key-rotation lineage, source stamp, and\n  whether each signed digest still matches the bytes (self-consistency). This\n  is identity and integrity, not a trust or authenticity verdict.\n  See the [APK signature guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fapk-signature.md).\n- Explicit local EVM bytecode carrier: `inspect_evm_interface` with caller-selected\n  `raw` or `hex` encoding. The owned worker deadline is `timeout_ms` (default\n  30000 ms, range 1..2147483647, next call). It does not raise the fixed byte,\n  address-space, or CPU allowances. Preserve carrier\u002Fdecoded digests and treat selectors,\n  argument strings and mutability as inferred candidates; this performs no chain\n  lookup or target execution. For the complete inferred interface without hex or\n  duplicate stdout, discover support and select `detail: \"summary\"`; complete\n  Evidence stays retained under its original identity. Use the returned\n  `parent_evidence_id` for exact function or `bytecode_hex`\u002Fstdout\u002Fstderr pages.\n  Candidate coverage does not establish interface completeness. See the\n  [EVM bytecode guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fevm-bytecode.md).\n- Embedded Go compiler, module or build-setting metadata: `inspect_go_binary`\n  with the explicit local file. This built-in target-free inspection requires no\n  Go installation or disassembler. Preserve raw module bytes and source ranges;\n  absent metadata does not prove a binary is not Go, and unparsed text records\n  remain explicit. See the\n  [Go binary guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fgo-binaries.md).\n- Embedded CUDA\u002FHIP code objects: `inspect_gpu_code_objects`; inventory targets\n  first, then decode selected payloads and query retained GPU Evidence.\n- Bundled GGUF or safetensors model declarations: `inspect_model_artifact`\n  with the explicit local file. Default header hashing leaves full-file identity\n  unknown; `hash: \"full\"` additionally reads all weights for SHA-256. MCP returns\n  retained summaries; optional `view` selects one page in the initial call. Use\n  `inspect_analysis_view` kind `model-artifact` for\n  batched metadata keys, tensor names or type totals, selected fields and pages.\n  Preserve header-scoped indices and array preview omissions; do not infer model\n  behavior from declared architecture or tensor types. See the\n  [model file guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fmodel-artifacts.md).\n- Unity IL2CPP names, member owners and string literals from `global-metadata.dat`:\n  `inspect_il2cpp_metadata` with the explicit local file; MCP defaults to compact\n  counts. Query sections, images, types, methods, fields, properties, events,\n  parameters or string_literals through `inspect_analysis_view`\n  with the returned `parent_evidence_id`, using exact filters, batch indices and\n  selected fields. Parameters accept `method_indices`, avoiding a scan of all\n  parameter pages. Missing collections in historical Evidence remain unknown.\n  Versions 24, 27, 29, 31 and 39; no Unity, IL2CPP\n  binary or disassembler is run. Unrecognized magic (possibly encrypted) and\n  other versions are unsupported. Optional matching `binary_path` enables static native addresses and type references; query `method_addresses` with indices or addresses\u002Fstates, preserving every shared-body method and both artifact identities. Without a linked binary native counts remain unknown. Byte-pattern fallback is inferred; no runtime behavior or same-build pairing is proved. See the\n  [IL2CPP metadata guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fil2cpp-metadata.md).\n- Embedded cargo-auditable Rust dependency metadata: `inspect_rust_binary`\n  with the explicit local ELF, PE, or thin Mach-O file. This built-in\n  target-free inspection requires no Rust installation or disassembler. Preserve\n  package order, dependency indices, and the section file range. A missing\n  `.dep-v0` section is null metadata, not proof the binary has no dependencies.\n  A rustc commit hash is an inference from a read-only `\u002Frustc\u002F\u003C40-hex>\u002F` path.\n  For selected crates, use `view: {collection: \"packages\", names: [...],\n  fields: [\"name\", \"version\", \"source\"]}` on the first call; explicitly include\n  `dependencies` for direct index references. Use `detail: \"summary\"` for counts\n  and ranges, or retained `inspect_analysis_view` Rust package\u002Fedge pages for\n  subsequent filters. Keep the complete parent Evidence accessible; CLI compact\n  delivery requires `--evidence_output`.\n  See the\n  [Rust binary guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Frust-binaries.md).\n- PE Authenticode certificate table: `inspect_pe_certificates` with the explicit\n  local PE32\u002FPE32+ file. This built-in target-free inspection requires no\n  Windows SDK. Preserve WIN_CERTIFICATE ranges, types, payload SHA-256, and\n  PKCS#7 signer\u002FX.509 identity fields, including `subject_key_identifier_hex`\n  when the signer uses that form. A missing security directory is observed\n  absence of that table, not proof the image is unsigned in every catalog sense.\n  Signatures are not verified. See the\n  [PE certificate guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fpe-certificates.md).\n- ELF note tables: `inspect_elf_notes` with the explicit local ELF32\u002FELF64\n  file. This built-in target-free inspection requires no disassembler. Preserve\n  PT_NOTE and SHT_NOTE ranges, owners, types, descriptor SHA-256, and GNU\n  build-id or ABI-tag fields. A missing table is observed absence of those\n  declarations, not proof the image never carried notes. See the\n  [ELF notes guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Felf-notes.md).\n- CPython 3.7–3.13 `.pyc` header, nested marshal code objects and bytecode\n  identity: `inspect_python_pyc` with the explicit local file. This built-in\n  target-free inspection requires no Python installation. Preserve magic,\n  PEP 552 hash or mtime\u002Fsize, nested names, and bytecode SHA-256. Bytecode is\n  not decompiled, and a decoded header does not prove the matching `.py` is\n  present. See the\n  [CPython pyc guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fpython-pyc.md).\n- Erlang BEAM IFF container: `inspect_erlang_beam` with the explicit local\n  `.beam` file. This built-in target-free inspection requires no Erlang\n  installation. Preserve chunk names, atom order, export\u002Fimport\u002Flambda tables,\n  and the Code header. Missing optional tables stay null. Bytecode is not\n  executed. See the\n  [Erlang BEAM guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Ferlang-beam.md).\n\n- Explicit local SQLite database snapshot: `inspect_sqlite_database`. Inspect\n  with Node.js 24.x >=24.15 or 26+ providing native SQLite limits. Read schema\n  first (compact inventory by default), or select an exact ordinary table\n  and `columns` when rows are needed. Defaults are selected-table schema and\n  20 rows; request `schema_scope: \"database\"` for the complete stored schema. Preserve both database and existing sibling WAL identity; row samples\n  report truncation and have unspecified order. Use a quiescent snapshot rather\n  than assuming a live database\u002FWAL pair was copied atomically. See the\n  [SQLite guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fsqlite-databases.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- PE resource type\u002Fname\u002Flanguage trees and static icon group references:\n  `inspect_pe_resources` with an explicit path. This portable operation requires\n  no active target or engine; opaque payloads retain file ranges and SHA-256.\n- PE export directories and ELF dynamic-symbol exports: `inspect_native_exports`\n  with an explicit path; portable, no active target or engine.\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\nWith `REA_KUNA_COMMAND` configured, `provider_id: \"kuna\"` answers procedure\nlists, lookups, pseudocode, assembly and `analyze_function` from Kuna's cached\nwhole-program export. Callers\u002Fcallees use a separate body-free graph shared by\nthe session; `xrefs` returns exact-address incoming sites and filters forwarding\naliases. These queries and inventory lookups do not trigger a C export. Indirect\ntargets remain unknown and can make relationship coverage partial. Reference\ncaches expire on close; a fresh CLI process repeats the native reference walk.\nTyped references, CFG, raw-memory tools and annotations remain unsupported. A cold first\nanswer can come from a single-function run (its limitations say so); assembly\nwaits for the export. For pseudocode and assembly, `raw_result.source` names the\ncached `.c`\u002F`.asm` file and byte span, which you may search directly instead of\ncalling per function. See the\n[Kuna provider guide](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fblob\u002Fmain\u002Fdocs\u002Fkuna-provider.md).\n\nIf the user says only \"my app\" without a name, path, or target already selected\nfor this task, ask which app before searching for artifacts. Paths in unrelated\nsaved reports and nearby test fixtures do not select the user's target. Resolve\nan actual human-readable app name to one clear installed artifact when possible;\nask when matches are ambiguous. 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. Expand each\ngroup's `names` into entries, inheriting the inventory-level client requirements\nunless the group overrides them. In its closed effect and annotation vocabularies,\nlisted flags are true and omitted known flags are false. The grouped name union\nis the complete tool inventory; use `tools\u002Flist` for canonical tool schemas.\nProvider candidate facts describe possible providers, while top-level session\ncapabilities describe the current route and `analysis_provider_binding` names the\nselected provider. Do not treat those scopes as interchangeable.\n\nFor a Ghidra startup timeout on a large native target, follow\n[deadline recovery](references\u002Fnative-and-artifacts.md#ghidra-startup-deadline-recovery)\nbefore abandoning deep analysis or repeating the same cold import. The default\n330 seconds is configurable; changing the server's environment requires a new\nREA process.\n\n## Work summary-first\n\nStart with the default result and use its inline Evidence and graph context.\nFor a JavaScript application or ELF layout whose size is unknown or large,\ncall `analyze_javascript_application` or `inspect_binary_layout` with\n`\"detail\": \"summary\"`, then inspect the retained `parent_evidence_id` with\n`inspect_analysis_view`.\nPage module identities and select the returned `node_id` before requesting an\nitem; a single file path can represent several graph roles. Do not repeat an\nidentical analysis or rejected call without a changed input or resolved blocker.\nRecheck session state when a lifecycle change makes that status useful.\nMake 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\nWhen the retained parent ID is unknown, use `get_evidence_bundle` with\n`detail: \"summary\"` and exact filters for operation, target SHA-256,\nanalysis-profile digest or canonical procedure address. Select its returned\nEvidence ID for the next view instead of requesting the complete bundle.\n`retention: \"complete-record\"` means the whole record is stored; native\nvalue-flow truncation and unknown metadata remain separate. For an exported\nportable bundle, use `rea inspect-evidence-bundle` with JSON containing `path`,\n`detail: \"summary\"` and the same `filters`. Reading that file still requires\nvalidating its full contents within the local memory budget.\n\nA client can also truncate a successful tool result without a REA transport\nerror. Treat that preview as incomplete; use the retained parent ID for smaller\nviews or export when the full record is needed. Do not parse the preview as\ncanonical JSON or repeat the producer. For JavaScript, read the\n[module-view and trace recipes](references\u002Fjavascript-applications.md) before\ndrilling into a large graph; a broad bidirectional trace can expand unrelated\ncontainment relationships even after summary analysis.\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.\nThe agent client can independently require approval. Follow the declared request\nscope and the host's actual access requirements; use the recovery guide for an\nobserved client-policy rejection.\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- Native instrumentation, debugger and process capture; browser\u002FElectron\n  observation; static\u002Fruntime comparison:\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":25,"description":7},{"version":26},"46","main","46209ae875b23589c19befc213c303406d14334d","skills\u002Frea",0,"https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow","https:\u002F\u002Fgithub.com\u002Fmahik504","2026-11-13 18:13:16",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add mahik504\u002Forchestra-workflow --skill rea",{"tool":40,"command":41},"bunx","bunx skills add mahik504\u002Forchestra-workflow --skill rea",{"tool":43,"command":44},"pnpm","pnpm dlx skills add mahik504\u002Forchestra-workflow --skill rea","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Frea\u002FSKILL.md",true,[48,53,59,63,67,71,75],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":16},"LICENSE.rea","LICENSE","许可证",1064,{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fandroid-applications.md","REFERENCE","参考文档",2318,"https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Frea\u002Freferences\u002Fandroid-applications.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fconnection-and-recovery.md",16650,"https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Frea\u002Freferences\u002Fconnection-and-recovery.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fevidence-workflows.md",7449,"https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Frea\u002Freferences\u002Fevidence-workflows.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fjavascript-applications.md",13430,"https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Frea\u002Freferences\u002Fjavascript-applications.md",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fnative-and-artifacts.md",33862,"https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Frea\u002Freferences\u002Fnative-and-artifacts.md",{"path":76,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fruntime-observation.md",11719,"https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Frea\u002Freferences\u002Fruntime-observation.md",[80,88,97,104,112,120],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":20},"01M7ATAT5KQ106HYZC60TJ6SXK","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FLICENSE.superpowers","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":20},"01M7ATANN9YAGPJES4BEBC8GKK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":20},"01M7ATAGXKX55X2XG8BFY71HJB","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\". Do not load on Plan-only or backend-only jobs.","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":20},"01M7ATACA5MVF8FG4C5JTT5ERD","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FLICENSE.superpowers","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":20},"01M7ATA7J6SQHX9ESPBW96T28V","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fusing-git-worktrees\u002FLICENSE.superpowers","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":20},"01M7ATA0N5YPZ4Q2BJ9QA4TZAX","unslop","Turns vibecoded, AI-looking UI into a designed interface with its own character. Finds a direction from the product itself, then fixes spacing, color, icons, copy, type, layout, details, visuals and motion in that order, and can generate a real hero visual with an image tool when one is available. Use when the user asks to unslop, polish, clean up or redesign a screen so it stops looking AI-generated, or when a UI shows the usual tells like purple gradients, glows, gradient text, emoji labels, \"New ✨\" badges, glossy blobs, uppercase tracked labels, pulsing elements or uneven spacing. Works on React, Tailwind, HTML and CSS, for dashboards, apps and landing pages.","CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmahik504\u002Forchestra-workflow\u002Fblob\u002Fmain\u002Fskills\u002Funslop\u002FSKILL.md",[],[]]