Agent Skills
› rmyndharis/antigravity-skills
› anti-reversing-techniques
anti-reversing-techniques
GitHub用于在授权场景下分析软件保护机制、混淆及反调试技术。适用于恶意软件分析、渗透测试、CTF及安全研究，提供防御建议并强调合规性与证据保全。
Trigger Scenarios
分析受保护的二进制文件
进行恶意软件分析或安全研究
参与CTF比赛或授权训练
理解反调试或混淆技术
Install
npx skills add rmyndharis/antigravity-skills --skill anti-reversing-techniques -g -y
SKILL.md
Frontmatter
{
"name": "anti-reversing-techniques",
"description": "Understand 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."
}
AUTHORIZED USE ONLY: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis:
- 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)
- Document scope: Ensure your activities fall within the defined scope of your authorization
- Legal compliance: Understand that unauthorized bypassing of software protection may violate laws (CFAA, DMCA anti-circumvention, etc.)
Legitimate use cases: Malware analysis, authorized penetration testing, CTF competitions, academic security research, analyzing software you own/have rights to
Use this skill when
- Analyzing protected binaries with explicit authorization
- Conducting malware analysis or security research in scope
- Participating in CTFs or approved training exercises
- Understanding anti-debugging or obfuscation techniques for defense
Do not use this skill when
- You lack written authorization or a defined scope
- The goal is to bypass protections for piracy or misuse
- Legal or policy restrictions prohibit analysis
Instructions
- Confirm written authorization, scope, and legal constraints.
- Identify protection mechanisms and choose safe analysis methods.
- Document findings and avoid modifying artifacts unnecessarily.
- Provide defensive recommendations and mitigation guidance.
Safety
- Do not share bypass steps outside the authorized context.
- Preserve evidence and maintain chain-of-custody for malware cases.
Refer to resources/implementation-playbook.md for detailed techniques and examples.
Resources
resources/implementation-playbook.mdfor detailed techniques and examples.
Version History
- e63f7dd Current 2026-07-05 09:27
