[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78SN18DPTF29HK5PXSZP134":3,"skill-same:01M78SN18DPTF29HK5PXSZP134":72},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M78SN18DPTF29HK5PXSZP134","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.","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\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.\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,"description":7,"when_to_use":24},"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","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fnemo-mbridge-perf-moe-optimization-workflow",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill nemo-mbridge-perf-moe-optimization-workflow",{"tool":40,"command":41},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill nemo-mbridge-perf-moe-optimization-workflow",{"tool":43,"command":44},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill nemo-mbridge-perf-moe-optimization-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002FSKILL.md",true,[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"BENCHMARK.md","REFERENCE","参考文档",4429,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002FBENCHMARK.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"card.yaml",5140,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002Fcard.yaml",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"evals\u002Fevals.json",1840,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002Fevals\u002Fevals.json",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"skill-card.md",3900,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002Fskill-card.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"skill.oms.sig","OTHER","其他",4841,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-mbridge-perf-moe-optimization-workflow\u002Fskill.oms.sig",[73,81,88,95,102,110],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]