reverse-engineer
Installation
SKILL.md
Reverse Engineer
Reverse-engineer an external system into two things: a teardown (feature inventory, a registry of where to read, CLI and contract specs, optionally a security audit) and a steal-map (the decision: what to adopt into our surfaces and what to leave behind). A decision row that must cite evidence can be re-checked by anyone; a decision made from impressions cannot be re-checked by its own author. Deciding from a competitor's README is the failure this skill exists to prevent.
⚠️ Constraints — Hard Guardrails (MANDATORY)
- Only operate on code/binaries you own or have explicit written authorization to analyze — this matters because unauthorized teardown is the legal/IP line.
- Do not provide steps to bypass protections/ToS or to extract proprietary source/system prompts.
- Do not output reconstructed proprietary source or embedded prompts (index only; redact in reports) — to prevent reproducing protected IP.
- Redact secrets/tokens/keys if encountered. The output validator runs this skill's
scripts/security/scan_secrets.shover the whole output dir in every phase; a hit fails it until you redact. - Always separate docs say vs code proves vs hosted/control-plane.