菜单
Benchmark HoloMotion inference with deployment-equivalent artifacts, runtime state, preprocessing, I/O, and hardware. Use for latency, throughput, cache, refinement, export, quantization, target-runtime, or framework-versus-deployment comparisons.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/HorizonRobotics/HoloMotion --skill benchmark-holomotion-latency命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Deploy and troubleshoot a HoloMotion policy for offline real-robot motion tracking. Use for deployment preflight, no-action validation, model or motion substitution, controller startup, and offline robot-runtime diagnosis.
Look up Isaac Lab APIs and implementations in the source tree associated with the project's active training environment. Use for source-level questions about Isaac Lab packages without importing simulator modules.
Set up, run, validate, or troubleshoot a supported HoloMotion live-teleoperation pipeline. Use for source readiness, reference processing, streaming, timing, visualization, policy integration, controller transitions, and real-robot teleoperation problems.
基于 SOC 职业分类
正在显示 SKILL.md
| name | benchmark-holomotion-latency |
| description | Benchmark HoloMotion inference with deployment-equivalent artifacts, runtime state, preprocessing, I/O, and hardware. Use for latency, throughput, cache, refinement, export, quantization, target-runtime, or framework-versus-deployment comparisons. |
Treat development-framework timing as structural evidence, not a deployment result. Resolve the current exporter, runtime caller, profile, and target backend from source before building a benchmark.
Keep artifact, inputs, backend, state, and measurement boundary fixed when comparing refinements, precisions, or runtimes. Validate numerical and task quality before accepting a speedup.
Target access or model execution on a robot computer requires explicit user authorization. Keep controllers stopped, use isolated temporary artifacts, and never overwrite deployed files or infer physical validation from a benchmark.
State the resolved artifact and hash, runtime/backend, precision, hardware, measurement boundary, state handling, warmup, sample count, load, latency percentiles, deadline relation, and numerical or task-quality delta.
