[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EXCSTT6XDXNFZ0JPV3STAX":3,"skill-same:01M7EXCSTT6XDXNFZ0JPV3STAX":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},"01M7EXCSTT6XDXNFZ0JPV3STAX","competition-reverse-pwn",null,"Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for reverse engineering, malware, DFIR, firmware, pwnable, and native exploit challenges. Use when the user asks to reverse a binary, unpack a sample, inspect a memory dump or PCAP, recover malware behavior, debug a crash, or build or verify an exploit chain under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.","longwangjiang88\u002FSusuAIOverclock-pojia","longwangjiang88","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F86055358?v=4","01M7EWPCXB6TZRPCAD8J1GQGRV","01M7EWPCXXRSYV10DVK1ZH6YMC",42,"MIT","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fcodex\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-reverse-pwn\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: competition-reverse-pwn\ndescription: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for reverse engineering, malware, DFIR, firmware, pwnable, and native exploit challenges. Use when the user asks to reverse a binary, unpack a sample, inspect a memory dump or PCAP, recover malware behavior, debug a crash, or build or verify an exploit chain under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.\n---\n\n# Competition Reverse Pwn\n\nUse this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.\n\nUse this skill for binary-heavy challenges where the decisive path runs through artifacts, decoded layers, process behavior, crash state, or exploit primitives.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Preserve the original artifact before unpacking, patching, or instrumenting.\n2. Start with passive triage: type, headers, sections, imports, strings, entropy, resources.\n3. Decide whether the path is reverse-first, DFIR-first, or exploit-first.\n4. Tie every claim to an observable boundary: decode edge, persistence edge, crash edge, or leak edge.\n5. Reproduce the artifact or primitive from a clean baseline.\n\n## Workflow\n\n### 1. Reverse Or Forensic Triage\n\n- Separate loader, payload, config, and post-decode behavior.\n- Correlate files, memory, logs, registry, services, tasks, IPC, and PCAPs as one graph.\n- Keep decoded or dumped artifacts separate from the pristine sample.\n\n### 2. Native And Exploit Path\n\n- Map mitigations, loader behavior, libc or runtime, syscall and IPC surfaces, and protocol framing.\n- Record the primitive, controllable bytes, leak source, target object, and final artifact separately.\n- Compare host, libc, loader, and framing differences before doubting the primitive.\n\n## Read This Reference\n\n- Load `references\u002Freverse-pwn.md` for triage order, exploit evidence expectations, and common failure modes.\n- If the task is specifically about staged payload boundaries, config blobs, beacon parameters, or decoded IOC fields, prefer `$competition-malware-config`.\n- If the task is specifically about firmware partitions, boot chains, extracted filesystems, or update-package trust boundaries, prefer `$competition-firmware-layout`.\n- If the task is specifically about upload parsing, previews, archive extraction, converters, or deserialization chains, prefer `$competition-file-parser-chain`.\n- If the task is specifically about source maps, emitted bundles, chunk registries, or reconstructing hidden runtime structure from served frontend assets, prefer `$competition-bundle-sourcemap-recovery`.\n- If the task is specifically about container-to-host boundary crossing, kernel exploit preconditions, namespace or cgroup crossover, or escape primitive verification, prefer `$competition-kernel-container-escape`.\n- If the task is specifically about reconstructing protocols, streams, or transferred artifacts from packet captures, prefer `$competition-pcap-protocol`.\n- If the task is specifically about a custom binary or text protocol where replay state, message order, or checksum logic is the real blocker, prefer `$competition-custom-protocol-replay`.\n- If the task is specifically about reconstructing chronology across EVTX, PCAP, registry, mail, or disk artifacts, prefer `$competition-forensic-timeline`.\n\n## What To Preserve\n\n- Offsets, hashes, section names, imports, config blobs, mutexes, registry keys\n- Crash offsets, registers, heap or stack shape, leak addresses, and protocol steps\n- Original, decoded, dumped, and instrumented artifacts as separate files\n","# Competition Reverse Pwn\n\nUse this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.\n\nUse this skill for binary-heavy challenges where the decisive path runs through artifacts, decoded layers, process behavior, crash state, or exploit primitives.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Preserve the original artifact before unpacking, patching, or instrumenting.\n2. Start with passive triage: type, headers, sections, imports, strings, entropy, resources.\n3. Decide whether the path is reverse-first, DFIR-first, or exploit-first.\n4. Tie every claim to an observable boundary: decode edge, persistence edge, crash edge, or leak edge.\n5. Reproduce the artifact or primitive from a clean baseline.\n\n## Workflow\n\n### 1. Reverse Or Forensic Triage\n\n- Separate loader, payload, config, and post-decode behavior.\n- Correlate files, memory, logs, registry, services, tasks, IPC, and PCAPs as one graph.\n- Keep decoded or dumped artifacts separate from the pristine sample.\n\n### 2. Native And Exploit Path\n\n- Map mitigations, loader behavior, libc or runtime, syscall and IPC surfaces, and protocol framing.\n- Record the primitive, controllable bytes, leak source, target object, and final artifact separately.\n- Compare host, libc, loader, and framing differences before doubting the primitive.\n\n## Read This Reference\n\n- Load `references\u002Freverse-pwn.md` for triage order, exploit evidence expectations, and common failure modes.\n- If the task is specifically about staged payload boundaries, config blobs, beacon parameters, or decoded IOC fields, prefer `$competition-malware-config`.\n- If the task is specifically about firmware partitions, boot chains, extracted filesystems, or update-package trust boundaries, prefer `$competition-firmware-layout`.\n- If the task is specifically about upload parsing, previews, archive extraction, converters, or deserialization chains, prefer `$competition-file-parser-chain`.\n- If the task is specifically about source maps, emitted bundles, chunk registries, or reconstructing hidden runtime structure from served frontend assets, prefer `$competition-bundle-sourcemap-recovery`.\n- If the task is specifically about container-to-host boundary crossing, kernel exploit preconditions, namespace or cgroup crossover, or escape primitive verification, prefer `$competition-kernel-container-escape`.\n- If the task is specifically about reconstructing protocols, streams, or transferred artifacts from packet captures, prefer `$competition-pcap-protocol`.\n- If the task is specifically about a custom binary or text protocol where replay state, message order, or checksum logic is the real blocker, prefer `$competition-custom-protocol-replay`.\n- If the task is specifically about reconstructing chronology across EVTX, PCAP, registry, mail, or disk artifacts, prefer `$competition-forensic-timeline`.\n\n## What To Preserve\n\n- Offsets, hashes, section names, imports, config blobs, mutexes, registry keys\n- Crash offsets, registers, heap or stack shape, leak addresses, and protocol steps\n- Original, decoded, dumped, and instrumented artifacts as separate files\n",{"name":5,"description":7},"main","667b2db2746516eae05412bbdcad77515d528f37","packed-packs\u002Fcodex\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-reverse-pwn",24,"https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia","https:\u002F\u002Fgithub.com\u002Flongwangjiang88","2026-10-15 18:06:23",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add longwangjiang88\u002FSusuAIOverclock-pojia --skill competition-reverse-pwn",{"tool":36,"command":37},"bunx","bunx skills add longwangjiang88\u002FSusuAIOverclock-pojia --skill competition-reverse-pwn",{"tool":39,"command":40},"pnpm","pnpm dlx skills add longwangjiang88\u002FSusuAIOverclock-pojia --skill competition-reverse-pwn","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fcodex\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-reverse-pwn\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",370,"https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fcodex\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-reverse-pwn\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Freverse-pwn.md",1010,"https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fcodex\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-reverse-pwn\u002Freferences\u002Freverse-pwn.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},"01M7EXRKPJ2292PAZT1RCNSCN5","competition-race-condition-state-drift","Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for race windows, ordering bugs, idempotency failures, lock gaps, concurrent worker drift, and state inconsistencies that produce decisive effects. Use when the user asks to reproduce timing-sensitive bugs, concurrent state corruption, duplicate actions, stale reads, or privilege or balance drift caused by request ordering. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fdsh\u002Fmaterials\u002Fskills\u002Fcompetition-race-condition-state-drift\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},"01M7EXREQMMPBNJ1HY11PNKNRG","competition-queue-worker-drift","Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for queues, async workers, cron jobs, delayed tasks, retry behavior, worker-only config drift, and payload-to-side-effect chains. Use when the user asks to trace a queue payload, inspect async job execution, explain worker-only behavior, follow retries or dead-letter handling, or connect an enqueued item to a later file, cache, email, or privilege-bearing side effect. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fdsh\u002Fmaterials\u002Fskills\u002Fcompetition-queue-worker-drift\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},"01M7EXRAD56074F23Q9G8XAQWR","competition-prompt-injection","Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for prompt-injection, retrieval poisoning, memory contamination, planner drift, MCP or tool-boundary abuse, and agent exfiltration challenges. Use when the user asks to analyze prompt injection, retrieval poisoning, memory contamination, planner drift, tool-argument corruption, or secret exposure caused by an agent chain. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fdsh\u002Fmaterials\u002Fskills\u002Fcompetition-prompt-injection\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},"01M7EXR5NNFRY7ZSG6M7D214X3","competition-pcap-protocol","Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for packet capture analysis, session reconstruction, application-protocol decoding, stream reassembly, beacon timing, and packet-to-process correlation. Use when the user asks to analyze a PCAP, rebuild TCP or UDP sessions, decode HTTP, WebSocket, DNS, custom C2, or binary protocols, extract transferred artifacts, or tie packet sequences to host or malware behavior. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fdsh\u002Fmaterials\u002Fskills\u002Fcompetition-pcap-protocol\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},"01M7EXR0VY8FRXXFSBDC1YN0XD","competition-oauth-oidc-chain","Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for OAuth, OIDC, redirect flows, state or nonce handling, PKCE, token exchange, refresh logic, claim mapping, and accepted login paths. Use when the user asks to trace redirects, callback parameters, scopes, state, nonce, PKCE, refresh tokens, consent, or explain how an OAuth or OIDC chain turns into accepted identity or privilege. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fdsh\u002Fmaterials\u002Fskills\u002Fcompetition-oauth-oidc-chain\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},"01M7EXQW6A6B4VE38F0YTC069G","competition-malware-config","Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for malware configuration recovery, staged payload boundaries, beacon parameter extraction, and IOC decoding. Use when the user asks to recover a malware config, decode C2 or beacon fields, unpack staged payloads, extract bot or campaign IDs, or tie recovered config to observed protocol behavior under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fdsh\u002Fmaterials\u002Fskills\u002Fcompetition-malware-config\u002FSKILL.md",[],[]]