MLPerf automations guide

VerifiedSafe

Compact task-oriented reference for the mlcflow CLI and mlperf-automations repository. Covers mental model, adding scripts, variations, and dependencies.

Sby Skills Guide Bot
DevelopmentIntermediate
7/29/2026
Claude CodeCursor
#mlperf#automation-scripts#mlcflow#benchmarking#debugging

Recommended for

Automated summary

A working guide for Claude when contributing to the mlperf-automations repository: it explains the mlcflow CLI execution model, the three-file structure of a script (meta.yaml, customize.py, run.sh), and provides playbooks for adding, extending, or debugging scripts.

Strengths

  • Gives a compact mental model of the flow from mlcflow to variation/dependency resolution, preprocess, run.sh, postprocess, and caching
  • Concrete copy-pasteable playbooks for reading a script, scaffolding a new one, and adding variations or conditional dependencies
  • Debugging section that lists common root causes such as stale dependency caches, missing new_env_keys entries, and unset env vars

Limitations

  • Deliberately short and defers full technical detail to AGENTS.md
  • Covers only a handful of tasks out of the repository's 377 script directories
  • Assumes mlcflow is already installed and some familiarity with the repo layout
When to use it

Use it when modifying or debugging an automation script in the mlperf-automations repository with an agent's help.

When not to use it

Do not use it to run MLPerf benchmarks as an end user, nor as exhaustive reference documentation for the automation engine.

Security analysis

Safe
Quality score88/100

The skill is a documentation-style guide for using the mlcflow/mlperf-automations CLI. It contains only standard shell commands for inspecting, adding, running, and clearing the tool's own cache. There are no destructive system-level operations, no exfiltration, no obfuscated payloads, and no instructions to disable safety features. Commands like `mlc rm cache -f` only affect the tool's local cache, not the broader system.

No concerns found

How this analysis is made

Examples

Scaffold a new script
Add a new script to mlperf-automations called run-mlperf-inference-mytest, tagged app,mlperf,inference, using an existing inference reference script as the template, then fill in meta.yaml and customize.py.
Add a conditional CUDA dependency
In script/<alias>/meta.yaml of mlperf-automations, add a dep on get,cuda that only runs when MLC_MLPERF_DEVICE is gpu or cuda, and skips on Windows.
Debug a silently failing script
My mlperf-automations script runs but the env var never reaches the next stage — walk me through the mlc show cache / mlc rm cache checks and whether new_env_keys is missing.

skill.md — Claude working guide for mlperf-automations

Compact task-oriented reference. Read AGENTS.md for full technical detail.


Mental model (read this first)

mlcflow CLI  →  finds script by tags  →  resolves variations & deps  →
  customise.py:preprocess()  →  run.sh  →  customise.py:postprocess()  →
  caches new_env to ~/MLC/repos/local/cache/{uid}/

Two repos, two roles:

  • mlperf-automations (this repo) = content: 377 script directories + automation/ engine
  • mlcflow = driver CLI: installs via pip, dynamically loads the engine above

Three key files per script:

  • meta.yaml — identity, tags, deps, variations, env mapping (schema in automation/script/meta_schema.py)
  • customize.py — Python hooks: preprocess() builds the shell command; postprocess() reads results
  • run.sh — executes eval "${MLC_MLPERF_ENDPOINT_CMD}" and exits non-zero on failure

Task playbooks

"I need to understand what a script does"

cat script/<alias>/meta.yaml        # tags, deps, variations, input_mapping
cat script/<alias>/customize.py     # what it validates and what command it builds
cat script/<alias>/run.sh           # what actually executes
cat script/<alias>/README.md        # human summary

Key fields to read in meta.yaml: tags, deps, variations, input_mapping, new_env_keys, default_env.

"I need to add a new script"

  1. Scaffold with mlc add script:

    # Basic skeleton (copies template,generic)
    mlc add script mlcommons@mlperf-automations:<alias> --tags=<tags>
    
    # Copy nearest existing script as the template instead
    mlc add script mlcommons@mlperf-automations:<alias> --tags=<tags> \
        --template_tags=app,mlperf,inference,reference
    

    This creates script/<alias>/ with meta.yaml, customize.py, and run.sh. If multiple scripts match --template_tags, it prompts you to pick one.

  2. Edit meta.yaml — update at minimum:

    • alias, uid (already generated), tags, category
    • input_mapping (CLI args → env vars)
    • new_env_keys (what this script promises to export)
    • deps chain
  3. Edit customize.py — implement preprocess(i):

    • Guard required env vars (return {'return':1,'error':'...'} if missing)
    • Build the shell command string in env['MY_CMD']
  4. Edit run.sh — ensure it evals the command and exits non-zero on failure.

  5. mlc lint script --tags=<alias> — fix key order

  6. mlct <alias> — run built-in tests

  7. PR → main branch

