[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSKD3ZG4RN6844QZDEJS51":3,"skill-same:01M7CSKD3ZG4RN6844QZDEJS51":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":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CSKD3ZG4RN6844QZDEJS51","nemo-mbridge-perf-activation-recompute",null,"Validate and use selective and full activation recompute in Megatron Bridge to reduce GPU memory usage at the cost of extra compute.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fnemo-mbridge-perf-activation-recompute\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nemo-mbridge-perf-activation-recompute\ndescription: Validate and use selective and full activation recompute in Megatron Bridge to reduce GPU memory usage at the cost of extra compute.\nlicense: Apache-2.0\nwhen_to_use: Reducing GPU memory via activation recompute, or investigating a commit that changed recompute settings and caused OOM or a regression; 'recompute_granularity', 'recompute_num_layers', 'recompute_modules', 'recompute_method', 'selective recompute', 'full recompute', 'activation memory OOM'.\n---\n\n# Activation Recompute\n\nStable docs: @docs\u002Ftraining\u002Factivation-recomputation.md\nCard: @skills\u002Fnemo-mbridge-perf-activation-recompute\u002Fcard.yaml\n\n## Answer Checklist\n\nFor OOM or CUDA graph questions, lead with this exact sequence:\n\n1. First try `PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True`; many\n   borderline failures are allocator fragmentation, not activation capacity.\n2. Prefer selective recompute before full-layer recompute:\n   `recompute_granularity=\"selective\"` with `recompute_modules=[\"core_attn\"]`.\n3. If still borderline, optionally add `\"layernorm\"`; use `\"mlp\"` only as a\n   last resort because it has a large compute cost on wide dense FFNs.\n4. Use full-layer recompute only after selective recompute fails to fit, and\n   always name the required fields: `recompute_granularity=\"full\"`,\n   `recompute_method`, and `recompute_num_layers`.\n5. If FP8 or TE-scoped CUDA graphs are enabled, call out the assertion risk:\n   full-layer recompute is incompatible with TE scopes such as `attn`, `mlp`,\n   and `moe_router`. Valid fixes are selective recompute, `cuda_graph_impl=\"none\"`,\n   or `cuda_graph_impl=\"local\"` with `cuda_graph_scope=\"full_iteration\"`.\n\n## What It Is\n\nActivation recompute trades GPU compute for memory by discarding intermediate\nactivations during the forward pass and recomputing them during backward.\nMegatron Bridge supports two granularities:\n\n| Granularity | What you specify | What gets recomputed | Memory savings | Compute cost |\n|---|---|---|---|---|\n| `selective` | `recompute_modules` list (e.g. `core_attn`, `mlp`) | specific submodules within each layer | moderate (module-dependent) | low to high |\n| `full` | `recompute_num_layers` + `recompute_method` | entire transformer layers (N layers) | strongest | highest |\n\nNote: MCore names these \"selective\" (submodule-level) vs \"full\" (layer-level).\n\"Full\" means recomputing full layers, not the full model — you still choose\nhow many layers via `recompute_num_layers`.\n\n## Quick Decision\n\n1. **Set `PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True` first** — most\n   borderline OOMs are caused by memory fragmentation, not capacity. This\n   fixes it at zero cost. See @skills\u002Fnemo-mbridge-perf-memory-tuning\u002FSKILL.md.\n2. Start with `recompute_granularity=selective`, `recompute_modules=[core_attn]`\n   (often already the default in recipes).\n3. Add `layernorm` to recompute modules — nearly free compute-wise but saves\n   negligible memory. Only helps in extremely borderline cases.\n4. Add `mlp` as a last resort — saves ~3 GB but costs ~16% GPU utilization on\n   large dense models (Llama3 70B).\n5. Use `recompute_granularity=full` only when selective recompute still does\n   not fit.\n\nCPU offloading (`cpu_offloading=True`) is an alternative that avoids recompute\ncost entirely, but it is **incompatible with PP > 1**.\n\n## Enablement\n\n### Selective recompute\n\n```python\ncfg.model.recompute_granularity = \"selective\"\ncfg.model.recompute_modules = [\"core_attn\"]  # add \"layernorm\", \"mlp\", or other valid modules as needed\n```\n\n### Full-layer recompute\n\n```python\ncfg.model.recompute_granularity = \"full\"\ncfg.model.recompute_method = \"uniform\"\ncfg.model.recompute_num_layers = 4\n```\n\n### Available recompute_modules\n\n| Module | What it recomputes | Compute cost | Memory savings |\n|---|---|---|---|\n| `core_attn` | attention softmax\u002Fdropout\u002FQKV dot product | low (Flash Attention already recomputes internally) | moderate |\n| `layernorm` | layer normalization | negligible (~0%) | negligible |\n| `mlp` | full FFN block | high (~16% on Llama3 70B, hidden=28672) | ~3 GB |\n| `moe` | MoE expert dispatch | varies | varies |\n| `moe_act` | MoE activation functions | low | small |\n| `shared_experts` | shared expert layers | moderate | moderate |\n| `mla_up_proj` | Multi-Latent Attention up projection | moderate | moderate |\n\n### Performance harness CLI\n\n```bash\npython scripts\u002Fperformance\u002Frun_performance_workload.py \\\n  --recompute_granularity selective \\\n  --recompute_modules core_attn layernorm \\\n  ...\n```\n\n## Compatibility and Constraints\n\n- `recompute_granularity=selective` requires a non-empty `recompute_modules` list\n- `recompute_granularity=full` requires `recompute_method` and `recompute_num_layers`\n- **Layer-level recompute (`recompute_granularity=\"full\"` +\n  `recompute_num_layers`) is incompatible with TE-scoped CUDA graphs.**\n  MCore calls this \"full\" granularity — the name refers to recomputing\n  full transformer layers, not the full model. Even though you're selecting\n  how many layers to recompute, MCore treats it differently from submodule\n  recompute. Any TE-scoped scope (`attn`, `mlp`, `moe_router`, etc.) will\n  assert. This commonly hits FP8 configs that enable TE-scoped graphs by\n  default (e.g. `LLAMA3_70B_SFT_CONFIG_H100_FP8_CS_V1` sets\n  `cuda_graph_impl=\"transformer_engine\"`, `cuda_graph_scope=\"mlp\"`). Options:\n  - use submodule recompute (`recompute_granularity=\"selective\"` +\n    `recompute_modules`) — compatible with TE-scoped graphs\n  - disable CUDA graphs (`cuda_graph_impl=\"none\"`) and use layer-level recompute\n  - switch to `cuda_graph_impl=\"local\"`, `cuda_graph_scope=\"full_iteration\"`\n- `distribute_saved_activations=True` cannot be combined with `sequence_parallel=True`\n- Combining `mlp` + `core_attn` recompute is slightly worse than `mlp` alone\n  due to double recompute overhead\n\n## Measured Results\n\nLlama3 70B SFT on 32x H100 80GB, FP8 (Current Scaling):\n- Baseline: TP=4, PP=4, VPP=5, DP=2, MBS=1, GBS=32, seq_len=4096\n- Golden GPU utilization: 709.93 TFLOP\u002Fs\u002FGPU\n- Regression threshold: 5%\n\n| Experiment | recompute_modules | TFLOP\u002Fs\u002FGPU | vs Golden | Peak Mem (GB) | Result |\n|---|---|---|---|---|---|\n| Baseline | [core_attn] | ~704 | -0.8% | 58.8 (OOM rank0) | OOM |\n| Exp 1 | [mlp] | 593.6 | -16.4% | 55.6 | Perf regression |\n| Exp 2 | [mlp, core_attn] | 586.8 | -17.3% | 55.6 | Perf regression |\n| Exp 3 | [core_attn, layernorm] | ~702 | -1.1% | 59.6 (OOM rank0) | OOM |\n\nKey takeaways:\n\n- `layernorm` recompute is nearly free compute-wise but saves negligible memory\n- `mlp` recompute saves ~3 GB peak but costs ~16% because the Llama3 70B FFN\n  (hidden=28672) is expensive to recompute\n- Combining `mlp` + `core_attn` is slightly worse than `mlp` alone\n- For this workload, the actual OOM fix was `PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True`\n  (memory fragmentation, not capacity). See @skills\u002Fnemo-mbridge-perf-memory-tuning\u002FSKILL.md.\n\n## Code Anchors\n\n### Recompute modules enum and selective checkpoint logic\n\n```python\n# 3rdparty\u002FMegatron-LM\u002Fmegatron\u002Fcore\u002Ftransformer\u002Ftransformer_block.py\n# _checkpointed_forward() applies selective recompute based on recompute_modules\n```\n\n### Recompute config validation\n\n```python\n# 3rdparty\u002FMegatron-LM\u002Fmegatron\u002Fcore\u002Ftransformer\u002Ftransformer_config.py\n# Validates recompute_granularity, recompute_method, recompute_num_layers\n```\n\n### Llama3 recipe defaults\n\n```99:103:src\u002Fmegatron\u002Fbridge\u002Frecipes\u002Fllama\u002Fllama3.py\n    # Memory saving (recompute & offloading)\n    cfg.model.recompute_granularity = None\n    cfg.model.recompute_modules = None\n    cfg.model.fine_grained_activation_offloading = False\n    cfg.model.offload_modules = None\n```\n\n### Full recompute + CUDA graph assertion (MCore)\n\n```2001:2005:3rdparty\u002FMegatron-LM\u002Fmegatron\u002Fcore\u002Ftransformer\u002Ftransformer_config.py\n            if self.recompute_granularity:\n                if self.recompute_granularity != \"selective\":\n                    assert self.cuda_graph_scope == [\n                        CudaGraphScope.full_iteration\n                    ], \"full recompute is only supported with full iteration CUDA graph.\"\n```\n\n### CPU offloading PP incompatibility (MCore)\n\n```1303:1306:3rdparty\u002FMegatron-LM\u002Fmegatron\u002Fcore\u002Ftransformer\u002Ftransformer_config.py\n        if self.cpu_offloading and self.pipeline_model_parallel_size > 1:\n            raise ValueError(\n                \"Currently there is no support for Pipeline parallelism with CPU offloading\"\n            )\n```\n\n## Failure Diagnosis\n\n| Symptom | Cause | Confirm | Fix |\n|---|---|---|---|\n| >15% GPU utilization drop | mlp recompute on large FFN | check `recompute_modules` includes `mlp` | check `expandable_segments:True` is set; consider reducing MBS |\n| Still OOM after adding layernorm | layernorm activations are too small | compare peak memory before\u002Fafter | add mlp recompute or check `expandable_segments:True` |\n| `AssertionError: full recompute is only supported with full iteration CUDA graph` | layer-level recompute (`recompute_granularity=full` + `recompute_num_layers`) with TE-scoped graphs. FP8 CS configs default to `cuda_graph_impl=transformer_engine`, `scope=mlp`. | check `cuda_graph_impl` and `cuda_graph_scope` | use submodule recompute (`selective` + `recompute_modules`), or `cuda_graph_impl=none`, or `local` + `full_iteration` |\n| ValueError: PP + CPU offloading | `cpu_offloading=True` with `pipeline_model_parallel_size > 1` | check PP config | disable CPU offloading or set PP=1 |\n| mlp+core_attn worse than mlp alone | double recompute overhead | compare Exp 1 vs Exp 2 | use mlp alone |\n\n## Known Limitations\n\n- Per-module memory savings vary significantly by model architecture and hidden\n  dimension\n- No automatic module selection — users must choose which modules to recompute\n- `layernorm` recompute is almost never worth it as a standalone fix\n- CPU offloading (the zero-compute-cost alternative) is blocked when PP > 1\n\n## Verification\n\n```bash\nuv run python -m pytest \\\n  tests\u002Funit_tests\u002Ftraining\u002Ftest_config.py -k \"recompute\" -q\n```\n\nSuccess criteria:\n- Unit tests pass for recompute config validation\n- No assertion errors from config validation\n","# Activation Recompute\n\nStable docs: @docs\u002Ftraining\u002Factivation-recomputation.md\nCard: @skills\u002Fnemo-mbridge-perf-activation-recompute\u002Fcard.yaml\n\n## Answer Checklist\n\nFor OOM or CUDA graph questions, lead with this exact sequence:\n\n1. First try `PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True`; many\n   borderline failures are allocator fragmentation, not activation capacity.\n2. Prefer selective recompute before full-layer recompute:\n   `recompute_granularity=\"selective\"` with `recompute_modules=[\"core_attn\"]`.\n3. If still borderline, optionally add `\"layernorm\"`; use `\"mlp\"` only as a\n   last resort because it has a large compute cost on wide dense FFNs.\n4. Use full-layer recompute only after selective recompute fails to fit, and\n   always name the required fields: `recompute_granularity=\"full\"`,\n   `recompute_method`, and `recompute_num_layers`.\n5. If FP8 or TE-scoped CUDA graphs are enabled, call out the assertion risk:\n   full-layer recompute is incompatible with TE scopes such as `attn`, `mlp`,\n   and `moe_router`. Valid fixes are selective recompute, `cuda_graph_impl=\"none\"`,\n   or `cuda_graph_impl=\"local\"` with `cuda_graph_scope=\"full_iteration\"`.\n\n## What It Is\n\nActivation recompute trades GPU compute for memory by discarding intermediate\nactivations during the forward pass and recomputing them during backward.\nMegatron Bridge supports two granularities:\n\n| Granularity | What you specify | What gets recomputed | Memory savings | Compute cost |\n|---|---|---|---|---|\n| `selective` | `recompute_modules` list (e.g. `core_attn`, `mlp`) | specific submodules within each layer | moderate (module-dependent) | low to high |\n| `full` | `recompute_num_layers` + `recompute_method` | entire transformer layers (N layers) | strongest | highest |\n\nNote: MCore names these \"selective\" (submodule-level) vs \"full\" (layer-level).\n\"Full\" means recomputing full layers, not the full model — you still choose\nhow many layers via `recompute_num_layers`.\n\n## Quick Decision\n\n1. **Set `PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True` first** — most\n   borderline OOMs are caused by memory fragmentation, not capacity. This\n   fixes it at zero cost. See @skills\u002Fnemo-mbridge-perf-memory-tuning\u002FSKILL.md.\n2. Start with `recompute_granularity=selective`, `recompute_modules=[core_attn]`\n   (often already the default in recipes).\n3. Add `layernorm` to recompute modules — nearly free compute-wise but saves\n   negligible memory. Only helps in extremely borderline cases.\n4. Add `mlp` as a last resort — saves ~3 GB but costs ~16% GPU utilization on\n   large dense models (Llama3 70B).\n5. Use `recompute_granularity=full` only when selective recompute still does\n   not fit.\n\nCPU offloading (`cpu_offloading=True`) is an alternative that avoids recompute\ncost entirely, but it is **incompatible with PP > 1**.\n\n## Enablement\n\n### Selective recompute\n\n```python\ncfg.model.recompute_granularity = \"selective\"\ncfg.model.recompute_modules = [\"core_attn\"]  # add \"layernorm\", \"mlp\", or other valid modules as needed\n```\n\n### Full-layer recompute\n\n```python\ncfg.model.recompute_granularity = \"full\"\ncfg.model.recompute_method = \"uniform\"\ncfg.model.recompute_num_layers = 4\n```\n\n### Available recompute_modules\n\n| Module | What it recomputes | Compute cost | Memory savings |\n|---|---|---|---|\n| `core_attn` | attention softmax\u002Fdropout\u002FQKV dot product | low (Flash Attention already recomputes internally) | moderate |\n| `layernorm` | layer normalization | negligible (~0%) | negligible |\n| `mlp` | full FFN block | high (~16% on Llama3 70B, hidden=28672) | ~3 GB |\n| `moe` | MoE expert dispatch | varies | varies |\n| `moe_act` | MoE activation functions | low | small |\n| `shared_experts` | shared expert layers | moderate | moderate |\n| `mla_up_proj` | Multi-Latent Attention up projection | moderate | moderate |\n\n### Performance harness CLI\n\n```bash\npython scripts\u002Fperformance\u002Frun_performance_workload.py \\\n  --recompute_granularity selective \\\n  --recompute_modules core_attn layernorm \\\n  ...\n```\n\n## Compatibility and Constraints\n\n- `recompute_granularity=selective` requires a non-empty `recompute_modules` list\n- `recompute_granularity=full` requires `recompute_method` and `recompute_num_layers`\n- **Layer-level recompute (`recompute_granularity=\"full\"` +\n  `recompute_num_layers`) is incompatible with TE-scoped CUDA graphs.**\n  MCore calls this \"full\" granularity — the name refers to recomputing\n  full transformer layers, not the full model. Even though you're selecting\n  how many layers to recompute, MCore treats it differently from submodule\n  recompute. Any TE-scoped scope (`attn`, `mlp`, `moe_router`, etc.) will\n  assert. This commonly hits FP8 configs that enable TE-scoped graphs by\n  default (e.g. `LLAMA3_70B_SFT_CONFIG_H100_FP8_CS_V1` sets\n  `cuda_graph_impl=\"transformer_engine\"`, `cuda_graph_scope=\"mlp\"`). Options:\n  - use submodule recompute (`recompute_granularity=\"selective\"` +\n    `recompute_modules`) — compatible with TE-scoped graphs\n  - disable CUDA graphs (`cuda_graph_impl=\"none\"`) and use layer-level recompute\n  - switch to `cuda_graph_impl=\"local\"`, `cuda_graph_scope=\"full_iteration\"`\n- `distribute_saved_activations=True` cannot be combined with `sequence_parallel=True`\n- Combining `mlp` + `core_attn` recompute is slightly worse than `mlp` alone\n  due to double recompute overhead\n\n## Measured Results\n\nLlama3 70B SFT on 32x H100 80GB, FP8 (Current Scaling):\n- Baseline: TP=4, PP=4, VPP=5, DP=2, MBS=1, GBS=32, seq_len=4096\n- Golden GPU utilization: 709.93 TFLOP\u002Fs\u002FGPU\n- Regression threshold: 5%\n\n| Experiment | recompute_modules | TFLOP\u002Fs\u002FGPU | vs Golden | Peak Mem (GB) | Result |\n|---|---|---|---|---|---|\n| Baseline | [core_attn] | ~704 | -0.8% | 58.8 (OOM rank0) | OOM |\n| Exp 1 | [mlp] | 593.6 | -16.4% | 55.6 | Perf regression |\n| Exp 2 | [mlp, core_attn] | 586.8 | -17.3% | 55.6 | Perf regression |\n| Exp 3 | [core_attn, layernorm] | ~702 | -1.1% | 59.6 (OOM rank0) | OOM |\n\nKey takeaways:\n\n- `layernorm` recompute is nearly free compute-wise but saves negligible memory\n- `mlp` recompute saves ~3 GB peak but costs ~16% because the Llama3 70B FFN\n  (hidden=28672) is expensive to recompute\n- Combining `mlp` + `core_attn` is slightly worse than `mlp` alone\n- For this workload, the actual OOM fix was `PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True`\n  (memory fragmentation, not capacity). See @skills\u002Fnemo-mbridge-perf-memory-tuning\u002FSKILL.md.\n\n## Code Anchors\n\n### Recompute modules enum and selective checkpoint logic\n\n```python\n# 3rdparty\u002FMegatron-LM\u002Fmegatron\u002Fcore\u002Ftransformer\u002Ftransformer_block.py\n# _checkpointed_forward() applies selective recompute based on recompute_modules\n```\n\n### Recompute config validation\n\n```python\n# 3rdparty\u002FMegatron-LM\u002Fmegatron\u002Fcore\u002Ftransformer\u002Ftransformer_config.py\n# Validates recompute_granularity, recompute_method, recompute_num_layers\n```\n\n### Llama3 recipe defaults\n\n```99:103:src\u002Fmegatron\u002Fbridge\u002Frecipes\u002Fllama\u002Fllama3.py\n    # Memory saving (recompute & offloading)\n    cfg.model.recompute_granularity = None\n    cfg.model.recompute_modules = None\n    cfg.model.fine_grained_activation_offloading = False\n    cfg.model.offload_modules = None\n```\n\n### Full recompute + CUDA graph assertion (MCore)\n\n```2001:2005:3rdparty\u002FMegatron-LM\u002Fmegatron\u002Fcore\u002Ftransformer\u002Ftransformer_config.py\n            if self.recompute_granularity:\n                if self.recompute_granularity != \"selective\":\n                    assert self.cuda_graph_scope == [\n                        CudaGraphScope.full_iteration\n                    ], \"full recompute is only supported with full iteration CUDA graph.\"\n```\n\n### CPU offloading PP incompatibility (MCore)\n\n```1303:1306:3rdparty\u002FMegatron-LM\u002Fmegatron\u002Fcore\u002Ftransformer\u002Ftransformer_config.py\n        if self.cpu_offloading and self.pipeline_model_parallel_size > 1:\n            raise ValueError(\n                \"Currently there is no support for Pipeline parallelism with CPU offloading\"\n            )\n```\n\n## Failure Diagnosis\n\n| Symptom | Cause | Confirm | Fix |\n|---|---|---|---|\n| >15% GPU utilization drop | mlp recompute on large FFN | check `recompute_modules` includes `mlp` | check `expandable_segments:True` is set; consider reducing MBS |\n| Still OOM after adding layernorm | layernorm activations are too small | compare peak memory before\u002Fafter | add mlp recompute or check `expandable_segments:True` |\n| `AssertionError: full recompute is only supported with full iteration CUDA graph` | layer-level recompute (`recompute_granularity=full` + `recompute_num_layers`) with TE-scoped graphs. FP8 CS configs default to `cuda_graph_impl=transformer_engine`, `scope=mlp`. | check `cuda_graph_impl` and `cuda_graph_scope` | use submodule recompute (`selective` + `recompute_modules`), or `cuda_graph_impl=none`, or `local` + `full_iteration` |\n| ValueError: PP + CPU offloading | `cpu_offloading=True` with `pipeline_model_parallel_size > 1` | check PP config | disable CPU offloading or set PP=1 |\n| mlp+core_attn worse than mlp alone | double recompute overhead | compare Exp 1 vs Exp 2 | use mlp alone |\n\n## Known Limitations\n\n- Per-module memory savings vary significantly by model architecture and hidden\n  dimension\n- No automatic module selection — users must choose which modules to recompute\n- `layernorm` recompute is almost never worth it as a standalone fix\n- CPU offloading (the zero-compute-cost alternative) is blocked when PP > 1\n\n## Verification\n\n```bash\nuv run python -m pytest \\\n  tests\u002Funit_tests\u002Ftraining\u002Ftest_config.py -k \"recompute\" -q\n```\n\nSuccess criteria:\n- Unit tests pass for recompute config validation\n- No assertion errors from config validation\n",{"name":5,"license":15,"description":7,"when_to_use":24},"Reducing GPU memory via activation recompute, or investigating a commit that changed recompute settings and caused OOM or a regression; 'recompute_granularity', 'recompute_num_layers', 'recompute_modules', 'recompute_method', 'selective recompute', 'full recompute', 'activation memory OOM'.","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fnemo-mbridge-perf-activation-recompute",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill nemo-mbridge-perf-activation-recompute",{"tool":40,"command":41},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill nemo-mbridge-perf-activation-recompute",{"tool":43,"command":44},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill nemo-mbridge-perf-activation-recompute","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fnemo-mbridge-perf-activation-recompute\u002FSKILL.md",true,[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"BENCHMARK.md","REFERENCE","参考文档",4404,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fnemo-mbridge-perf-activation-recompute\u002FBENCHMARK.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"card.yaml",7920,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fnemo-mbridge-perf-activation-recompute\u002Fcard.yaml",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"evals\u002Fevals.json",1720,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fnemo-mbridge-perf-activation-recompute\u002Fevals\u002Fevals.json",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"skill-card.md",3749,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fnemo-mbridge-perf-activation-recompute\u002Fskill-card.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"skill.oms.sig","OTHER","其他",4833,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fnemo-mbridge-perf-activation-recompute\u002Fskill.oms.sig",[73,81,88,95,102,109],{"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},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\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},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\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},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\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},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\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":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]