[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FD36S6C8VH9ASMZS84T06":3,"skill-same:01M79FD36S6C8VH9ASMZS84T06":69},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79FD36S6C8VH9ASMZS84T06","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.","Elogic360\u002Fsoftware-factory","Elogic360","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F156535519?v=4","01M74NH3F0RB13PWB7JZDE2V80","elogic360","01M74NH3FPC65082MDZVMFHDM3",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\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\u003C!-- NVSkills CI refresh: 2026-06-15. No instruction changes. -->\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. Rule out allocator fragmentation first with\n   `PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True`; see\n   @skills\u002Fnemo-mbridge-perf-memory-tuning\u002FSKILL.md.\n2. For activation pressure, start with selective recompute:\n   `recompute_granularity=\"selective\"` and `recompute_modules=[\"core_attn\"]`.\n3. Add modules by cost: `\"layernorm\"` is cheap but saves little, while `\"mlp\"`\n   saves much more memory at a clear throughput cost.\n4. Use full-layer recompute only when selective recompute does not fit, and set\n   all required fields: `recompute_granularity=\"full\"`, `recompute_method`, and\n   `recompute_num_layers`.\n5. With FP8 or TE-scoped CUDA graphs, avoid full-layer recompute unless graph\n   scope is `full_iteration`; otherwise use selective recompute or disable TE\n   graph capture.\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\nuv run python scripts\u002Fperformance\u002Frun_script.py \\\n  -m llama \\\n  -mr llama3_8b \\\n  --task pretrain \\\n  -g h100 \\\n  -c bf16 \\\n  -ng 8 \\\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 a large FFN | check whether `recompute_modules` includes `mlp` | remove `mlp`, lower micro batch size, or use CPU offload if PP=1 |\n| Still OOM after adding layernorm | layernorm activations are too small to move the peak materially | compare peak memory before\u002Fafter | switch to a higher-impact module or full-layer recompute |\n| `AssertionError: full recompute is only supported with full iteration CUDA graph` | layer-level recompute with TE-scoped graph capture | check `cuda_graph_impl` and `cuda_graph_scope` | use `selective`, set `cuda_graph_impl=none`, or use `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\u003C!-- NVSkills CI refresh: 2026-06-15. No instruction changes. -->\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. Rule out allocator fragmentation first with\n   `PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True`; see\n   @skills\u002Fnemo-mbridge-perf-memory-tuning\u002FSKILL.md.\n2. For activation pressure, start with selective recompute:\n   `recompute_granularity=\"selective\"` and `recompute_modules=[\"core_attn\"]`.\n3. Add modules by cost: `\"layernorm\"` is cheap but saves little, while `\"mlp\"`\n   saves much more memory at a clear throughput cost.\n4. Use full-layer recompute only when selective recompute does not fit, and set\n   all required fields: `recompute_granularity=\"full\"`, `recompute_method`, and\n   `recompute_num_layers`.\n5. With FP8 or TE-scoped CUDA graphs, avoid full-layer recompute unless graph\n   scope is `full_iteration`; otherwise use selective recompute or disable TE\n   graph capture.\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\nuv run python scripts\u002Fperformance\u002Frun_script.py \\\n  -m llama \\\n  -mr llama3_8b \\\n  --task pretrain \\\n  -g h100 \\\n  -c bf16 \\\n  -ng 8 \\\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 a large FFN | check whether `recompute_modules` includes `mlp` | remove `mlp`, lower micro batch size, or use CPU offload if PP=1 |\n| Still OOM after adding layernorm | layernorm activations are too small to move the peak materially | compare peak memory before\u002Fafter | switch to a higher-impact module or full-layer recompute |\n| `AssertionError: full recompute is only supported with full iteration CUDA graph` | layer-level recompute with TE-scoped graph capture | check `cuda_graph_impl` and `cuda_graph_scope` | use `selective`, set `cuda_graph_impl=none`, or use `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","c475fc64e94e803b50d14a791dfee8853fbb2c5c","skills\u002Fnvidia\u002Fnemo-mbridge-perf-activation-recompute","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory","https:\u002F\u002Fgithub.com\u002FElogic360","2026-11-08 22:21:22",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Elogic360\u002Fsoftware-factory --skill nemo-mbridge-perf-activation-recompute",{"tool":37,"command":38},"bunx","bunx skills add Elogic360\u002Fsoftware-factory --skill nemo-mbridge-perf-activation-recompute",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Elogic360\u002Fsoftware-factory --skill nemo-mbridge-perf-activation-recompute","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-activation-recompute\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"BENCHMARK.md","REFERENCE","参考文档",4036,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-activation-recompute\u002FBENCHMARK.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"card.yaml",7920,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-activation-recompute\u002Fcard.yaml",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"evals\u002Fevals.json",1720,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-activation-recompute\u002Fevals\u002Fevals.json",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"skill-card.md",3814,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-activation-recompute\u002Fskill-card.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"skill.oms.sig","OTHER","其他",4833,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-mbridge-perf-activation-recompute\u002Fskill.oms.sig",[70,77,84,91,98,105],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79G206MT3J6S0GY3C45P2KV","vss-summarize-video","Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-summarize-video\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79G1WN63PGRE8CKD47WEBQ5","vss-setup-video-analytics-api","Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M79G1S9F7VY3EF6H53PRP5AN","vss-setup-behavior-analytics","Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-behavior-analytics\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M79G1N1S1Y27PFZPYMNK1MTQ","vss-search-archive","Use this skill to run top-level VSS fusion search on archived video, or to ingest video files \u002F RTSP streams for search. Do NOT use for ad-hoc visual Q&A (use vss-ask-video), live captioning (use vss-deploy-dense-captioning), or video summarization and reports (use vss-summarize-video).","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-search-archive\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M79G1H6WN0Q6C0VCAXCZX6B7","vss-query-analytics","Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-query-analytics\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M79G1DYPNXQS7QHZ0AAF5FX5","vss-manage-video-io-storage","Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add\u002Fdelete sensors and streams). Not for VLM inference or search.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-manage-video-io-storage\u002FSKILL.md",[],[]]