[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AE9AT76PNV2ES0GCBBQY04":3,"skill-same:01M7AE9AT76PNV2ES0GCBBQY04":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7AE9AT76PNV2ES0GCBBQY04","competition-file-parser-chain",null,"Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for file uploads, imports, previews, archive extraction, format conversion, parser invocation, and deserialization chains. Use when the user asks to inspect an upload or import path, trace archive extraction, preview or converter behavior, explain how a file reaches a parser or deserializer, or connect one uploaded artifact to the decisive backend effect. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.","Rain-kl\u002FReverseTemplate","Rain-kl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63696351?v=4","01M7AE7E8ECRECCF300YM1A8BS","Ryan","01M7AE7E9Q3AYTB7W3NNSV3200",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-file-parser-chain\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: competition-file-parser-chain\ndescription: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for file uploads, imports, previews, archive extraction, format conversion, parser invocation, and deserialization chains. Use when the user asks to inspect an upload or import path, trace archive extraction, preview or converter behavior, explain how a file reaches a parser or deserializer, or connect one uploaded artifact to the decisive backend effect. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.\n---\n\n# Competition File Parser Chain\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 when the hard part is following a file from ingress through every parser, extractor, converter, or deserializer boundary that matters.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Preserve the original upload and every derived artifact separately.\n2. Map the chain in order: ingress, temp storage, archive extraction, format conversion, parser call, deserialization, and final consumer.\n3. Record filenames, MIME guesses, extensions, temp paths, and parser choices before mutating anything.\n4. Separate client-visible validation from backend parser behavior.\n5. Reproduce the smallest file-processing chain that yields the decisive branch or artifact.\n\n## Workflow\n\n### 1. Map File Ingress And Derivation\n\n- Record request shape, multipart names, content type, filename, temp paths, upload staging, and storage keys.\n- Note every derived artifact: extracted archive member, converted preview, generated thumbnail, temp document, or deserialized object.\n- Keep original file and each derivative labeled separately.\n\n### 2. Trace Parser And Conversion Boundaries\n\n- Show which parser, converter, extractor, or deserializer runs at each step.\n- Record parser-specific decisions driven by extension, MIME, magic bytes, schema, archive member names, or embedded metadata.\n- Distinguish parsing success, preview success, conversion success, and business-logic acceptance.\n\n### 3. Reduce To The Decisive File Chain\n\n- Compress the result to the smallest sequence: upload -> derived artifact -> parser boundary -> resulting effect.\n- State clearly whether the decisive weakness lives in archive handling, MIME inference, file conversion, path resolution, or deserialization.\n- If the chain becomes mostly a generic async worker problem after enqueue, hand off to the tighter queue or worker skill.\n\n## Read This Reference\n\n- Load `references\u002Ffile-parser-chain.md` for the ingress checklist, parser checklist, and evidence packaging.\n\n## What To Preserve\n\n- Original uploads, derived files, temp paths, storage keys, parser names, and conversion steps\n- The exact boundary where backend behavior diverges from user-visible validation\n- One minimal replayable file-processing sequence that reaches the decisive effect\n","# Competition File Parser Chain\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 when the hard part is following a file from ingress through every parser, extractor, converter, or deserializer boundary that matters.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Preserve the original upload and every derived artifact separately.\n2. Map the chain in order: ingress, temp storage, archive extraction, format conversion, parser call, deserialization, and final consumer.\n3. Record filenames, MIME guesses, extensions, temp paths, and parser choices before mutating anything.\n4. Separate client-visible validation from backend parser behavior.\n5. Reproduce the smallest file-processing chain that yields the decisive branch or artifact.\n\n## Workflow\n\n### 1. Map File Ingress And Derivation\n\n- Record request shape, multipart names, content type, filename, temp paths, upload staging, and storage keys.\n- Note every derived artifact: extracted archive member, converted preview, generated thumbnail, temp document, or deserialized object.\n- Keep original file and each derivative labeled separately.\n\n### 2. Trace Parser And Conversion Boundaries\n\n- Show which parser, converter, extractor, or deserializer runs at each step.\n- Record parser-specific decisions driven by extension, MIME, magic bytes, schema, archive member names, or embedded metadata.\n- Distinguish parsing success, preview success, conversion success, and business-logic acceptance.\n\n### 3. Reduce To The Decisive File Chain\n\n- Compress the result to the smallest sequence: upload -> derived artifact -> parser boundary -> resulting effect.\n- State clearly whether the decisive weakness lives in archive handling, MIME inference, file conversion, path resolution, or deserialization.\n- If the chain becomes mostly a generic async worker problem after enqueue, hand off to the tighter queue or worker skill.\n\n## Read This Reference\n\n- Load `references\u002Ffile-parser-chain.md` for the ingress checklist, parser checklist, and evidence packaging.\n\n## What To Preserve\n\n- Original uploads, derived files, temp paths, storage keys, parser names, and conversion steps\n- The exact boundary where backend behavior diverges from user-visible validation\n- One minimal replayable file-processing sequence that reaches the decisive effect\n",{"name":5,"description":7},"main","5b045f5effb9db25a3199f06d549a00373078082",".agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-file-parser-chain","https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate","https:\u002F\u002Fgithub.com\u002FRain-kl","2026-09-19 20:30:24",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Rain-kl\u002FReverseTemplate --skill competition-file-parser-chain",{"tool":36,"command":37},"bunx","bunx skills add Rain-kl\u002FReverseTemplate --skill competition-file-parser-chain",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Rain-kl\u002FReverseTemplate --skill competition-file-parser-chain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-file-parser-chain\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",410,"https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-file-parser-chain\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Ffile-parser-chain.md",1074,"https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-file-parser-chain\u002Freferences\u002Ffile-parser-chain.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":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7AEMCR7PHAB7SRFX17KAKKS","windows-ad","Use for authorized Active Directory and Windows identity attacks including Kerberos, AD CS, BloodHound paths, NTLM relay, and domain privilege escalation research.","https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002Fskills\u002Fwindows-ad\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7AEMA913F9CGJPHXGRA4DMW","wifi-wireless","Use for authorized wireless security assessment including Wi-Fi capture, WPA handshake analysis, rogue AP detection research, and lab-only deauth testing.","https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002Fskills\u002Fwifi-wireless\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7AEM7SKHX0JD2HKD4EP7FCH","threat-hunting","Use for blue-team threat hunting, detection engineering with Sigma\u002FYARA, SIEM query design, and incident detection validation.","https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002Fskills\u002Fthreat-hunting\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7AEM4S61F6E0F20A2HB50QM","thick-client","Use for authorized security testing of desktop thick clients including local storage, update channels, IPC, traffic, and client-side trust boundaries.","https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002Fskills\u002Fthick-client\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7AEM1KQQHZBD9RDQ2P3GKWH","supply-chain-security","Use for software supply-chain security assessment covering SBOM, SCA, CI\u002FCD pipelines, container images, build integrity, dependency provenance, and vulnerability reachability.","https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002Fskills\u002Fsupply-chain-security\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7AEKXA2PNZA2NYRW63RFNZS","dsl-vm-reverse","Reverse JavaScript-based custom DSL\u002FVM interpreters, non-standard WASM-like runtimes, and risk-control engines. Use when analyzing IIFE or switch-based opcode dispatchers, extracting instruction tables, recovering bytecode semantics, capturing VM state at runtime, or reconstructing execution flow.","https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002Fskills\u002Freverse-engineering\u002Fdsl-vm-reverse\u002FSKILL.md",[],[]]