[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AE9G5Y7VCW92N7DW98SXH8":3,"skill-same:01M7AE9G5Y7VCW92N7DW98SXH8":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},"01M7AE9G5Y7VCW92N7DW98SXH8","competition-firmware-layout",null,"Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init chains, recover update keys or credentials, trace config loading, or explain how a device surface reaches the decisive artifact. 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-firmware-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: competition-firmware-layout\ndescription: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init chains, recover update keys or credentials, trace config loading, or explain how a device surface reaches the decisive artifact. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.\n---\n\n# Competition Firmware Layout\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 understanding how a firmware image is structured, booted, updated, and turned into reachable device behavior.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Preserve the original image, extracted partitions, unpacked filesystems, and patched copies as separate artifacts.\n2. Map outer container, partition table, bootloader, kernel, rootfs, config, and update metadata before editing anything.\n3. Track the boot or update chain in order instead of jumping straight to the most interesting file.\n4. Record keys, signatures, offsets, partition boundaries, and init entrypoints in one compact evidence chain.\n5. Reproduce the decisive secret, branch, or reachable service from the smallest extracted path.\n\n## Workflow\n\n### 1. Establish Image Layout\n\n- Identify container type, partition headers, compression, filesystem type, and any appended or nested images.\n- Record offsets, sizes, hashes, mount points, and partition names before extraction mutates anything.\n- Separate bootloader, kernel, initramfs, rootfs, config blobs, and update metadata as different layers.\n\n### 2. Trace Boot Or Update Flow\n\n- Map how control moves from bootloader to kernel to init to services, or from update package to verifier to installer.\n- Note which credentials, certificates, passwords, seeds, or config files are consumed at each stage.\n- Distinguish checked-in firmware intent from the live behavior the extracted files actually support.\n\n### 3. Reduce To The Decisive Path\n\n- Show the smallest chain from image boundary to service exposure, auth bypass, debug interface, credential recovery, or flag artifact.\n- Keep extracted filesystems, derived configs, and patch experiments separate from pristine inputs.\n- If the challenge becomes mostly about native crash behavior or exploit primitives after extraction, switch back to the broader reverse skill.\n\n## Read This Reference\n\n- Load `references\u002Ffirmware-layout.md` for the layout checklist, boot-chain checklist, and evidence packaging.\n\n## What To Preserve\n\n- Partition offsets, hashes, filesystem types, mount paths, boot entrypoints, and update metadata\n- Extracted secrets, config paths, init scripts, service units, and credentials tied to the stage that consumes them\n- Original images, extracted layers, mounted views, and patched copies as separate artifacts\n","# Competition Firmware Layout\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 understanding how a firmware image is structured, booted, updated, and turned into reachable device behavior.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Preserve the original image, extracted partitions, unpacked filesystems, and patched copies as separate artifacts.\n2. Map outer container, partition table, bootloader, kernel, rootfs, config, and update metadata before editing anything.\n3. Track the boot or update chain in order instead of jumping straight to the most interesting file.\n4. Record keys, signatures, offsets, partition boundaries, and init entrypoints in one compact evidence chain.\n5. Reproduce the decisive secret, branch, or reachable service from the smallest extracted path.\n\n## Workflow\n\n### 1. Establish Image Layout\n\n- Identify container type, partition headers, compression, filesystem type, and any appended or nested images.\n- Record offsets, sizes, hashes, mount points, and partition names before extraction mutates anything.\n- Separate bootloader, kernel, initramfs, rootfs, config blobs, and update metadata as different layers.\n\n### 2. Trace Boot Or Update Flow\n\n- Map how control moves from bootloader to kernel to init to services, or from update package to verifier to installer.\n- Note which credentials, certificates, passwords, seeds, or config files are consumed at each stage.\n- Distinguish checked-in firmware intent from the live behavior the extracted files actually support.\n\n### 3. Reduce To The Decisive Path\n\n- Show the smallest chain from image boundary to service exposure, auth bypass, debug interface, credential recovery, or flag artifact.\n- Keep extracted filesystems, derived configs, and patch experiments separate from pristine inputs.\n- If the challenge becomes mostly about native crash behavior or exploit primitives after extraction, switch back to the broader reverse skill.\n\n## Read This Reference\n\n- Load `references\u002Ffirmware-layout.md` for the layout checklist, boot-chain checklist, and evidence packaging.\n\n## What To Preserve\n\n- Partition offsets, hashes, filesystem types, mount paths, boot entrypoints, and update metadata\n- Extracted secrets, config paths, init scripts, service units, and credentials tied to the stage that consumes them\n- Original images, extracted layers, mounted views, and patched copies as separate artifacts\n",{"name":5,"description":7},"main","5b045f5effb9db25a3199f06d549a00373078082",".agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-firmware-layout","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-firmware-layout",{"tool":36,"command":37},"bunx","bunx skills add Rain-kl\u002FReverseTemplate --skill competition-firmware-layout",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Rain-kl\u002FReverseTemplate --skill competition-firmware-layout","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-firmware-layout\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",402,"https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-firmware-layout\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Ffirmware-layout.md",1089,"https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-firmware-layout\u002Freferences\u002Ffirmware-layout.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",[],[]]