[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EXDGSK47RYR3B12BKWFE41":3,"skill-same:01M7EXDGSK47RYR3B12BKWFE41":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},"01M7EXDGSK47RYR3B12BKWFE41","competition-template-render-path",null,"Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for SSR, template rendering, route loaders, hydration payloads, server-client render boundaries, and template-to-handler enforcement gaps. Use when the user asks to inspect SSR or template routes, trace render context or hydration data, compare template gating with handler enforcement, explain preview or hidden-route rendering, or connect render pipeline behavior to the decisive branch. 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-template-render-path\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: competition-template-render-path\ndescription: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for SSR, template rendering, route loaders, hydration payloads, server-client render boundaries, and template-to-handler enforcement gaps. Use when the user asks to inspect SSR or template routes, trace render context or hydration data, compare template gating with handler enforcement, explain preview or hidden-route rendering, or connect render pipeline behavior to the decisive branch. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.\n---\n\n# Competition Template Render Path\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 decisive bug or artifact lives in route resolution, server render context, template data, or hydration handoff rather than in a plain JSON API alone.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Map the render chain in order: route resolution, loader or data fetch, template or component context, response HTML, hydration payload, and client takeover.\n2. Record host, route params, preview toggles, tenant or host switches, and server-only variables before mutating anything.\n3. Compare template gating with loader or handler enforcement.\n4. Preserve one successful render and one failing render path with the smallest delta.\n5. Reproduce the smallest request-to-render branch that proves the decisive behavior.\n\n## Workflow\n\n### 1. Map Route To Render Context\n\n- Record host, path, route match, loader, template, layout, hydration blob, and client boot chunk for the active view.\n- Note whether the response is SSR HTML, static HTML plus hydration, edge-rendered content, or a template fragment used by another route.\n- Keep server-only context and client-visible context separate.\n\n### 2. Trace Template And Enforcement Boundaries\n\n- Show where permissions, feature flags, preview state, tenant selection, or host-based switches are applied.\n- Compare template-level gating, loader-level gating, and backend handler enforcement instead of trusting any one layer.\n- Record hidden fields, inline data, hydration JSON, meta tags, or alternate partials that expose the decisive branch.\n\n### 3. Reduce To The Decisive Render Path\n\n- Compress the result to the smallest sequence: request -> route match -> loader or template context -> rendered output or hidden data -> resulting effect.\n- State clearly whether the decisive weakness lives in route selection, template context construction, server-client hydration handoff, or mismatched enforcement between render and handler.\n- If the task becomes mostly emitted bundle recovery or source map reconstruction, hand off to the tighter bundle skill.\n\n## Read This Reference\n\n- Load `references\u002Ftemplate-render-path.md` for the render checklist, hydration checklist, and evidence packaging.\n\n## What To Preserve\n\n- Route names, loader names, templates, layouts, hydration keys, and host or preview switches\n- One success or failure pair that shows where render-layer behavior diverges\n- One minimal request-to-render sequence that reaches the decisive branch\n","# Competition Template Render Path\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 decisive bug or artifact lives in route resolution, server render context, template data, or hydration handoff rather than in a plain JSON API alone.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Map the render chain in order: route resolution, loader or data fetch, template or component context, response HTML, hydration payload, and client takeover.\n2. Record host, route params, preview toggles, tenant or host switches, and server-only variables before mutating anything.\n3. Compare template gating with loader or handler enforcement.\n4. Preserve one successful render and one failing render path with the smallest delta.\n5. Reproduce the smallest request-to-render branch that proves the decisive behavior.\n\n## Workflow\n\n### 1. Map Route To Render Context\n\n- Record host, path, route match, loader, template, layout, hydration blob, and client boot chunk for the active view.\n- Note whether the response is SSR HTML, static HTML plus hydration, edge-rendered content, or a template fragment used by another route.\n- Keep server-only context and client-visible context separate.\n\n### 2. Trace Template And Enforcement Boundaries\n\n- Show where permissions, feature flags, preview state, tenant selection, or host-based switches are applied.\n- Compare template-level gating, loader-level gating, and backend handler enforcement instead of trusting any one layer.\n- Record hidden fields, inline data, hydration JSON, meta tags, or alternate partials that expose the decisive branch.\n\n### 3. Reduce To The Decisive Render Path\n\n- Compress the result to the smallest sequence: request -> route match -> loader or template context -> rendered output or hidden data -> resulting effect.\n- State clearly whether the decisive weakness lives in route selection, template context construction, server-client hydration handoff, or mismatched enforcement between render and handler.\n- If the task becomes mostly emitted bundle recovery or source map reconstruction, hand off to the tighter bundle skill.\n\n## Read This Reference\n\n- Load `references\u002Ftemplate-render-path.md` for the render checklist, hydration checklist, and evidence packaging.\n\n## What To Preserve\n\n- Route names, loader names, templates, layouts, hydration keys, and host or preview switches\n- One success or failure pair that shows where render-layer behavior diverges\n- One minimal request-to-render sequence that reaches the decisive branch\n",{"name":5,"description":7},"main","667b2db2746516eae05412bbdcad77515d528f37","packed-packs\u002Fcodex\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-template-render-path",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-template-render-path",{"tool":36,"command":37},"bunx","bunx skills add longwangjiang88\u002FSusuAIOverclock-pojia --skill competition-template-render-path",{"tool":39,"command":40},"pnpm","pnpm dlx skills add longwangjiang88\u002FSusuAIOverclock-pojia --skill competition-template-render-path","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fcodex\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-template-render-path\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",415,"https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fcodex\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-template-render-path\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Ftemplate-render-path.md",1099,"https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fcodex\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-template-render-path\u002Freferences\u002Ftemplate-render-path.md",[55,63,70,77,83,89],{"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":62},"01M7EYSVDK2NDWT3E55EQN2KJY","yingan-tuoxiu","Owner-authorized YingAn\u002FYingPo Android APK shell rehydration and stable rebuild workflow. Use for APKs with tiny or abnormal root DEX files, v.m.p or abcd655xx shell callbacks, libabcd\u002Flib*shellservice_dex native loaders, protected assets, runtime-loaded DEX images, hidden real Application or Activity routes, and native lifecycle wrappers that must be recovered into a normally installable, signed multidex APK without changing product authentication or business authorization behavior.","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fworkbuddy\u002Fmaterials\u002Fskills\u002F西宫影安老版本脱修\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":62},"01M7EYSNPJM4G98TAYPQ0DRHDA","reverse-engineering","Use when performing reverse engineering on any target: websites, desktop binaries (PE\u002FELF),\nmobile apps (APK\u002FIPA), or network protocols. Covers web scraping\u002FAPI reverse, disassembly\nand decompilation, Frida\u002FXposed hooking, il2cpp\u002FUnity reverse, protocol capture and replay,\nencryption\u002Fsignature analysis, and memory debugging.\nTriggers: 逆向、反编译、Hook、脱壳、抓包、协议分析、Frida、Xposed、il2cpp、Unity逆向、\n内存扫描、DLL注入、PE分析、ELF分析、APK逆向、IPA逆向、反混淆、签名分析、加密还原、\nsmali、Ghidra、IDA、Cheat Engine、mitmproxy、Wireshark、脱壳、加固、SO逆向、Web逆向。","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fworkbuddy\u002Fmaterials\u002Fskills\u002F外挂逆向skills\u002Freverse-engineering\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":62},"01M7EYSFJ2GD8JMZ2BEN5EZ1P2","game-hacking","游戏辅助开发全链路助手——覆盖内存读写、协议分析、反编译、Hook 技术、驱动级隐藏、自动化脚本。\n支持 C\u002FC++、Python、x86\u002Fx64 汇编、DirectX\u002FOpenGL。适用于 PC 端游、Android\u002FiOS 手游、主机游戏。\n当用户提到以下任何关键词时必须触发：游戏外挂、游戏辅助、内存修改、CE教程、游戏Hook、\n协议分析、反编译、驱动隐藏、游戏脚本、按键精灵、游戏逆向、内存扫描、指针追踪、DLL注入、\n游戏破解、脱壳、抓包分析、Frida、Xposed、il2cpp、Unity逆向、UE4逆向、DirectX Hook、\nOpenGL Hook、游戏自动化、坐标识别、模板匹配、游戏安全测试。","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fworkbuddy\u002Fmaterials\u002Fskills\u002F外挂逆向skills\u002Fgame-hacking\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":6,"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":62},"01M7EYSDN4YRG47G64RZWN9VQP","supply-chain-security","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fworkbuddy\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002Fskills\u002Fsupply-chain-security\u002FSKILL.md",[],[],{"skillNo":84,"name":65,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":62},"01M7EYS778SXQN48QQHGSD72HD","Provides reverse engineering techniques. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it when the vulnerability is already understood and the remaining task is exploitation; use pwn instead. Do not use it for pure web workflows, log or disk forensics, or standalone crypto problems unless reversing the implementation is the real blocker.","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fworkbuddy\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002Fskills\u002Freverse-engineering\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":62},"01M7EYS223506HTEF0RD9952QP","radare2","Use this skill whenever the user wants to analyze binaries with radare2\u002Fr2 from the command line, including reverse engineering, disassembly, function analysis, strings\u002Fimport inspection, patching, binary diffing, hex inspection, or r2 scripting. Also use it when the user mentions PE\u002FELF\u002FMach-O\u002FDEX\u002FWASM files together with CLI analysis, `rabin2`, `rasm2`, `radiff2`, `r2pipe`, or asks for radare2 command help on Windows\u002FLinux\u002FmacOS.","https:\u002F\u002Fgithub.com\u002Flongwangjiang88\u002FSusuAIOverclock-pojia\u002Fblob\u002Fmain\u002Fpacked-packs\u002Fworkbuddy\u002Fmaterials\u002Fskills\u002Fzzy-codex5.6\u002Fzzy-reverse-skill\u002Fskills\u002Fradare2\u002FSKILL.md",[],[]]