[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DB0GR2JRF65YS97G5E1HGF":3,"skill-same:01M7DB0GR2JRF65YS97G5E1HGF":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"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":29,"updatedAt":30,"install":31,"resources":44},"01M7DB0GR2JRF65YS97G5E1HGF","overview",null,"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\u002Foverview\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: awesome-game-security-overview\ndescription: Guide for understanding and contributing to the awesome-game-security curated resource list. Use this skill when adding new resources, organizing categories, mapping topics across anti-cheat, Windows kernel, DMA, reverse engineering, and game-engine research, or maintaining README.md format consistency.\nx-alice-class: reverse\n---# Awesome Game Security - Project Overview\n\n## Purpose\n\nThis is a curated collection of resources related to game security, covering both offensive (game hacking, cheating) and defensive (anti-cheat) aspects. The project serves as a comprehensive reference for security researchers, game developers, and enthusiasts, especially where Windows internals, driver trust, reverse engineering, DMA, and modern anti-cheat defenses intersect.\n\n## README Coverage\n\n- Top-level engines and rendering: `Game Engine`, `Renderer`, `DirectX`, `OpenGL`, `Vulkan`\n- Offensive research: `Cheat`\n- Defensive research: `Anti Cheat`\n- Platform hardening: `Windows Security Features`\n- Platform-specific ecosystems: `Android Emulator`, `IOS Emulator`, `Windows Emulator`, `Linux Emulator`\n- Supporting infrastructure: `Mathematics`, `3D Graphics`, `AI`, `Image Codec`, `Wavefront Obj`, `Task Scheduler`, `Game Network`, `PhysX SDK`, `Game Develop`, `Game Assets`, `Game Hot Patch`, `Game Testing`, `Game Tools`, `Game Manager`, `Game CI`\n- Platform subsystems: `WSL`, `WSA`\n- Console emulation: `Game Boy`, `Nintendo Switch`, `Xbox`, `PlayStation`\n- Tips and tricks: `Some Tricks`\n\n## Project Structure\n\n```\nawesome-game-security\u002F\n├── README.md           # Main resource list\n├── LICENSE             # MIT License\n├── awesome-image.webp  # Project banner\n└── scripts\u002F\n    ├── generate-toc.py  # Generate table of contents\n    └── remove-forks.py  # Clean up forked repos\n```\n\n## README.md Format Convention\n\n### Category Structure\n\nEach category follows this format:\n\n```markdown\n## Category Name\n> Subcategory (optional)\n- https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo [Brief description]\n- https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo [Another description]\n```\n\n### Link Format\n\n- Always use full GitHub URLs for repositories\n- Non-GitHub links are also supported (blog posts, articles, documentation sites)\n- Add brief descriptions in square brackets `[description]`\n- Use consistent spacing and formatting\n- Group related resources under subcategories with `>`\n\n### Example Entry\n\n```markdown\n## Game Engine\n> Guide\n- https:\u002F\u002Fgithub.com\u002Fexample\u002Fguide [Comprehensive game dev guide]\n\n> Source\n- https:\u002F\u002Fgithub.com\u002Fexample\u002Fengine [Open source game engine]\n```\n\n## Skill Routing Guide\n\nWhen an AI agent receives a query, use this table to select the best skill:\n\n| Query topic | Primary skill | Related skills |\n|---|---|---|\n| EAC, BattlEye, Vanguard, detection, heartbeat, screenshot | anti-cheat | windows-kernel |\n| pcileech, FPGA, DMA, IOMMU, Thunderbolt | dma-attack | anti-cheat |\n| Unreal SDK, Unity IL2CPP, engine structs, Godot, Lumix | game-engine | game-hacking |\n| Memory hacking, injection, overlays, driver comm, HWID spoof | game-hacking | graphics-api |\n| D3D\u002FVulkan\u002FOpenGL hooks, Present hook, shader interception | graphics-api | game-hacking |\n| Android root, Frida, iOS jailbreak, KernelSU, APatch | mobile-security | game-hacking |\n| IDA, Ghidra, DBI, deobfuscation, binary diffing, MCP RE tools, trap-and-emulate CFT, WHP tracing | reverse-engineering | anti-cheat, windows-kernel |\n| Drivers, callbacks, PatchGuard, HVCI, ETW, pool forensics, WHP API | windows-kernel | anti-cheat, reverse-engineering |\n| Claim validation, citation checks, detector evaluation, evidence conflicts | research-rigor | the matching domain skill |\n| Adding resources, README format, link validation | overview | (any) |\n\nAlso check `wiki\u002Foverviews\u002F\u003Ctopic>.md` for the matching primary skill topic before deep README\u002Farchive dives.\n\n## Main Categories\n\nAll 27 top-level `##` sections in README.md:\n\n1. **Game Engine**: Engines, source code, plugins (Unreal\u002FUnity\u002FGodot\u002FLumix), detectors\n2. **Mathematics**: Linear algebra, physics libraries\n3. **Renderer**: Software renderers, ray tracing\n4. **3D Graphics**: 3D modeling and graphics resources\n5. **AI**: Machine learning for games\n6. **Image Codec**: Image processing libraries\n7. **Wavefront Obj**: OBJ file parsers\n8. **Task Scheduler**: Job\u002Ftask scheduling systems\n9. **Game Network**: Networking, KCP, JWT, geolocation\n10. **PhysX SDK**: NVIDIA PhysX resources\n11. **Game Develop**: Development guides, source code, MCP servers, AI agents\n12. **Game Assets \u002F Hot Patch \u002F Testing \u002F Tools \u002F Manager \u002F CI**: Supporting infrastructure\n13. **DirectX**: Guides, hooks, tools, emulation, overlays\n14. **OpenGL**: Guides, source, hooks\n15. **Vulkan**: API, guides, hooks\n16. **Cheat**: Offensive research (debugging, injection, hooking, DMA, overlays, driver comm, EFI, anti-forensics, game-specific)\n17. **Anti Cheat**: Defensive research (protection, detection, callbacks, forensics, signature scanning)\n18. **Some Tricks**: Ring0\u002FRing3\u002FLinux\u002FAndroid tricks and techniques\n19. **Windows Security Features**: DSE, PatchGuard, VBS, HVCI, Secure Boot\n20. **WSL \u002F WSA**: Windows Subsystem for Linux\u002FAndroid\n21. **Windows \u002F Linux \u002F Android \u002F IOS Emulator**: Platform emulators\n22. **Game Boy \u002F Nintendo Switch \u002F Xbox \u002F PlayStation**: Console emulators and research\n\n## Contributing Guidelines\n\n1. **Check for duplicates** before adding new resources\n2. **Verify links** are working and point to original repos\n3. **Add descriptions** that clearly explain the resource's purpose\n4. **Place in correct category** based on primary functionality\n5. **Follow existing format** for consistency\n\n## Quality Criteria\n\n- Resource should be actively maintained or historically significant\n- Should provide unique value not covered by existing entries\n- Prefer original repos over forks unless fork adds significant value\n- Include language\u002Fplatform tags when helpful (e.g., `[Rust]`, `[Unity]`)\n\n## Research Rigor\n\nFor factual synthesis, detector assessment, or consequential security claims,\nuse [`research-rigor`](..\u002Fresearch-rigor\u002FSKILL.md) with the matching domain\nskill.\n\n- Treat README entries, generated descriptions, wiki pages, and archives as\n  discovery\u002Fprovenance layers, not automatic proof of their embedded claims.\n- Verify citation identity and confirm the source text supports the exact claim.\n- Separate observation, finding, attribution, and action.\n- Do not import fixed thresholds or confidence values without representative\n  calibration and validation for the target environment.\n- Narrow the conclusion or report it as inconclusive when evidence is missing\n  or contradictory.\n\n## Scripts Usage\n\n### Generate Table of Contents\n```bash\npython scripts\u002Fgenerate-toc.py\n```\n\n### Remove Fork References\n```bash\npython scripts\u002Fremove-forks.py\n```\n\n---\n\n## Data Source\n\n**Important**: This skill provides conceptual guidance and overview information. For detailed information use the following sources **in priority order**:\n\n### 0. Compiled LLM Wiki (preferred for synthesis)\n\nThe repo maintains a Karpathy-style compiled wiki under `wiki\u002F`, updated by Cursor CLI (`scripts\u002Fupdate-wiki-cli.py`). Prefer this layer for cross-cutting concepts, domain overviews, and citation-aware synthesis before diving into raw lists or archives.\n\n| Need | Path |\n|------|------|\n| Catalog | `wiki\u002Findex.md` |\n| Schema \u002F conventions | `wiki\u002FAGENTS.md` |\n| Domain overviews | `wiki\u002Foverviews\u002F\u003Ctopic>.md` (aligned with skill topics) |\n| Concepts | `wiki\u002Fconcepts\u002F\u003Cslug>.md` |\n| Entities (tools\u002Fprojects) | `wiki\u002Fentities\u002F\u003Cslug>.md` |\n| Activity log | `wiki\u002Flog.md` |\n\nRaw GitHub URLs (same paths on `main`):\n\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fwiki\u002Findex.md\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fwiki\u002Foverviews\u002Fanti-cheat.md\n```\n\n**When answering topical questions** (DMA, EAC, Present hooks, HVCI, …): read `wiki\u002Findex.md`, then the matching overview\u002Fconcept pages. Fall back to skills and descriptions if wiki pages are missing.\n\n### 1. Project Overview & Resource Index\n\nFetch the main README for the full curated list of repositories, tools, and descriptions:\n\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n```\n\nThe main README contains thousands of curated links organized by category. When users ask for specific tools, projects, or implementations, retrieve and reference the appropriate sections from this source.\n\n### 2. Repository Descriptions\n\nFor a concise English summary of what a repository does, the project maintains auto-generated description files.\n\n**Description URL format:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002F{owner}\u002F{repo}\u002Fdescription_en.txt\n```\n\n**Examples:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002F00christian00\u002FUnityDecompiled\u002Fdescription_en.txt\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002Fufrisk\u002Fpcileech\u002Fdescription_en.txt\n```\n\n**How to use:**\n1. Identify the GitHub repository the user is asking about (owner and repo name from the URL).\n2. Construct the description URL: replace `{owner}` with the GitHub username\u002Forg and `{repo}` with the repository name.\n3. Fetch the description file — it contains a short, human-readable summary of the repository's purpose and contents.\n4. If the fetch returns a 404, the description has not been generated yet; fall back to the README entry or the archive.\n\n### 3. Repository Code Details (Archive)\n\nFor detailed repository information (file structure, source code, implementation details), the project maintains a local archive. If a repository has been archived, **prefer fetching from the archive** over cloning or browsing GitHub directly — but prefer description + wiki first for high-level answers.\n\n**Archive URL format:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002F{owner}\u002F{repo}.txt\n```\n\n**Examples:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002Fufrisk\u002Fpcileech.txt\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002F000-aki-000\u002FGameDebugMenu.txt\n```\n\n**How to use:**\n1. Identify the GitHub repository the user is asking about (owner and repo name from the URL).\n2. Construct the archive URL: replace `{owner}` with the GitHub username\u002Forg and `{repo}` with the repository name (no `.git` suffix).\n3. Fetch the archive file — it contains a full code snapshot with file trees and source code generated by `code2prompt`.\n4. If the fetch returns a 404, the repository has not been archived yet; fall back to the README or direct GitHub browsing.\n\n**Priority order when answering questions about a specific repository:**\n1. Wiki entity\u002Fconcept (if present) — compiled context\n2. Description (quick summary) — `description\u002F{owner}\u002F{repo}\u002Fdescription_en.txt`\n3. Archive (full code snapshot) — when deeper implementation details are needed\n4. README entry — fallback when neither wiki, description, nor archive is available\n\n---\n\n## Compiled wiki\n\nStart with `wiki\u002Findex.md` and `wiki\u002Foverviews\u002Foverview.md`. Schema: `wiki\u002FAGENTS.md`. Maintained by `scripts\u002Fupdate-wiki-cli.py`.\n","## Purpose\n\nThis is a curated collection of resources related to game security, covering both offensive (game hacking, cheating) and defensive (anti-cheat) aspects. The project serves as a comprehensive reference for security researchers, game developers, and enthusiasts, especially where Windows internals, driver trust, reverse engineering, DMA, and modern anti-cheat defenses intersect.\n\n## README Coverage\n\n- Top-level engines and rendering: `Game Engine`, `Renderer`, `DirectX`, `OpenGL`, `Vulkan`\n- Offensive research: `Cheat`\n- Defensive research: `Anti Cheat`\n- Platform hardening: `Windows Security Features`\n- Platform-specific ecosystems: `Android Emulator`, `IOS Emulator`, `Windows Emulator`, `Linux Emulator`\n- Supporting infrastructure: `Mathematics`, `3D Graphics`, `AI`, `Image Codec`, `Wavefront Obj`, `Task Scheduler`, `Game Network`, `PhysX SDK`, `Game Develop`, `Game Assets`, `Game Hot Patch`, `Game Testing`, `Game Tools`, `Game Manager`, `Game CI`\n- Platform subsystems: `WSL`, `WSA`\n- Console emulation: `Game Boy`, `Nintendo Switch`, `Xbox`, `PlayStation`\n- Tips and tricks: `Some Tricks`\n\n## Project Structure\n\n```\nawesome-game-security\u002F\n├── README.md           # Main resource list\n├── LICENSE             # MIT License\n├── awesome-image.webp  # Project banner\n└── scripts\u002F\n    ├── generate-toc.py  # Generate table of contents\n    └── remove-forks.py  # Clean up forked repos\n```\n\n## README.md Format Convention\n\n### Category Structure\n\nEach category follows this format:\n\n```markdown\n## Category Name\n> Subcategory (optional)\n- https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo [Brief description]\n- https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo [Another description]\n```\n\n### Link Format\n\n- Always use full GitHub URLs for repositories\n- Non-GitHub links are also supported (blog posts, articles, documentation sites)\n- Add brief descriptions in square brackets `[description]`\n- Use consistent spacing and formatting\n- Group related resources under subcategories with `>`\n\n### Example Entry\n\n```markdown\n## Game Engine\n> Guide\n- https:\u002F\u002Fgithub.com\u002Fexample\u002Fguide [Comprehensive game dev guide]\n\n> Source\n- https:\u002F\u002Fgithub.com\u002Fexample\u002Fengine [Open source game engine]\n```\n\n## Skill Routing Guide\n\nWhen an AI agent receives a query, use this table to select the best skill:\n\n| Query topic | Primary skill | Related skills |\n|---|---|---|\n| EAC, BattlEye, Vanguard, detection, heartbeat, screenshot | anti-cheat | windows-kernel |\n| pcileech, FPGA, DMA, IOMMU, Thunderbolt | dma-attack | anti-cheat |\n| Unreal SDK, Unity IL2CPP, engine structs, Godot, Lumix | game-engine | game-hacking |\n| Memory hacking, injection, overlays, driver comm, HWID spoof | game-hacking | graphics-api |\n| D3D\u002FVulkan\u002FOpenGL hooks, Present hook, shader interception | graphics-api | game-hacking |\n| Android root, Frida, iOS jailbreak, KernelSU, APatch | mobile-security | game-hacking |\n| IDA, Ghidra, DBI, deobfuscation, binary diffing, MCP RE tools, trap-and-emulate CFT, WHP tracing | reverse-engineering | anti-cheat, windows-kernel |\n| Drivers, callbacks, PatchGuard, HVCI, ETW, pool forensics, WHP API | windows-kernel | anti-cheat, reverse-engineering |\n| Claim validation, citation checks, detector evaluation, evidence conflicts | research-rigor | the matching domain skill |\n| Adding resources, README format, link validation | overview | (any) |\n\nAlso check `wiki\u002Foverviews\u002F\u003Ctopic>.md` for the matching primary skill topic before deep README\u002Farchive dives.\n\n## Main Categories\n\nAll 27 top-level `##` sections in README.md:\n\n1. **Game Engine**: Engines, source code, plugins (Unreal\u002FUnity\u002FGodot\u002FLumix), detectors\n2. **Mathematics**: Linear algebra, physics libraries\n3. **Renderer**: Software renderers, ray tracing\n4. **3D Graphics**: 3D modeling and graphics resources\n5. **AI**: Machine learning for games\n6. **Image Codec**: Image processing libraries\n7. **Wavefront Obj**: OBJ file parsers\n8. **Task Scheduler**: Job\u002Ftask scheduling systems\n9. **Game Network**: Networking, KCP, JWT, geolocation\n10. **PhysX SDK**: NVIDIA PhysX resources\n11. **Game Develop**: Development guides, source code, MCP servers, AI agents\n12. **Game Assets \u002F Hot Patch \u002F Testing \u002F Tools \u002F Manager \u002F CI**: Supporting infrastructure\n13. **DirectX**: Guides, hooks, tools, emulation, overlays\n14. **OpenGL**: Guides, source, hooks\n15. **Vulkan**: API, guides, hooks\n16. **Cheat**: Offensive research (debugging, injection, hooking, DMA, overlays, driver comm, EFI, anti-forensics, game-specific)\n17. **Anti Cheat**: Defensive research (protection, detection, callbacks, forensics, signature scanning)\n18. **Some Tricks**: Ring0\u002FRing3\u002FLinux\u002FAndroid tricks and techniques\n19. **Windows Security Features**: DSE, PatchGuard, VBS, HVCI, Secure Boot\n20. **WSL \u002F WSA**: Windows Subsystem for Linux\u002FAndroid\n21. **Windows \u002F Linux \u002F Android \u002F IOS Emulator**: Platform emulators\n22. **Game Boy \u002F Nintendo Switch \u002F Xbox \u002F PlayStation**: Console emulators and research\n\n## Contributing Guidelines\n\n1. **Check for duplicates** before adding new resources\n2. **Verify links** are working and point to original repos\n3. **Add descriptions** that clearly explain the resource's purpose\n4. **Place in correct category** based on primary functionality\n5. **Follow existing format** for consistency\n\n## Quality Criteria\n\n- Resource should be actively maintained or historically significant\n- Should provide unique value not covered by existing entries\n- Prefer original repos over forks unless fork adds significant value\n- Include language\u002Fplatform tags when helpful (e.g., `[Rust]`, `[Unity]`)\n\n## Research Rigor\n\nFor factual synthesis, detector assessment, or consequential security claims,\nuse [`research-rigor`](..\u002Fresearch-rigor\u002FSKILL.md) with the matching domain\nskill.\n\n- Treat README entries, generated descriptions, wiki pages, and archives as\n  discovery\u002Fprovenance layers, not automatic proof of their embedded claims.\n- Verify citation identity and confirm the source text supports the exact claim.\n- Separate observation, finding, attribution, and action.\n- Do not import fixed thresholds or confidence values without representative\n  calibration and validation for the target environment.\n- Narrow the conclusion or report it as inconclusive when evidence is missing\n  or contradictory.\n\n## Scripts Usage\n\n### Generate Table of Contents\n```bash\npython scripts\u002Fgenerate-toc.py\n```\n\n### Remove Fork References\n```bash\npython scripts\u002Fremove-forks.py\n```\n\n---\n\n## Data Source\n\n**Important**: This skill provides conceptual guidance and overview information. For detailed information use the following sources **in priority order**:\n\n### 0. Compiled LLM Wiki (preferred for synthesis)\n\nThe repo maintains a Karpathy-style compiled wiki under `wiki\u002F`, updated by Cursor CLI (`scripts\u002Fupdate-wiki-cli.py`). Prefer this layer for cross-cutting concepts, domain overviews, and citation-aware synthesis before diving into raw lists or archives.\n\n| Need | Path |\n|------|------|\n| Catalog | `wiki\u002Findex.md` |\n| Schema \u002F conventions | `wiki\u002FAGENTS.md` |\n| Domain overviews | `wiki\u002Foverviews\u002F\u003Ctopic>.md` (aligned with skill topics) |\n| Concepts | `wiki\u002Fconcepts\u002F\u003Cslug>.md` |\n| Entities (tools\u002Fprojects) | `wiki\u002Fentities\u002F\u003Cslug>.md` |\n| Activity log | `wiki\u002Flog.md` |\n\nRaw GitHub URLs (same paths on `main`):\n\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fwiki\u002Findex.md\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fwiki\u002Foverviews\u002Fanti-cheat.md\n```\n\n**When answering topical questions** (DMA, EAC, Present hooks, HVCI, …): read `wiki\u002Findex.md`, then the matching overview\u002Fconcept pages. Fall back to skills and descriptions if wiki pages are missing.\n\n### 1. Project Overview & Resource Index\n\nFetch the main README for the full curated list of repositories, tools, and descriptions:\n\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n```\n\nThe main README contains thousands of curated links organized by category. When users ask for specific tools, projects, or implementations, retrieve and reference the appropriate sections from this source.\n\n### 2. Repository Descriptions\n\nFor a concise English summary of what a repository does, the project maintains auto-generated description files.\n\n**Description URL format:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002F{owner}\u002F{repo}\u002Fdescription_en.txt\n```\n\n**Examples:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002F00christian00\u002FUnityDecompiled\u002Fdescription_en.txt\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002Fufrisk\u002Fpcileech\u002Fdescription_en.txt\n```\n\n**How to use:**\n1. Identify the GitHub repository the user is asking about (owner and repo name from the URL).\n2. Construct the description URL: replace `{owner}` with the GitHub username\u002Forg and `{repo}` with the repository name.\n3. Fetch the description file — it contains a short, human-readable summary of the repository's purpose and contents.\n4. If the fetch returns a 404, the description has not been generated yet; fall back to the README entry or the archive.\n\n### 3. Repository Code Details (Archive)\n\nFor detailed repository information (file structure, source code, implementation details), the project maintains a local archive. If a repository has been archived, **prefer fetching from the archive** over cloning or browsing GitHub directly — but prefer description + wiki first for high-level answers.\n\n**Archive URL format:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002F{owner}\u002F{repo}.txt\n```\n\n**Examples:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002Fufrisk\u002Fpcileech.txt\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002F000-aki-000\u002FGameDebugMenu.txt\n```\n\n**How to use:**\n1. Identify the GitHub repository the user is asking about (owner and repo name from the URL).\n2. Construct the archive URL: replace `{owner}` with the GitHub username\u002Forg and `{repo}` with the repository name (no `.git` suffix).\n3. Fetch the archive file — it contains a full code snapshot with file trees and source code generated by `code2prompt`.\n4. If the fetch returns a 404, the repository has not been archived yet; fall back to the README or direct GitHub browsing.\n\n**Priority order when answering questions about a specific repository:**\n1. Wiki entity\u002Fconcept (if present) — compiled context\n2. Description (quick summary) — `description\u002F{owner}\u002F{repo}\u002Fdescription_en.txt`\n3. Archive (full code snapshot) — when deeper implementation details are needed\n4. README entry — fallback when neither wiki, description, nor archive is available\n\n---\n\n## Compiled wiki\n\nStart with `wiki\u002Findex.md` and `wiki\u002Foverviews\u002Foverview.md`. Schema: `wiki\u002FAGENTS.md`. Maintained by `scripts\u002Fupdate-wiki-cli.py`.\n",{},"main","19a54ac988e9929160334271f5c1924ddd9b227e","_modules\u002Foverview",19,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill","https:\u002F\u002Fgithub.com\u002Falicewe1","写一些自己用得上的工具，能自动化就绝不手动 · 自动化 \u002F 工程效率 \u002F Agent 技能生态 · 保持好奇，持续构建","2026-09-30 00:41:20",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add alicewe1\u002Falice_skill --skill overview",{"tool":37,"command":38},"bunx","bunx skills add alicewe1\u002Falice_skill --skill overview",{"tool":40,"command":41},"pnpm","pnpm dlx skills add alicewe1\u002Falice_skill --skill overview","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Foverview\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7DBMD9P6R27SWQCW5HYVWG0","alice","Alice 六类技能总路由。用户输入 Alice 或要求查看 Alice 技能菜单时，严格输出固定菜单；输入攻\u002F防模式、六类入口或直接描述任务时，按类别→领域→模块渐进路由。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Faliceskill\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"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",[],[]]