[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DA07JBGGGG88RMZDVRM05B":3,"skill-same:01M7DA07JBGGGG88RMZDVRM05B":57},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7DA07JBGGGG88RMZDVRM05B","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.","alicewe1\u002Falice_skill","alicewe1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102134151?v=4","01M7D9STCM8HAESM958JP0989K","Alice_we","01M7D9STDR22MTD9FTTWPAZNV8",64,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\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.\nx-alice-class: reverse\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,"x-alice-class":24},"reverse","main","19a54ac988e9929160334271f5c1924ddd9b227e","_modules\u002Fcompetition-firmware-layout",19,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill","https:\u002F\u002Fgithub.com\u002Falicewe1","写一些自己用得上的工具，能自动化就绝不手动 · 自动化 \u002F 工程效率 \u002F Agent 技能生态 · 保持好奇，持续构建","2026-09-30 00:41:20",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add alicewe1\u002Falice_skill --skill competition-firmware-layout",{"tool":39,"command":40},"bunx","bunx skills add alicewe1\u002Falice_skill --skill competition-firmware-layout",{"tool":42,"command":43},"pnpm","pnpm dlx skills add alicewe1\u002Falice_skill --skill competition-firmware-layout","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fcompetition-firmware-layout\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",402,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fcompetition-firmware-layout\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Ffirmware-layout.md",1089,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fcompetition-firmware-layout\u002Freferences\u002Ffirmware-layout.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DBMD9P6R27SWQCW5HYVWG0","alice","Alice 六类技能总路由。用户输入 Alice 或要求查看 Alice 技能菜单时，严格输出固定菜单；输入攻\u002F防模式、六类入口或直接描述任务时，按类别→领域→模块渐进路由。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Faliceskill\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7DBM8X5M7YXPYBVFMWF8HRC","alice-reverse","逆向分析渐进路由（二进制 \u002F 移动端 \u002F 协议 \u002F 取证 \u002F 保护机制 \u002F 运行时观测）。触发词：二进制\u002F移动端\u002F反编译\u002FFrida\u002FIDA\u002FGhidra\u002FPE\u002FELF\u002FAPK\u002F协议\u002F取证；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-reverse\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DBM630E2YKQP29194TT7HC","alice-pentest","web安全渐进路由（Web \u002F API \u002F 资产发现 \u002F 漏洞验证 \u002F 云与网络安全）。触发词：Web\u002FAPI\u002F资产发现\u002F端口\u002F漏洞验证\u002F云与网络安全；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-pentest\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7DBM20M2VDYV5D3MYDGBTQX","alice-game","游戏攻防渐进路由（游戏客户端 \u002F 内存 \u002F 图形 \u002F 反作弊 \u002F 安全研究）。触发词：游戏客户端\u002F内存\u002F图形\u002F偏移\u002F反作弊\u002F模拟器\u002F覆盖层；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-game\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7DBKXVEKB8931MZG23VACFN","alice-crack","卡密授权渐进路由（卡密 \u002F 激活 \u002F 授权验证 \u002F 许可证管理 \u002F 本地授权分析）。触发词：卡密\u002F激活\u002F授权验证\u002Flicense\u002F机器码\u002F试用状态；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-crack\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7DBKTMT90MGV2WP8K73TMQD","alice-assist","技能指令渐进路由（技能路由 \u002F 评分 \u002F 吸收 \u002F 迁移 \u002F 自动化 \u002F 文档与平台集成）。触发词：技能创建\u002F吸收\u002F评分\u002F迁移\u002F自动化\u002F文档\u002F平台指令；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-assist\u002FSKILL.md",[],[]]