[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BJZVH8NAFGE8CSGP2PCK4S":3,"skill-same:01M7BJZVH8NAFGE8CSGP2PCK4S":73},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7BJZVH8NAFGE8CSGP2PCK4S","nemo-mbridge-perf-moe-optimization-workflow",null,"Systematic workflow for MoE training optimization in Megatron Bridge, based on the Megatron-Core MoE paper. Covers the Three Walls framework, parallel folding, recompute strategy, dispatcher choice, and CUDA-graph bring-up.","YYC-Cube\u002FYYC3-AI-Agent-Archive","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79K9J2WD44BBY4662XKNZRB",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nemo-mbridge-perf-moe-optimization-workflow\ndescription: Systematic workflow for MoE training optimization in Megatron Bridge, based on the Megatron-Core MoE paper. Covers the Three Walls framework, parallel folding, recompute strategy, dispatcher choice, and CUDA-graph bring-up.\ncategory: development-code\nversion: 1.0.0\nlicense: Apache-2.0\nwhen_to_use: Full MoE throughput tuning sweep, or diagnosing a MoE throughput regression after a commit or config change; 'optimize MoE throughput', 'MoE perf tuning', 'Three Walls', 'memory wall', 'communication wall', 'compute wall'.\n---\n\n# MoE Training Optimization Workflow\n\nStable docs: @docs\u002Ftraining\u002Fmoe-optimization.md\nCard: @skills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002Fcard.yaml\nSource: [Scalable Training of MoE Models with Megatron Core](https:\u002F\u002Farxiv.org\u002Fabs\u002F2603.07685)\n\n## Quick Reference\n\nThink in terms of the paper's Three Walls:\n\n- memory wall\n- communication wall\n- compute and host-overhead wall\n\nMoE tuning is iterative. Fixing one wall usually exposes the next one, so the\nbest workflow is: fit first, scale second, profile third, then retune.\n\n## First Answer Checklist\n\nFor MoE optimization workflow prompts, present the response in this order:\n\n1. **Fit**: make the model memory-feasible first. Use the smallest model\n   parallelism that fits, prefer selective recompute before full recompute, add\n   offloading only after recompute and parallelism are insufficient, and use\n   `--fake-init-process-group` to sanity-check large layouts.\n2. **Scale**: maximize DP after the model fits, keep hot communication inside\n   the fastest interconnect, use PP plus VPP for multi-node scaling, prefer EP\n   over extra TP for expert layers, and add CP when long context makes attention\n   memory dominant.\n3. **Profile**: identify the dominant wall: memory, communication, host\n   overhead, or compute.\n4. **Retune**: change dispatcher, overlap, FP8 mode, CUDA graphs, or recompute\n   based on the profiled bottleneck.\n5. Include the exact Parallel Folding meshes: `Attention: TP x CP x DP x PP`\n   and `MoE: ETP x EP x EDP x PP`.\n6. Include the default mappings: `alltoall` for safe bring-up,\n   `flex` + `deepep` for H100\u002FB200-style systems, `flex` + `hybridep` for\n   GB200\u002FGB300\u002FNVL72 systems, Hopper to FP8 blockwise, Blackwell to MXFP8, and\n   dropless MoE TE-scoped CUDA graphs over `attn`, `moe_router`, and\n   `moe_preprocess`.\n\n## Phase 1: Make The Run Memory-Feasible\n\nStart with a configuration that fits reliably before chasing throughput.\n\nRecommended order:\n\n1. Use the smallest amount of model parallelism that still fits.\n2. Turn on selective recompute before falling back to full recompute.\n3. Add offloading only when recompute and parallelism are still insufficient.\n4. Use `--fake-init-process-group` to sanity-check large parallel layouts on a\n   single GPU before burning cluster time.\n\n### Recompute guidance\n\nPrefer selective recompute for MoE runs:\n\n- good first choices: `layernorm`, `core_attn`, `moe_act`, `mlp`, or\n  model-specific modules (`shared_experts`, `mla_up_proj`)\n- use full recompute only when the run still does not fit\n- revisit recompute after enabling CUDA graphs, because some graph scopes and\n  full recompute paths do not mix well\n\nAs a rule of thumb, fine-grained recompute often recovers most of the needed\nmemory while keeping throughput much closer to the non-recompute baseline than\nfull-layer recompute does.\n\n## Phase 2: Choose Parallelism For Scale\n\nPriority order:\n\n1. Maximize DP once the model fits.\n2. Keep the hot communication path inside the fast interconnect when possible.\n3. Use PP, plus VPP if needed, for multi-node scaling.\n4. Prefer EP over extra TP for expert layers.\n5. Add CP for long context once sequence length makes attention memory dominant.\n\n### Parallel Folding\n\nParallel Folding decouples attention and MoE parallelism so you do not have to\npick a single compromise layout:\n\n```text\nAttention: TP × CP × DP × PP\nMoE:       ETP × EP × EDP × PP\n```\n\nKey knobs:\n\n- `--expert-model-parallel-size`\n- `--expert-tensor-parallel-size`\n\nUse it when attention prefers some TP or CP, but expert layers benefit from a\nlarger EP degree than the dense layers can tolerate.\n\n## Phase 3: Profile The Dominant Bottleneck\n\n| Bottleneck | What it looks like | Primary fixes |\n|---|---|---|\n| Memory | Run fits only with aggressive full recompute or OOMs during warmup | selective recompute, FP8, offloading, better PP layout |\n| Communication | Nsight shows large all-to-all or collective blocks | DeepEP or HybridEP, EP overlap, DP\u002FTP overlap, better PP layout |\n| Host overhead | GPU gaps, launch-bound traces, Python overhead | CUDA graphs, `--manual-gc`, higher MBS, CPU affinity tuning |\n| Compute | Low SM utilization after comm and host issues are addressed | grouped GEMM, fusion work, FP8, dispatcher-specific kernel tuning |\n\n## Dispatcher And Overlap Guidance\n\nUse dispatcher choice as a bottleneck fix, not as the first tuning knob.\n\n- `moe_token_dispatcher_type=\"alltoall\"`: safest bring-up path, fine for\n  smaller EP sizes\n- `moe_token_dispatcher_type=\"flex\"` + `moe_flex_dispatcher_backend=\"deepep\"`:\n  strong default for H100 and B200 style deployments\n- `moe_token_dispatcher_type=\"flex\"` + `moe_flex_dispatcher_backend=\"hybridep\"`:\n  strongest starting point on GB200 or GB300 NVL72 systems\n\nIf the all-to-all path is visible in profiles, combine dispatcher tuning with:\n\n- `--overlap-moe-expert-parallel-comm`\n- `--overlap-grad-reduce`\n- `--tp-comm-overlap`\n\n## FP8 Recipe Quick Decision\n\n| Platform | Recommended starting recipe |\n|---|---|\n| Hopper | FP8 blockwise |\n| Blackwell | MXFP8 |\n| Blackwell, speed-first exploration | NVFP4 after the BF16 or FP8 path is stable |\n\nKeep the router in FP32. The largest wins usually come from expert GEMMs and\nother heavy matrix math, not from trying to quantize every small MoE component.\n\n## CUDA Graphs For MoE\n\nFor dropless MoE, start with partial TE-scoped graphs:\n\n- `attn`\n- `moe_router`\n- `moe_preprocess`\n\nThat path usually gives a meaningful step-time win while keeping the dynamic\nexpert work outside the graph. Expect a moderate speedup when launch overhead is\nvisible, but budget several extra GB of memory and verify that shapes remain\nstatic.\n\nUse full-iteration graphs only for graph-friendly workloads such as drop-and-pad\nor tightly controlled static-shape experiments.\n\nRelated references:\n\n- @skills\u002Fnemo-mbridge-perf-cuda-graphs\u002FSKILL.md\n- @docs\u002Ftraining\u002Fcuda-graphs.md\n- @docs\u002Ftraining\u002Factivation-recomputation.md\n\n## Pitfalls\n\n1. **Do not optimize in the wrong order**: fitting the model and selecting sane\n   parallelism matter more than micro-optimizations.\n\n2. **Platform changes the limiting wall**: H100-class runs often feel more\n   communication-bound, while GB200 or GB300 runs often expose CPU or launch\n   overhead earlier.\n\n3. **FP8 MFU can look misleadingly low**: compare absolute throughput as well as\n   MFU when switching precision modes.\n\n4. **CUDA graphs and recompute interact**: TE-scoped graphs are usually paired\n   with selective recompute, not blanket full recompute.\n\n5. **Parallel Folding is not optional at large scale**: once attention and expert\n   layers want clearly different layouts, a single shared TP or EP plan becomes\n   a tax on both.\n","# MoE Training Optimization Workflow\n\nStable docs: @docs\u002Ftraining\u002Fmoe-optimization.md\nCard: @skills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002Fcard.yaml\nSource: [Scalable Training of MoE Models with Megatron Core](https:\u002F\u002Farxiv.org\u002Fabs\u002F2603.07685)\n\n## Quick Reference\n\nThink in terms of the paper's Three Walls:\n\n- memory wall\n- communication wall\n- compute and host-overhead wall\n\nMoE tuning is iterative. Fixing one wall usually exposes the next one, so the\nbest workflow is: fit first, scale second, profile third, then retune.\n\n## First Answer Checklist\n\nFor MoE optimization workflow prompts, present the response in this order:\n\n1. **Fit**: make the model memory-feasible first. Use the smallest model\n   parallelism that fits, prefer selective recompute before full recompute, add\n   offloading only after recompute and parallelism are insufficient, and use\n   `--fake-init-process-group` to sanity-check large layouts.\n2. **Scale**: maximize DP after the model fits, keep hot communication inside\n   the fastest interconnect, use PP plus VPP for multi-node scaling, prefer EP\n   over extra TP for expert layers, and add CP when long context makes attention\n   memory dominant.\n3. **Profile**: identify the dominant wall: memory, communication, host\n   overhead, or compute.\n4. **Retune**: change dispatcher, overlap, FP8 mode, CUDA graphs, or recompute\n   based on the profiled bottleneck.\n5. Include the exact Parallel Folding meshes: `Attention: TP x CP x DP x PP`\n   and `MoE: ETP x EP x EDP x PP`.\n6. Include the default mappings: `alltoall` for safe bring-up,\n   `flex` + `deepep` for H100\u002FB200-style systems, `flex` + `hybridep` for\n   GB200\u002FGB300\u002FNVL72 systems, Hopper to FP8 blockwise, Blackwell to MXFP8, and\n   dropless MoE TE-scoped CUDA graphs over `attn`, `moe_router`, and\n   `moe_preprocess`.\n\n## Phase 1: Make The Run Memory-Feasible\n\nStart with a configuration that fits reliably before chasing throughput.\n\nRecommended order:\n\n1. Use the smallest amount of model parallelism that still fits.\n2. Turn on selective recompute before falling back to full recompute.\n3. Add offloading only when recompute and parallelism are still insufficient.\n4. Use `--fake-init-process-group` to sanity-check large parallel layouts on a\n   single GPU before burning cluster time.\n\n### Recompute guidance\n\nPrefer selective recompute for MoE runs:\n\n- good first choices: `layernorm`, `core_attn`, `moe_act`, `mlp`, or\n  model-specific modules (`shared_experts`, `mla_up_proj`)\n- use full recompute only when the run still does not fit\n- revisit recompute after enabling CUDA graphs, because some graph scopes and\n  full recompute paths do not mix well\n\nAs a rule of thumb, fine-grained recompute often recovers most of the needed\nmemory while keeping throughput much closer to the non-recompute baseline than\nfull-layer recompute does.\n\n## Phase 2: Choose Parallelism For Scale\n\nPriority order:\n\n1. Maximize DP once the model fits.\n2. Keep the hot communication path inside the fast interconnect when possible.\n3. Use PP, plus VPP if needed, for multi-node scaling.\n4. Prefer EP over extra TP for expert layers.\n5. Add CP for long context once sequence length makes attention memory dominant.\n\n### Parallel Folding\n\nParallel Folding decouples attention and MoE parallelism so you do not have to\npick a single compromise layout:\n\n```text\nAttention: TP × CP × DP × PP\nMoE:       ETP × EP × EDP × PP\n```\n\nKey knobs:\n\n- `--expert-model-parallel-size`\n- `--expert-tensor-parallel-size`\n\nUse it when attention prefers some TP or CP, but expert layers benefit from a\nlarger EP degree than the dense layers can tolerate.\n\n## Phase 3: Profile The Dominant Bottleneck\n\n| Bottleneck | What it looks like | Primary fixes |\n|---|---|---|\n| Memory | Run fits only with aggressive full recompute or OOMs during warmup | selective recompute, FP8, offloading, better PP layout |\n| Communication | Nsight shows large all-to-all or collective blocks | DeepEP or HybridEP, EP overlap, DP\u002FTP overlap, better PP layout |\n| Host overhead | GPU gaps, launch-bound traces, Python overhead | CUDA graphs, `--manual-gc`, higher MBS, CPU affinity tuning |\n| Compute | Low SM utilization after comm and host issues are addressed | grouped GEMM, fusion work, FP8, dispatcher-specific kernel tuning |\n\n## Dispatcher And Overlap Guidance\n\nUse dispatcher choice as a bottleneck fix, not as the first tuning knob.\n\n- `moe_token_dispatcher_type=\"alltoall\"`: safest bring-up path, fine for\n  smaller EP sizes\n- `moe_token_dispatcher_type=\"flex\"` + `moe_flex_dispatcher_backend=\"deepep\"`:\n  strong default for H100 and B200 style deployments\n- `moe_token_dispatcher_type=\"flex\"` + `moe_flex_dispatcher_backend=\"hybridep\"`:\n  strongest starting point on GB200 or GB300 NVL72 systems\n\nIf the all-to-all path is visible in profiles, combine dispatcher tuning with:\n\n- `--overlap-moe-expert-parallel-comm`\n- `--overlap-grad-reduce`\n- `--tp-comm-overlap`\n\n## FP8 Recipe Quick Decision\n\n| Platform | Recommended starting recipe |\n|---|---|\n| Hopper | FP8 blockwise |\n| Blackwell | MXFP8 |\n| Blackwell, speed-first exploration | NVFP4 after the BF16 or FP8 path is stable |\n\nKeep the router in FP32. The largest wins usually come from expert GEMMs and\nother heavy matrix math, not from trying to quantize every small MoE component.\n\n## CUDA Graphs For MoE\n\nFor dropless MoE, start with partial TE-scoped graphs:\n\n- `attn`\n- `moe_router`\n- `moe_preprocess`\n\nThat path usually gives a meaningful step-time win while keeping the dynamic\nexpert work outside the graph. Expect a moderate speedup when launch overhead is\nvisible, but budget several extra GB of memory and verify that shapes remain\nstatic.\n\nUse full-iteration graphs only for graph-friendly workloads such as drop-and-pad\nor tightly controlled static-shape experiments.\n\nRelated references:\n\n- @skills\u002Fnemo-mbridge-perf-cuda-graphs\u002FSKILL.md\n- @docs\u002Ftraining\u002Fcuda-graphs.md\n- @docs\u002Ftraining\u002Factivation-recomputation.md\n\n## Pitfalls\n\n1. **Do not optimize in the wrong order**: fitting the model and selecting sane\n   parallelism matter more than micro-optimizations.\n\n2. **Platform changes the limiting wall**: H100-class runs often feel more\n   communication-bound, while GB200 or GB300 runs often expose CPU or launch\n   overhead earlier.\n\n3. **FP8 MFU can look misleadingly low**: compare absolute throughput as well as\n   MFU when switching precision modes.\n\n4. **CUDA graphs and recompute interact**: TE-scoped graphs are usually paired\n   with selective recompute, not blanket full recompute.\n\n5. **Parallel Folding is not optional at large scale**: once attention and expert\n   layers want clearly different layouts, a single shared TP or EP plan becomes\n   a tax on both.\n",{"name":5,"license":15,"version":24,"category":25,"description":7,"when_to_use":26},"1.0.0","development-code","Full MoE throughput tuning sweep, or diagnosing a MoE throughput regression after a commit or config change; 'optimize MoE throughput', 'MoE perf tuning', 'Three Walls', 'memory wall', 'communication wall', 'compute wall'.","main","d591030ef9fb1bbcebed3454aa5c2dcb8d608f69","skills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive","https:\u002F\u002Fai-agent.yyc3.vip\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-13 22:26:14",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add YYC-Cube\u002FYYC3-AI-Agent-Archive --skill nemo-mbridge-perf-moe-optimization-workflow",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-AI-Agent-Archive --skill nemo-mbridge-perf-moe-optimization-workflow",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-AI-Agent-Archive --skill nemo-mbridge-perf-moe-optimization-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002FSKILL.md",true,[49,55,59,63,67],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"BENCHMARK.md","REFERENCE","参考文档",4429,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002FBENCHMARK.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"card.yaml",5140,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002Fcard.yaml",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"evals\u002Fevals.json",1840,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002Fevals\u002Fevals.json",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"skill-card.md",3900,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002Fskill-card.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"skill.oms.sig","OTHER","其他",4841,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002Fskill.oms.sig",[74,82,89,96,103,111],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7BTB92RE8MT5YE706QBNDTQ","yingmi-skill","当用户需要查询基金、策略、公告、财经资讯，做资产配置、组合诊断、风险回测、现金流分析，或生成图表、PDF 时，优先使用本 Skill 获取真实数据与可执行能力。","MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fyingmi-skill\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7BT7ZYR091HPJYEFNWVTEJJ","web-access","所有联网操作必须通过此 skill 处理，包括：搜索、网页抓取、登录后操作、网络交互等。","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fweb-access\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7BT4NKS0DNP8A53M1BGGZR2","tencentmap-map-assistant","腾讯位置服务·地图助手 Skill，一句自然语言调用腾讯地图全套能力，无需开发者账号、开箱即用。提供 AI 旅游攻略、地点搜索（含评分\u002F人均\u002F营业时间）、关键词提示、路线规划（驾车\u002F步行\u002F公交\u002F骑行）、地址解析与逆解析、行政区划、IP 定位、距离计算、天气查询，并可将行程或多 POI 渲染成网页地图。涉及找地点、规划路线、旅游行程、查天气、坐标转换等出行场景时使用。","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Ftencentmap-map-assistant\u002FSKILL.md",[],[],{"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":78,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7BSWKV1T5XYYRGV4W4JP88C","skill-scanner","Scan any agent skill for security risks before you install or use it. Powered by Tencent Zhuque Lab A.I.G (AI-Infra-Guard). 100% local static analysis — no file contents or credentials leave your device. Compatible with CodeBuddy, Cursor, Windsurf, Claude Code, OpenClaw and more. Triggers on: 这个 skill 安全吗, skill 安全扫描, 检查 skill 安全, audit skill, scan skill, check skill safety, analyze skill, inspect skill, verify skill, skill security, skill supply chain. Do NOT trigger for general agent usage, full system health checks, project debugging, or normal development.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fskill-scanner\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7BSWGTCFW7F123S4BM4XY6W","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends agent capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7BSVV4DH8JK2ZMQSCW25VCD","shader-dev","Comprehensive GLSL shader techniques for creating stunning visual effects — ray marching, SDF modeling, fluid simulation, particle systems, procedural generation, lighting, post-processing, and more.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fshader-dev\u002FSKILL.md",[],[]]