[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78D0H6HC44PAJKA3PDBRRHN":3,"skill-same:01M78D0H6HC44PAJKA3PDBRRHN":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":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M78D0H6HC44PAJKA3PDBRRHN","nemo-mbridge-perf-moe-hardware-configs",null,"Representative MoE training playbooks by hardware platform and model family. Summarizes rounded throughput bands, parallelism patterns, and common tuning stacks.","Solizardking\u002Fskillhub-main","Solizardking","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F108096810?v=4","01M786KDB10AYV042N0F9BD5B5","Clawd","01M786NYYXSZK1D05WM8JQPC48",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-moe-hardware-configs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nemo-mbridge-perf-moe-hardware-configs\ndescription: Representative MoE training playbooks by hardware platform and model family. Summarizes rounded throughput bands, parallelism patterns, and common tuning stacks.\nlicense: Apache-2.0\nwhen_to_use: Hardware-specific MoE playbooks or throughput estimates; 'MoE on H100', 'GB200 config', 'expected throughput', 'MoE hardware playbook', 'parallelism for B200'.\n---\n\n# MoE Hardware Configuration Reference\n\nStable docs: @docs\u002Ftraining\u002Fmoe-optimization.md\nCard: @skills\u002Fnemo-mbridge-perf-moe-hardware-configs\u002Fcard.yaml\n\n## Quick Platform Playbook\n\n| Platform | Typical MoE strategy | What usually matters most |\n|---|---|---|\n| H100 | DeepEP + stronger PP + moderate TP | communication overlap and PP efficiency |\n| B200 | DeepEP + MXFP8 + careful PP layout | container quality and tuned comm settings |\n| GB200 | HybridEP + partial CUDA graphs + CPU cleanup | host overhead, topology-aware dispatch, memory headroom |\n| GB300 | HybridEP + newer FP8 and kernel stack | same GB200 playbook, usually with a higher ceiling |\n\n## First Answer Checklist\n\nFor hardware playbook questions, answer from these canonical rows before adding\nthroughput caveats:\n\n| Workload | Hardware | Dispatcher | Layout |\n|---|---|---|---|\n| DSV3 | H100 | DeepEP | TP=2, EP=64, PP=8, VPP=4 |\n| DSV3 | GB200\u002FGB300 | HybridEP | TP=1, EP=64, PP=4, VPP=4 |\n| Qwen3 235B | H100 | DeepEP | TP=2, EP=32, PP=8, VPP=4 |\n| Qwen3 235B | GB200 | HybridEP | TP=1 or 2, EP=32-64, PP=4, VPP=unspecified |\n\nFor Qwen3 235B on GB200, explicitly say `VPP=unspecified`; do not invent or\nextrapolate `VPP=12` unless a measured row provides it. Include TE-scoped CUDA\ngraph scopes (`attn`, `moe_router`, `moe_preprocess`),\n`CUDA_DEVICE_MAX_CONNECTIONS` selection,\n`PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True`, `NCCL_GRAPH_REGISTER=0`,\nGB200\u002FGB300 CPU-side tuning, and the warning not to cargo-cult tracker rows.\n\n## Rounded Performance Bands\n\nThese are intentionally rounded so the document stays durable as the tracker\nmoves. Treat them as planning ranges, not exact promises.\n\n| Workload family | Hardware | Typical band | Representative shape |\n|---|---|---|---|\n| DSV3, large-scale | H100 | low-to-mid hundreds TFLOPS\u002FGPU, high-teens MFU | TP2, EP64, PP8, DeepEP |\n| DSV3, large-scale | B200 | high-hundreds TFLOPS\u002FGPU, mid-teens MFU | TP1, EP32, PP8, DeepEP |\n| DSV3, large-scale | GB200 | around 1K TFLOPS\u002FGPU, low-20s MFU | TP1, EP64, PP4, HybridEP |\n| DSV3, large-scale | GB300 | above the GB200 band, often mid-20s MFU | TP1, EP64, PP4, HybridEP |\n| Qwen3 235B | H100 | low-300s TFLOPS\u002FGPU, around 30% MFU | TP2, EP32, PP8, DeepEP |\n| Qwen3 235B | GB200 | high-hundreds TFLOPS\u002FGPU in tuned runs | TP1 or TP2, EP32-64, PP4, HybridEP |\n| Qwen3 30B | H100 | low-200s TFLOPS\u002FGPU | TP1, EP8, PP1, DeepEP |\n| Qwen3-Next 80B | GB200 | low-300s TFLOPS\u002FGPU in BF16-class runs | TP1, EP32, PP2, HybridEP |\n\n## Representative Config Families\n\n### DSV3 on H100\n\n```text\nDispatcher: DeepEP\nTP=2  EP=64  PP=8  VPP=4\nRouting: force balance\nRecompute: light-to-moderate selective recompute\nPriority: overlap communication and keep PP efficient\n```\n\n### DSV3 on B200\n\n```text\nDispatcher: DeepEP\nTP=1  EP=32  PP=8  VPP=2 or similar\nPrecision: MXFP8-class\nRecompute: selective recompute around MLA up-projection and MLP-side modules\nPriority: container quality, PP layout, and DeepEP SMS tuning\n```\n\n### DSV3 on GB200 or GB300\n\n```text\nDispatcher: HybridEP\nTP=1  EP=64  PP=4  VPP=4\nPrecision: MXFP8-class\nCUDA Graph: attn + moe_router + moe_preprocess\nPriority: HybridEP, CPU optimization, and graph-friendly static shapes\n```\n\n### Qwen3 235B on H100\n\n```text\nDispatcher: DeepEP\nTP=2  EP=32  PP=8  VPP=4\nRecompute: norm and activation-side selective recompute\nPriority: communication overlap and router-path cleanup\n```\n\n### Qwen3 235B on GB200\n\n```text\nDispatcher: HybridEP\nTP=1 or 2  EP=32 to 64  PP=4  VPP=unspecified unless measured\nCUDA Graph: attn + moe_router + moe_preprocess\nRecompute: moe_act, mlp, or norm depending on memory pressure\nPriority: balance throughput against memory headroom\n```\n\n### Qwen3-Next 80B on GB200\n\n```text\nDispatcher: HybridEP\nTP=1  EP=32  PP=2  VPP around 4\nCUDA Graph: attn + moe_router + moe_preprocess\nPriority: pipeline layout and grouped GEMM quality\n```\n\n## Cross-Cutting Patterns\n\n### PP layout\n\n- `E` = embedding\n- `t` = transformer\n- `m` = MTP\n- `L` = loss\n- `|` = stage boundary\n\nThe biggest platform difference is usually not just the dispatcher. It is the\ncombination of dispatcher, PP shape, and whether VPP keeps each stage balanced.\n\n### Recompute strategy\n\n| Memory pressure | Starting point |\n|---|---|\n| low | none or a very narrow selective set |\n| moderate | `moe_act`, `mlp`, `norm`, or similar selective modules |\n| high | model-specific up-projection plus selective MoE and MLP modules |\n| extreme or long-context | full recompute only if the selective path still does not fit |\n\n### Environment variables\n\n```bash\nCUDA_DEVICE_MAX_CONNECTIONS=1\nCUDA_DEVICE_MAX_CONNECTIONS=32   # common when EP overlap and CUDA graphs are combined\nPYTORCH_CUDA_ALLOC_CONF=expandable_segments:True\nNCCL_GRAPH_REGISTER=0\n```\n\n### CPU-side tuning\n\nOn GB200 and GB300, CPU affinity and general host-overhead cleanup can move the\nneedle almost as much as a dispatcher swap. Treat them as first-class tuning\nwork, not as afterthoughts.\n\n## Pitfalls\n\n1. **Do not cargo-cult a tracker row**: the winning config usually depends on\n   routing mode, container, and PP layout as much as on hardware name.\n\n2. **Container quality matters**: large regressions can come from the software\n   stack rather than the model recipe.\n\n3. **VPP must be intentional**: a bad VPP split can erase the gain from a better\n   dispatcher.\n\n4. **Compare absolute throughput, not only MFU**: MFU can mislead when switching\n   between BF16, FP8, and other precision modes.\n\n5. **Force-balance routing is the safer benchmark default**: keep routing mode\n   fixed when comparing hardware or dispatcher stacks.\n","# MoE Hardware Configuration Reference\n\nStable docs: @docs\u002Ftraining\u002Fmoe-optimization.md\nCard: @skills\u002Fnemo-mbridge-perf-moe-hardware-configs\u002Fcard.yaml\n\n## Quick Platform Playbook\n\n| Platform | Typical MoE strategy | What usually matters most |\n|---|---|---|\n| H100 | DeepEP + stronger PP + moderate TP | communication overlap and PP efficiency |\n| B200 | DeepEP + MXFP8 + careful PP layout | container quality and tuned comm settings |\n| GB200 | HybridEP + partial CUDA graphs + CPU cleanup | host overhead, topology-aware dispatch, memory headroom |\n| GB300 | HybridEP + newer FP8 and kernel stack | same GB200 playbook, usually with a higher ceiling |\n\n## First Answer Checklist\n\nFor hardware playbook questions, answer from these canonical rows before adding\nthroughput caveats:\n\n| Workload | Hardware | Dispatcher | Layout |\n|---|---|---|---|\n| DSV3 | H100 | DeepEP | TP=2, EP=64, PP=8, VPP=4 |\n| DSV3 | GB200\u002FGB300 | HybridEP | TP=1, EP=64, PP=4, VPP=4 |\n| Qwen3 235B | H100 | DeepEP | TP=2, EP=32, PP=8, VPP=4 |\n| Qwen3 235B | GB200 | HybridEP | TP=1 or 2, EP=32-64, PP=4, VPP=unspecified |\n\nFor Qwen3 235B on GB200, explicitly say `VPP=unspecified`; do not invent or\nextrapolate `VPP=12` unless a measured row provides it. Include TE-scoped CUDA\ngraph scopes (`attn`, `moe_router`, `moe_preprocess`),\n`CUDA_DEVICE_MAX_CONNECTIONS` selection,\n`PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True`, `NCCL_GRAPH_REGISTER=0`,\nGB200\u002FGB300 CPU-side tuning, and the warning not to cargo-cult tracker rows.\n\n## Rounded Performance Bands\n\nThese are intentionally rounded so the document stays durable as the tracker\nmoves. Treat them as planning ranges, not exact promises.\n\n| Workload family | Hardware | Typical band | Representative shape |\n|---|---|---|---|\n| DSV3, large-scale | H100 | low-to-mid hundreds TFLOPS\u002FGPU, high-teens MFU | TP2, EP64, PP8, DeepEP |\n| DSV3, large-scale | B200 | high-hundreds TFLOPS\u002FGPU, mid-teens MFU | TP1, EP32, PP8, DeepEP |\n| DSV3, large-scale | GB200 | around 1K TFLOPS\u002FGPU, low-20s MFU | TP1, EP64, PP4, HybridEP |\n| DSV3, large-scale | GB300 | above the GB200 band, often mid-20s MFU | TP1, EP64, PP4, HybridEP |\n| Qwen3 235B | H100 | low-300s TFLOPS\u002FGPU, around 30% MFU | TP2, EP32, PP8, DeepEP |\n| Qwen3 235B | GB200 | high-hundreds TFLOPS\u002FGPU in tuned runs | TP1 or TP2, EP32-64, PP4, HybridEP |\n| Qwen3 30B | H100 | low-200s TFLOPS\u002FGPU | TP1, EP8, PP1, DeepEP |\n| Qwen3-Next 80B | GB200 | low-300s TFLOPS\u002FGPU in BF16-class runs | TP1, EP32, PP2, HybridEP |\n\n## Representative Config Families\n\n### DSV3 on H100\n\n```text\nDispatcher: DeepEP\nTP=2  EP=64  PP=8  VPP=4\nRouting: force balance\nRecompute: light-to-moderate selective recompute\nPriority: overlap communication and keep PP efficient\n```\n\n### DSV3 on B200\n\n```text\nDispatcher: DeepEP\nTP=1  EP=32  PP=8  VPP=2 or similar\nPrecision: MXFP8-class\nRecompute: selective recompute around MLA up-projection and MLP-side modules\nPriority: container quality, PP layout, and DeepEP SMS tuning\n```\n\n### DSV3 on GB200 or GB300\n\n```text\nDispatcher: HybridEP\nTP=1  EP=64  PP=4  VPP=4\nPrecision: MXFP8-class\nCUDA Graph: attn + moe_router + moe_preprocess\nPriority: HybridEP, CPU optimization, and graph-friendly static shapes\n```\n\n### Qwen3 235B on H100\n\n```text\nDispatcher: DeepEP\nTP=2  EP=32  PP=8  VPP=4\nRecompute: norm and activation-side selective recompute\nPriority: communication overlap and router-path cleanup\n```\n\n### Qwen3 235B on GB200\n\n```text\nDispatcher: HybridEP\nTP=1 or 2  EP=32 to 64  PP=4  VPP=unspecified unless measured\nCUDA Graph: attn + moe_router + moe_preprocess\nRecompute: moe_act, mlp, or norm depending on memory pressure\nPriority: balance throughput against memory headroom\n```\n\n### Qwen3-Next 80B on GB200\n\n```text\nDispatcher: HybridEP\nTP=1  EP=32  PP=2  VPP around 4\nCUDA Graph: attn + moe_router + moe_preprocess\nPriority: pipeline layout and grouped GEMM quality\n```\n\n## Cross-Cutting Patterns\n\n### PP layout\n\n- `E` = embedding\n- `t` = transformer\n- `m` = MTP\n- `L` = loss\n- `|` = stage boundary\n\nThe biggest platform difference is usually not just the dispatcher. It is the\ncombination of dispatcher, PP shape, and whether VPP keeps each stage balanced.\n\n### Recompute strategy\n\n| Memory pressure | Starting point |\n|---|---|\n| low | none or a very narrow selective set |\n| moderate | `moe_act`, `mlp`, `norm`, or similar selective modules |\n| high | model-specific up-projection plus selective MoE and MLP modules |\n| extreme or long-context | full recompute only if the selective path still does not fit |\n\n### Environment variables\n\n```bash\nCUDA_DEVICE_MAX_CONNECTIONS=1\nCUDA_DEVICE_MAX_CONNECTIONS=32   # common when EP overlap and CUDA graphs are combined\nPYTORCH_CUDA_ALLOC_CONF=expandable_segments:True\nNCCL_GRAPH_REGISTER=0\n```\n\n### CPU-side tuning\n\nOn GB200 and GB300, CPU affinity and general host-overhead cleanup can move the\nneedle almost as much as a dispatcher swap. Treat them as first-class tuning\nwork, not as afterthoughts.\n\n## Pitfalls\n\n1. **Do not cargo-cult a tracker row**: the winning config usually depends on\n   routing mode, container, and PP layout as much as on hardware name.\n\n2. **Container quality matters**: large regressions can come from the software\n   stack rather than the model recipe.\n\n3. **VPP must be intentional**: a bad VPP split can erase the gain from a better\n   dispatcher.\n\n4. **Compare absolute throughput, not only MFU**: MFU can mislead when switching\n   between BF16, FP8, and other precision modes.\n\n5. **Force-balance routing is the safer benchmark default**: keep routing mode\n   fixed when comparing hardware or dispatcher stacks.\n",{"name":5,"license":15,"description":7,"when_to_use":24},"Hardware-specific MoE playbooks or throughput estimates; 'MoE on H100', 'GB200 config', 'expected throughput', 'MoE hardware playbook', 'parallelism for B200'.","main","be3de0244dc1a57e323d8160787ebb40fb64930e","skills\u002Fnvidia\u002Fnemo-mbridge-perf-moe-hardware-configs","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main","https:\u002F\u002Fskills.x402.wtf","https:\u002F\u002Fgithub.com\u002FSolizardking","https:\u002F\u002Fmusebook.trade","Got a mile high and never came down","2026-10-08 23:20:13",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Solizardking\u002Fskillhub-main --skill nemo-mbridge-perf-moe-hardware-configs",{"tool":40,"command":41},"bunx","bunx skills add Solizardking\u002Fskillhub-main --skill nemo-mbridge-perf-moe-hardware-configs",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Solizardking\u002Fskillhub-main --skill nemo-mbridge-perf-moe-hardware-configs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-moe-hardware-configs\u002FSKILL.md",true,[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"BENCHMARK.md","REFERENCE","参考文档",4338,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-moe-hardware-configs\u002FBENCHMARK.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"card.yaml",5298,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-moe-hardware-configs\u002Fcard.yaml",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"evals\u002Fevals.json",1984,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-moe-hardware-configs\u002Fevals\u002Fevals.json",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"skill-card.md",3854,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-moe-hardware-configs\u002Fskill-card.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"skill.oms.sig","OTHER","其他",4829,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-moe-hardware-configs\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},"01M78E0TGCAMNPS207BA3G07S7","zkrouter","Self-hosted OpenAI-compatible LLM router — smart tier-based routing, ZK-stamped routing decisions, mode overrides, free OpenRouter at install via the Birth bot. Save 60-80% on inference costs by routing to the cheapest capable model across 12+ OpenRouter models.","MIT","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzkrouter\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},"01M78E0R1Z8BDT6EDTHY17MTNB","zk","For custom ZK Solana programs and privacy-preserving applications to prevent double spending. Guide to integrate rent-free nullifier PDAs for double-spend prevention.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk\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},"01M78E0P3ZTZ1YWF8MD5MM23QE","zk-omni-messaging","Zero-knowledge omnichain messaging between Robinhood Chain and Solana using CheshireZkOmniMessenger (msgType 4) with nullifier anti-replay and the zk-omni-relayer service.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk-omni-messaging\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},"01M78E0JXZ2PNB1896VXAGDBWD","zerion-wallet-data","Use when the user asks to check a wallet's portfolio, token balances, DeFi positions, PnL, transaction history, or NFTs. Provides interpreted on-chain data across 40+ EVM chains and Solana via x402 pay-per-request or API key — no raw RPC decoding needed.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzerion-wallet-data\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},"01M78E0G14FH9GRRTQYMKD5E59","youtube-clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\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},"01M78E0C2ZYA99CFFDNB7ZMK5S","yield-optimization","Multi-chain yield optimization via yield.xyz (StakeKit). Discover 2,988+ yield opportunities across 75+ blockchains, build deposit\u002Fwithdrawal transactions with shell scripts, and sign them with a MoonPay wallet. Use when the user wants to earn yield, find the best lending or staking rate, enter\u002Fexit a position, or check portfolio balances.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyield-optimization\u002FSKILL.md",[],[]]