[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEA6ED0BRM4T3MW3TSBWTZ":3,"skill-same:01M7AEA6ED0BRM4T3MW3TSBWTZ":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},"01M7AEA6ED0BRM4T3MW3TSBWTZ","competition-ios-runtime",null,"Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for IPA runtime analysis, Frida hooks, Objective-C or Swift method tracing, Keychain inspection, SSL pinning bypass, URL scheme handling, and iOS request-signing recovery. Use when the user asks to hook an IPA, trace Objective-C or Swift runtime behavior, inspect Keychain or plist state, bypass pinning, analyze deeplinks or universal links, or replay accepted iOS requests. 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-ios-runtime\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: competition-ios-runtime\ndescription: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for IPA runtime analysis, Frida hooks, Objective-C or Swift method tracing, Keychain inspection, SSL pinning bypass, URL scheme handling, and iOS request-signing recovery. Use when the user asks to hook an IPA, trace Objective-C or Swift runtime behavior, inspect Keychain or plist state, bypass pinning, analyze deeplinks or universal links, or replay accepted iOS requests. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.\n---\n\n# Competition iOS Runtime\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 path runs through live iOS trust boundaries rather than static strings or plist values alone.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Preserve the original IPA, extracted bundle, and any decrypted or re-signed copy as separate artifacts.\n2. Start with `Info.plist`, entitlements, URL schemes, frameworks, Keychain usage, and local app storage before broad runtime hooks.\n3. Choose the narrowest runtime boundary that proves behavior: signer, trust evaluator, Keychain accessor, Objective-C or Swift method, or network request builder.\n4. Correlate static bundle evidence and live hook output before claiming the trust path is understood.\n5. Reproduce the accepted request, token, or gated branch from the smallest hook set.\n\n## Workflow\n\n### 1. Static iOS Triage\n\n- Map bundle structure, `Info.plist`, entitlements, URL schemes, universal links, embedded frameworks, and app group paths.\n- Record likely trust boundaries: request signers, device binding, certificate checks, jailbreak checks, Keychain access, or local cache loading.\n- Note whether sensitive logic sits in Objective-C, Swift, embedded frameworks, or a bundled web surface.\n\n### 2. Hook The Runtime Boundary\n\n- Prefer hooking request builders, crypto helpers, trust evaluators, Keychain reads, or Objective-C selectors instead of broad UI handlers.\n- Record plaintext inputs, headers, nonces, signed strings, and outputs at the boundary that changes server acceptance.\n- Patch or bypass pinning or environment checks only enough to expose the real request path.\n\n### 3. Replay The Accepted Path\n\n- Rebuild the smallest stateful sequence: local token, device identifier, request body, signature, headers, and trust checks.\n- Keep hook logs, bundle paths, plist keys, and local storage artifacts tied to the same session or account state.\n- If the task becomes mostly about transform recovery instead of iOS runtime, switch back to the broader crypto or mobile skill.\n\n## Read This Reference\n\n- Load `references\u002Fios-runtime.md` for hook targets, storage checklist, and evidence packaging.\n\n## What To Preserve\n\n- Bundle paths, entitlements, plist keys, selectors, class names, hook points, and header names\n- Keychain items, local DB or plist paths, URL schemes, and app-group storage locations\n- The smallest replayable request or branch that proves the iOS trust boundary\n","# Competition iOS Runtime\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 path runs through live iOS trust boundaries rather than static strings or plist values alone.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Preserve the original IPA, extracted bundle, and any decrypted or re-signed copy as separate artifacts.\n2. Start with `Info.plist`, entitlements, URL schemes, frameworks, Keychain usage, and local app storage before broad runtime hooks.\n3. Choose the narrowest runtime boundary that proves behavior: signer, trust evaluator, Keychain accessor, Objective-C or Swift method, or network request builder.\n4. Correlate static bundle evidence and live hook output before claiming the trust path is understood.\n5. Reproduce the accepted request, token, or gated branch from the smallest hook set.\n\n## Workflow\n\n### 1. Static iOS Triage\n\n- Map bundle structure, `Info.plist`, entitlements, URL schemes, universal links, embedded frameworks, and app group paths.\n- Record likely trust boundaries: request signers, device binding, certificate checks, jailbreak checks, Keychain access, or local cache loading.\n- Note whether sensitive logic sits in Objective-C, Swift, embedded frameworks, or a bundled web surface.\n\n### 2. Hook The Runtime Boundary\n\n- Prefer hooking request builders, crypto helpers, trust evaluators, Keychain reads, or Objective-C selectors instead of broad UI handlers.\n- Record plaintext inputs, headers, nonces, signed strings, and outputs at the boundary that changes server acceptance.\n- Patch or bypass pinning or environment checks only enough to expose the real request path.\n\n### 3. Replay The Accepted Path\n\n- Rebuild the smallest stateful sequence: local token, device identifier, request body, signature, headers, and trust checks.\n- Keep hook logs, bundle paths, plist keys, and local storage artifacts tied to the same session or account state.\n- If the task becomes mostly about transform recovery instead of iOS runtime, switch back to the broader crypto or mobile skill.\n\n## Read This Reference\n\n- Load `references\u002Fios-runtime.md` for hook targets, storage checklist, and evidence packaging.\n\n## What To Preserve\n\n- Bundle paths, entitlements, plist keys, selectors, class names, hook points, and header names\n- Keychain items, local DB or plist paths, URL schemes, and app-group storage locations\n- The smallest replayable request or branch that proves the iOS trust boundary\n",{"name":5,"description":7},"main","5b045f5effb9db25a3199f06d549a00373078082",".agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-ios-runtime","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-ios-runtime",{"tool":36,"command":37},"bunx","bunx skills add Rain-kl\u002FReverseTemplate --skill competition-ios-runtime",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Rain-kl\u002FReverseTemplate --skill competition-ios-runtime","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-ios-runtime\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",392,"https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-ios-runtime\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fios-runtime.md",1187,"https:\u002F\u002Fgithub.com\u002FRain-kl\u002FReverseTemplate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freverse-skill\u002FCTF-Sandbox-Orchestrator\u002Fcompetition-ios-runtime\u002Freferences\u002Fios-runtime.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",[],[]]