"I need to add a variation"

Add to meta.yaml variations::

variations:
  my-variant:
    group: my-group        # omit group if stackable (free-standing)
    default: true          # omit if not the default
    env:
      MY_ENV_VAR: value
    deps:
      - tags: get,extra,dep   # extra dep only when this variation is active

Invoke: mlcr <tags>,_my-variant (underscore prefix on CLI).

"I need to add a conditional dependency"

deps:
  - tags: get,cuda
    enable_if_env:
      MLC_MLPERF_DEVICE: [gpu, cuda]   # only run if device is gpu or cuda
  - tags: get,rocm
    skip_if_env:
      MLC_HOST_OS_TYPE: [windows]      # skip on Windows

"I need to debug a script that fails silently"

mlcr <tags> --verbose                    # full debug output
mlc find cache --tags=<failing-dep>      # check if dep is cached
mlc rm cache --tags=<failing-dep>        # clear dep cache and re-run
mlc show cache --tags=<script-tags>      # inspect cached new_env
cat ~/MLC/repos/local/cache/*/mlc-cached-state.json | python3 -m json.tool

Common root causes:

  • Dep cached but stale → mlc rm cache --tags=<dep-tags>
  • new_env_keys missing from meta.yaml → key is silently dropped at the boundary
  • preprocess returned success but didn't set the expected env var → add assertion
  • MLC_TMP_* var expected downstream but not in new_env_keys → rename it or declare it

"I need to understand why an env var is not reaching a script"

Env propagation rules:

  1. CLI --key=val → input_mapping → env[MAPPED_VAR]
  2. env passes to deps unless dep has clean_env_keys that matches
  3. Dep's new_env_keys is the only way values come back from a dep
  4. MLC_TMP_* never cached, never passed to deps automatically
  5. If a parent caches, only declared new_env_keys are replayed on cache hit

"I need to run the inference benchmark locally for testing"

# Quickest smoke test — resnet50, onnxruntime, CPU, 500 samples
mlcr run-mlperf,inference,_submission,_short,_r6.0-dev \
     --model=resnet50 --implementation=mlcommons-python \
     --backend=onnxruntime --device=cpu \
     --scenario=Offline --test_query_count=500 --target_qps=1 \
     --hw_name=my_machine --quiet

# Find performance (tunes target QPS before a real run)
mlcr run-mlperf,inference,_find-performance,_short,_r6.0-dev \
     --model=resnet50 --implementation=mlcommons-python \
     --backend=onnxruntime --device=cpu \
     --scenario=Offline --hw_name=my_machine --quiet

# Accuracy-only run
mlcr run-mlperf,inference,_accuracy-only,_short,_r6.0-dev \
     --model=resnet50 --implementation=mlcommons-python \
     --backend=onnxruntime --device=cpu \
     --scenario=Offline --hw_name=my_machine --quiet

# Full submission run (both modes + compliance + checker + tar)
mlcr run-mlperf,inference,_submission,_full,_r6.0-dev \
     --model=resnet50 --implementation=mlcommons-python \
     --backend=onnxruntime --device=cpu \
     --scenario=Offline --execution_mode=valid \
     --submitter=MLCommons --hw_name=my_machine --quiet

"I need to inspect or clear cache"

mlc find cache --tags=get,mlperf,endpoints  # find cache folder
mlc show cache --tags=get,mlperf,endpoints  # print new_env snapshot
mlc rm cache --tags=get,mlperf,endpoints    # delete specific cache
mlc rm cache -f                             # delete ALL caches
mlc prune cache                             # delete expired (past cache_expiration)

"I need to run in Docker"

mlcd app,mlperf,inference,endpoints,_echo-server --num_samples=50
# Rebuilds image if meta.yaml docker: section changed:
mlcd app,mlperf,inference,endpoints --docker_rebuild

Quick reference: meta.yaml field cheat-sheet

| Field | What it does | |---|---| | alias | Script directory name and lookup key | | uid | 16-hex unique ID; never change after first commit | | automation_uid | UID of the script automation type (5b4e0237da074764); the only automation type currently in this repo | | tags | Comma-separated discovery tags; must be a superset of what callers request | | category | Grouping label in docs | | default_env | Env vars set before variation env (lowest priority) | | new_env_keys | Only these keys leave the script; use * and ? wildcards | | input_mapping | CLI --key → ENV_VAR translation | | deps | Scripts to run before preprocess() | | prehook_deps | Scripts to run after preprocess(), before run.sh | | posthook_deps | Scripts to run after run.sh, before postprocess() | | post_deps | Scripts to run after postprocess() | | variations | Named parameter sets; group: makes them mutually exclusive | | add_deps_recursive / adr | Override tags/versions on named deps deep in subtree | | versions | Per-version dep overrides and env | | cache | Enable caching (default: false) | | cache_expiration | Auto-invalidate after 1h / 1d / 1w | | tests | Inline test cases run by mlct |


customize.py hook signatures

def preprocess(i):  # before run.sh
def postprocess(i): # after run.sh
def predeps(i):     # before dep execution
def postdeps(i):    # after dep execution

All receive the same i dict:

i['env']         # mutable env dict → set vars here
i['automation']  # ScriptAutomation instance → i['automation'].logger
i['os_info']     # dict from detect-os
i['meta']        # parsed meta.yaml

All must return {'return': 0} or {'return': 1, 'error': 'reason'}.


Env variable naming conventions

No rigid rules — just two hard constraints and a naming guideline:

  • MLC_ prefix — use on all env vars set by MLC scripts so they are clearly distinguishable from the surrounding environment.
  • MLC_TMP_* — reserved for transient vars: never cached, never passed to deps. Use this when a value is only needed within the current script's run.
  • +VAR in new_env_keys — prepend to an existing env var (e.g. +PATH); the engine handles concatenation.

Everything else: name vars to reflect the script they come from and what they hold. Keep names reasonably short and meaningful — no other convention is enforced.


Files to read first by task type

| Task | Read these first | |---|---| | Understand the inference benchmark | script/run-mlperf-inference-app/meta.yaml, customize.py | | Reference for a new MLPerf benchmark (dep chain, variations, dispatch pattern) | script/app-mlperf-inference-mlcommons-python/meta.yaml, script/run-mlperf-inference-app/meta.yaml | | Debug env propagation | automation/script/module.py (search: new_env_keys, clean_env_keys) | | Debug caching | automation/script/cache_utils.py | | Add a script | Nearest similar script + automation/script/meta_schema.py | | Fix meta.yaml format | automation/script/lint.py | | Run CI locally | .github/workflows/test-mlc-script-features.yml | | Understand Docker path | automation/script/docker.py |


Don'ts

  • Don't use print() in customize.py — use i['automation'].logger
  • Don't raise exceptions for recoverable errors — return {'return': 1, 'error': '...'}
  • Don't edit mlc-cached-state.json or tmp-env.sh by hand
  • Don't push directly to main — always open a PR; use dev only for urgent merges without approval
  • Don't hard-code paths in run.sh — use env vars set by preprocess
  • Don't change automation_uid: 5b4e0237da074764 — it's the UID of the script automation type, not a script-specific value
  • Don't commit API keys — pass via --api_key=... only
  • Don't set MLC_TMP_* in new_env_keys (it's a transient namespace)

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/mlperf-automations-guide-ms5lrgpu/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/mlperf-automations-guide-ms5lrgpu' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mlperf-automations-guide-ms5lrgpu/download' --output '.skill-downloads/mlperf-automations-guide-ms5lrgpu/SKILL.md.part' && mv '.skill-downloads/mlperf-automations-guide-ms5lrgpu/SKILL.md.part' '.skill-downloads/mlperf-automations-guide-ms5lrgpu/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Quick reference: meta.yaml field cheat-sheet
FieldWhat it does
aliasScript directory name and lookup key
uid16-hex unique ID; never change after first commit
automation_uidUID of the script automation type (5b4e0237da074764); the only automation type currently in this repo
tagsComma-separated discovery tags; must be a superset of what callers request
categoryGrouping label in docs
default_envEnv vars set before variation env (lowest priority)
new_env_keysOnly these keys leave the script; use * and ? wildcards
input_mappingCLI --key → ENV_VAR translation
depsScripts to run before preprocess()
prehook_depsScripts to run after preprocess(), before run.sh
posthook_depsScripts to run after run.sh, before postprocess()
post_depsScripts to run after postprocess()
variationsNamed parameter sets; group: makes them mutually exclusive
add_deps_recursive / adrOverride tags/versions on named deps deep in subtree
versionsPer-version dep overrides and env
cacheEnable caching (default: false)
cache_expirationAuto-invalidate after 1h / 1d / 1w
testsInline test cases run by mlct

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/mlperf-automations-guide-ms5lrgpu/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills