[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75FQ8CX4VFDF08H886WHFNM":3,"skill-same:01M75FQ8CX4VFDF08H886WHFNM":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M75FQ8CX4VFDF08H886WHFNM","anti-reversing-techniques",null,"Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use this skill when analyzing malware evasion techniques, when implementing anti-debugging protections for CTF challenges, when reverse engineering packed binaries, or when building security research tools that need to detect virtualized environments.","RudyCity\u002Fsuperagent","RudyCity","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82188919?v=4","01M75FP5X8AW8ACBH0SH34WS7M","01M75FP5YAHJK8M1Q52BWXB82K",70,"MIT","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanti-reversing-techniques\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: anti-reversing-techniques\ndescription: Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use this skill when analyzing malware evasion techniques, when implementing anti-debugging protections for CTF challenges, when reverse engineering packed binaries, or when building security research tools that need to detect virtualized environments.\n---\n\n> **AUTHORIZED USE ONLY**: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis:\n>\n> 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)\n> 2. **Document scope**: Ensure your activities fall within the defined scope of your authorization\n> 3. **Legal compliance**: Understand that unauthorized bypassing of software protection may violate laws (CFAA, DMCA anti-circumvention, etc.)\n>\n> **Legitimate use cases**: Malware analysis, authorized penetration testing, CTF competitions, academic security research, analyzing software you own\u002Fhave rights to\n\n# Anti-Reversing Techniques\n\nUnderstanding protection mechanisms encountered during authorized software analysis, security research, and malware analysis. This knowledge helps analysts bypass protections to complete legitimate analysis tasks.\n\nFor advanced techniques, see [references\u002Fadvanced-techniques.md](references\u002Fadvanced-techniques.md)\n\n---\n\n## Input \u002F Output\n\n**What you provide:**\n\n- **Binary path or sample**: the executable, DLL, or firmware image under analysis\n- **Platform**: Windows x86\u002Fx64, Linux, macOS, ARM — affects which checks apply\n- **Goal**: bypass for dynamic analysis, identify protection type, build detection code, implement for CTF\n\n**What this skill produces:**\n\n- **Protection identification**: named technique (e.g., RDTSC timing check, PEB BeingDebugged) with location in binary\n- **Bypass strategy**: specific patch addresses, hook points, or tool commands to neutralize each check\n- **Analysis report**: structured findings listing each protection layer, severity, and recommended bypass\n- **Code artifacts**: Python\u002FIDAPython scripts, GDB command sequences, or C stubs for bypassing or implementing checks\n\n---\n\n## Detailed patterns and worked examples\n\nDetailed pattern documentation lives in `references\u002Fdetails.md`. Read that file when the navigation tier above is insufficient.\n\n## Troubleshooting\n\n**Detection technique works on x86 but not ARM**\n\nRDTSC and CPUID are x86-only. On ARM, use `MRS x0, PMCCNTR_EL0` (requires kernel PMU access) or `clock_gettime(CLOCK_MONOTONIC)`. PEB\u002FTEB do not exist on ARM — replace with `\u002Fproc\u002Fself\u002Fstatus` (Linux) or `task_info` (macOS). Rebuild detection logic with platform-specific APIs.\n\n**False positive on legitimate debugger or analysis tool**\n\nTiming checks fire when Process Monitor or AV hooks inflate syscall latency. Calibrate the threshold at startup: measure the guarded path 3 times and use `mean + 3*stddev`. For ptrace checks, verify the TracerPid comm name via `\u002Fproc\u002F\u003Cpid>\u002Fcomm` before exiting — it may be an unrelated monitoring tool, not a debugger.\n\n**Bypass patch causes crash instead of continuing execution**\n\nBefore NOPing a conditional jump, trace the \"detected\" branch fully. If it initializes or frees heap state needed later, patching the jump skips that setup and corrupts state. Instead, patch the comparison operand to the expected \"clean\" value, or use x64dbg's \"Set condition to always false\" on the breakpoint rather than modifying bytes.\n\n---\n\n## Related Skills\n\n- `binary-analysis-patterns` — static and dynamic analysis workflows for ELF\u002FPE\u002FMach-O\n- `memory-forensics` — process memory acquisition, artifact extraction, and live analysis\n- `protocol-reverse-engineering` — decoding custom binary protocols and encrypted network traffic\n","> **AUTHORIZED USE ONLY**: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis:\n>\n> 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)\n> 2. **Document scope**: Ensure your activities fall within the defined scope of your authorization\n> 3. **Legal compliance**: Understand that unauthorized bypassing of software protection may violate laws (CFAA, DMCA anti-circumvention, etc.)\n>\n> **Legitimate use cases**: Malware analysis, authorized penetration testing, CTF competitions, academic security research, analyzing software you own\u002Fhave rights to\n\n# Anti-Reversing Techniques\n\nUnderstanding protection mechanisms encountered during authorized software analysis, security research, and malware analysis. This knowledge helps analysts bypass protections to complete legitimate analysis tasks.\n\nFor advanced techniques, see [references\u002Fadvanced-techniques.md](references\u002Fadvanced-techniques.md)\n\n---\n\n## Input \u002F Output\n\n**What you provide:**\n\n- **Binary path or sample**: the executable, DLL, or firmware image under analysis\n- **Platform**: Windows x86\u002Fx64, Linux, macOS, ARM — affects which checks apply\n- **Goal**: bypass for dynamic analysis, identify protection type, build detection code, implement for CTF\n\n**What this skill produces:**\n\n- **Protection identification**: named technique (e.g., RDTSC timing check, PEB BeingDebugged) with location in binary\n- **Bypass strategy**: specific patch addresses, hook points, or tool commands to neutralize each check\n- **Analysis report**: structured findings listing each protection layer, severity, and recommended bypass\n- **Code artifacts**: Python\u002FIDAPython scripts, GDB command sequences, or C stubs for bypassing or implementing checks\n\n---\n\n## Detailed patterns and worked examples\n\nDetailed pattern documentation lives in `references\u002Fdetails.md`. Read that file when the navigation tier above is insufficient.\n\n## Troubleshooting\n\n**Detection technique works on x86 but not ARM**\n\nRDTSC and CPUID are x86-only. On ARM, use `MRS x0, PMCCNTR_EL0` (requires kernel PMU access) or `clock_gettime(CLOCK_MONOTONIC)`. PEB\u002FTEB do not exist on ARM — replace with `\u002Fproc\u002Fself\u002Fstatus` (Linux) or `task_info` (macOS). Rebuild detection logic with platform-specific APIs.\n\n**False positive on legitimate debugger or analysis tool**\n\nTiming checks fire when Process Monitor or AV hooks inflate syscall latency. Calibrate the threshold at startup: measure the guarded path 3 times and use `mean + 3*stddev`. For ptrace checks, verify the TracerPid comm name via `\u002Fproc\u002F\u003Cpid>\u002Fcomm` before exiting — it may be an unrelated monitoring tool, not a debugger.\n\n**Bypass patch causes crash instead of continuing execution**\n\nBefore NOPing a conditional jump, trace the \"detected\" branch fully. If it initializes or frees heap state needed later, patching the jump skips that setup and corrupts state. Instead, patch the comparison operand to the expected \"clean\" value, or use x64dbg's \"Set condition to always false\" on the breakpoint rather than modifying bytes.\n\n---\n\n## Related Skills\n\n- `binary-analysis-patterns` — static and dynamic analysis workflows for ELF\u002FPE\u002FMach-O\n- `memory-forensics` — process memory acquisition, artifact extraction, and live analysis\n- `protocol-reverse-engineering` — decoding custom binary protocols and encrypted network traffic\n",{"name":5,"description":7},"main","62c7af5ced2c21355d148c243edb6d5921cca1a6",".agents\u002Fskills\u002Fanti-reversing-techniques",8,"https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent","https:\u002F\u002Fgithub.com\u002FRudyCity","2026-11-14 22:58:49",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add RudyCity\u002Fsuperagent --skill anti-reversing-techniques",{"tool":36,"command":37},"bunx","bunx skills add RudyCity\u002Fsuperagent --skill anti-reversing-techniques",{"tool":39,"command":40},"pnpm","pnpm dlx skills add RudyCity\u002Fsuperagent --skill anti-reversing-techniques","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanti-reversing-techniques\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fadvanced-techniques.md","REFERENCE","参考文档",10615,"https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanti-reversing-techniques\u002Freferences\u002Fadvanced-techniques.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fdetails.md",11400,"https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanti-reversing-techniques\u002Freferences\u002Fdetails.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M75GP28CM6QCSXSHKFF3NNKS","telegram_bot","Use Telegram Bot when the user asks for Telegram Bot or this provider's API.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Ftelegram-bot\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M75GNZGZYM7NWDV6MBP3HS14","superagent-bridge","Operate the Muse\u003C->superagent Telegram bridge: poll the private group for task_request\u002Ftask_result envelopes, validate senders, and reply with task_batch\u002Ftask_done as Muse (the remote brain).","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Fsuperagent-bridge\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M75GNHN19HJWZ7NAPM5E5JCV","Writing Skills","TDD for process documentation - test with subagents before writing, iterate until bulletproof","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M75GNCQEKVRA4FH161NZPZNB","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M75GNAF9NAYCSTBDZDGMK0DZ","Writing Plans","Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M75GN72EV0V5NQAW9CSPFRFH","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[]]