[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DC0ZM9X7CY52N7XQDG38FQ":3,"skill-same:01M6DC0ZM9X7CY52N7XQDG38FQ":74},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6DC0ZM9X7CY52N7XQDG38FQ","swfoc-reverse-engineering",null,"Use when working on SWFOC editor runtime or native analysis, or on the swfoc_memory dump bundle, especially for dump triage, debugger attach flows, signature generation, binary comparison, import repair, or moving evidence between WinDbg Preview, x64dbg, Cheat Engine, IDA Pro, Binary Ninja, and Ghidra.","Prekzursil\u002Fagent-skills-toolchain","Prekzursil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54636077?v=4","01M6DACZ1PCQHD99SCR1YXG28B","Andrei Mihai Visalon","01M6DACZ670WZF535V3WYYSS4Z",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fswfoc-reverse-engineering\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"swfoc reverse engineering","engineering","attach","x64dbg","cheat","bundle","binary ninja","runtime","generation","repair","preview","memory","evidence","use","engine","analysis","debugger","ghidra","editor","triage","2026-11-10 10:12:30",false,"---\nname: swfoc-reverse-engineering\ndescription: Use when working on SWFOC editor runtime or native analysis, or on the swfoc_memory dump bundle, especially for dump triage, debugger attach flows, signature generation, binary comparison, import repair, or moving evidence between WinDbg Preview, x64dbg, Cheat Engine, IDA Pro, Binary Ninja, and Ghidra.\n---\n\n# SWFOC Reverse Engineering\n\n## Overview\n\nUse this skill for SWFOC-native evidence work: dump triage, runtime tracing, static follow-up, and signature or diff workflows. Keep XML, Lua, MEG packaging, and submod integration in `$swfoc-modding`; use this skill when the question is really about the executable, dump, memory layout, or runtime behavior.\n\n## Workspace Anchors\n\n- Source and trainer workspace: `C:\\Users\\Prekzursil\\Downloads\\SWFOC editor`\n- Dump and artifact workspace: `C:\\Users\\Prekzursil\\Downloads\\swfoc_memory`\n- Primary dump artifact: `StarWarsG.DMP`\n- Prebuilt evidence pack: `swfoc_memory\\chatgpt_pro_bundle\\`\n\n## Recommended Workflow\n\n1. Validate the target first. Confirm whether the request is about the SWFOC runtime, a dump artifact, or source-side modding. If it is XML, Lua, or packaging work, hand back to `$swfoc-modding`.\n2. For the dump path, start with `$windbg-preview` on `StarWarsG.DMP`. Use `$windbg-command-cookbook` when you need exact WinDbg commands, and capture exception context, loaded modules, and the most relevant threads before opening a disassembler.\n3. For the live-runtime path, use `$x64dbg` plus `$cheat-engine-workflow`. Use `$cheat-engine-x64dbg-ida-handoff` when the target workflow explicitly spans Cheat Engine, x64dbg, and IDA. Add `$ret-sync` only after the debugger path is stable enough to justify syncing into a disassembler.\n4. Move into static analysis once you know which module, function family, or address range matters. Use `$ida-decompiler-cleanup` for Hex-Rays cleanup, `$binary-ninja-diff-signatures` for Binary Ninja-centered diff\u002Fsignature work, or `$ghidra-automation-recipes` when Ghidra should be scripted. Use `$apply-callee-type-ex` in IDA, `$peutils` in Binary Ninja, or `$ghidra-bridge` for the narrower helper cases.\n5. Use `$swfoc-runtime-address-hunting` for SWFOC-specific anchors, then route durable findings through `$dump-to-signature-workflow`. When a finding must survive across game builds or variants, export both sides with `$binexport`, compare with `$bindiff`, and generate resilient patterns with `$binja-sigmaker` or a Cheat Engine AOB workflow.\n6. Escalate to the existing `$volatility-3` or `$angr` skills only for genuinely memory-forensics-specific extraction or symbolic analysis needs.\n\n## Common Mistakes\n\n- Jumping straight from a dump to random decompiler browsing without first capturing the exception and thread context.\n- Mixing modding tasks and runtime RE tasks in one workflow without deciding which artifact is authoritative.\n- Treating one-off absolute addresses as stable without diffing or signature work.\n- Forgetting to reuse the existing evidence bundle under `swfoc_memory\\chatgpt_pro_bundle` before redoing work.\n\n## Reference Map\n\nRead `references\u002Fworkspace.md` for the local workspace layout, the recommended first-pass commands, and the exact artifact folders that are already present.\n","# SWFOC Reverse Engineering\n\n## Overview\n\nUse this skill for SWFOC-native evidence work: dump triage, runtime tracing, static follow-up, and signature or diff workflows. Keep XML, Lua, MEG packaging, and submod integration in `$swfoc-modding`; use this skill when the question is really about the executable, dump, memory layout, or runtime behavior.\n\n## Workspace Anchors\n\n- Source and trainer workspace: `C:\\Users\\Prekzursil\\Downloads\\SWFOC editor`\n- Dump and artifact workspace: `C:\\Users\\Prekzursil\\Downloads\\swfoc_memory`\n- Primary dump artifact: `StarWarsG.DMP`\n- Prebuilt evidence pack: `swfoc_memory\\chatgpt_pro_bundle\\`\n\n## Recommended Workflow\n\n1. Validate the target first. Confirm whether the request is about the SWFOC runtime, a dump artifact, or source-side modding. If it is XML, Lua, or packaging work, hand back to `$swfoc-modding`.\n2. For the dump path, start with `$windbg-preview` on `StarWarsG.DMP`. Use `$windbg-command-cookbook` when you need exact WinDbg commands, and capture exception context, loaded modules, and the most relevant threads before opening a disassembler.\n3. For the live-runtime path, use `$x64dbg` plus `$cheat-engine-workflow`. Use `$cheat-engine-x64dbg-ida-handoff` when the target workflow explicitly spans Cheat Engine, x64dbg, and IDA. Add `$ret-sync` only after the debugger path is stable enough to justify syncing into a disassembler.\n4. Move into static analysis once you know which module, function family, or address range matters. Use `$ida-decompiler-cleanup` for Hex-Rays cleanup, `$binary-ninja-diff-signatures` for Binary Ninja-centered diff\u002Fsignature work, or `$ghidra-automation-recipes` when Ghidra should be scripted. Use `$apply-callee-type-ex` in IDA, `$peutils` in Binary Ninja, or `$ghidra-bridge` for the narrower helper cases.\n5. Use `$swfoc-runtime-address-hunting` for SWFOC-specific anchors, then route durable findings through `$dump-to-signature-workflow`. When a finding must survive across game builds or variants, export both sides with `$binexport`, compare with `$bindiff`, and generate resilient patterns with `$binja-sigmaker` or a Cheat Engine AOB workflow.\n6. Escalate to the existing `$volatility-3` or `$angr` skills only for genuinely memory-forensics-specific extraction or symbolic analysis needs.\n\n## Common Mistakes\n\n- Jumping straight from a dump to random decompiler browsing without first capturing the exception and thread context.\n- Mixing modding tasks and runtime RE tasks in one workflow without deciding which artifact is authoritative.\n- Treating one-off absolute addresses as stable without diffing or signature work.\n- Forgetting to reuse the existing evidence bundle under `swfoc_memory\\chatgpt_pro_bundle` before redoing work.\n\n## Reference Map\n\nRead `references\u002Fworkspace.md` for the local workspace layout, the recommended first-pass commands, and the exact artifact folders that are already present.\n",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5",".agents\u002Fskills\u002Fswfoc-reverse-engineering","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill swfoc-reverse-engineering",{"tool":56,"command":57},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill swfoc-reverse-engineering",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill swfoc-reverse-engineering","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fswfoc-reverse-engineering\u002FSKILL.md",true,[64,70],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"agents\u002Fopenai.yaml","REFERENCE","参考文档",250,"https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fswfoc-reverse-engineering\u002Fagents\u002Fopenai.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fworkspace.md",996,"https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fswfoc-reverse-engineering\u002Freferences\u002Fworkspace.md",[75,96,127,154,168,184],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":39},"01M6DF7D7478R55P46REYH4QAC","clarify-requirements","Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fworkspace-hooks\u002Fskills\u002Fclarify-requirements\u002FSKILL.md",[],[82,83,84,85,86,87,88,89,90,32,91,92,93,94,95],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","context","repo","injection","execution","file",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":107,"publishedAt":39},"01M6DF79CA4BHJS66J8EZDBPWJ","openmm-md","Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein \u002F protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fmcp\u002Fopenmm-md-mcp\u002Fskill\u002Fopenmm-md\u002FSKILL.md",[102],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[108,109,110,111,112,113,114,115,116,117,118,119,120,121,32,122,123,124,125,126],"openmm md","how","decision","pick","linux","analyze","tool","stack","open","NVIDIA","gpu","license","workflow","windows","free","molecular dynamics","local","do","MCP",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":139,"publishedAt":39},"01M6DF76C1MG85VEWP8VZCBNMN","visual-review","Take screenshots of web pages and UI using Playwright for visual review and iteration","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fvisual-review\u002FSKILL.md",[133,136],{"categoryNo":134,"categoryName":135,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":137,"categoryName":138,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000008","测试与质量",[140,141,142,143,144,145,146,147,148,149,109,150,151,152,153],"review","visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":39},"01M6DF73AQVCBZKEN0YXEX9FXP","status","Diagnostic status report — shows metaswarm installation state, project setup, and potential issues","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstatus\u002FSKILL.md",[],[156,161,162,163,164,165,166,167],"setup","report","project","installation","project setup","issues","state",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":175,"publishedAt":39},"01M6DF6X6C2XB0P6GX76P7TTYV","start","Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstart\u002FSKILL.md",[174],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},[170,176,87,177,178,179,32,180,181,182,183],"start issue","issue","ready","work on issue","user","work","work on","development",{"skillNo":185,"name":161,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":39},"01M6DF6QMJ9AJKFKHHKRT005PQ","Interactive project setup — detects your project, configures metaswarm, writes project-local files","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fsetup\u002FSKILL.md",[],[161,163,124,190,165,191],"files","interactive"]