$npx -y skills add SamarthaKV29/antigravity-god-mode --skill anti-reversing-techniquesUnderstand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or understanding software protection mechanisms.
| 1 | > **AUTHORIZED USE ONLY**: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis: |
| 2 | > 1. **Verify authorization**: Confirm you have explicit written permission from the software owner, or are operating within a legitimate security context (CTF, authorized pentest, malware analysis, security research) |
| 3 | > 2. **Document scope**: Ensure your activities fall within the defined scope of your authorization |
| 4 | > 3. **Legal compliance**: Understand that unauthorized bypassing of software protection may violate laws (CFAA, DMCA anti-circumvention, etc.) |
| 5 | > |
| 6 | > **Legitimate use cases**: Malware analysis, authorized penetration testing, CTF competitions, academic security research, analyzing software you own/have rights to |
| 7 | |
| 8 | ## Use this skill when |
| 9 | |
| 10 | - Analyzing protected binaries with explicit authorization |
| 11 | - Conducting malware analysis or security research in scope |
| 12 | - Participating in CTFs or approved training exercises |
| 13 | - Understanding anti-debugging or obfuscation techniques for defense |
| 14 | |
| 15 | ## Do not use this skill when |
| 16 | |
| 17 | - You lack written authorization or a defined scope |
| 18 | - The goal is to bypass protections for piracy or misuse |
| 19 | - Legal or policy restrictions prohibit analysis |
| 20 | |
| 21 | ## Instructions |
| 22 | |
| 23 | 1. Confirm written authorization, scope, and legal constraints. |
| 24 | 2. Identify protection mechanisms and choose safe analysis methods. |
| 25 | 3. Document findings and avoid modifying artifacts unnecessarily. |
| 26 | 4. Provide defensive recommendations and mitigation guidance. |
| 27 | |
| 28 | ## Safety |
| 29 | |
| 30 | - Do not share bypass steps outside the authorized context. |
| 31 | - Preserve evidence and maintain chain-of-custody for malware cases. |
| 32 | |
| 33 | Refer to `resources/implementation-playbook.md` for detailed techniques and examples. |
| 34 | |
| 35 | ## Resources |
| 36 | |
| 37 | - `resources/implementation-playbook.md` for detailed techniques and examples. |