Automated summary
Working guide for modifying and debugging the mlcflow repository, the CLI driver of the MLCommons automation framework.
Strengths
- Provides an explicit mental model of the call chain from `mlcr <tags>` down to `ScriptAutomation.run`
- Gives file-by-file playbooks for adding a command, a dispatch branch, a schema key, or an error code
- Includes an ordered debugging procedure (`--verbose`, `mlc find`, `mlc reindex`, cache purge) for run and index failures
- States the `{'return': 0}` / `{'return': N, 'error': ...}` result contract every action must follow
Limitations
- Highly specific to mlcflow: assumes the repo is cloned and `mlperf-automations` is registered
- Covers neither testing nor code style nor the contribution workflow (defers to AGENTS.md)
- Cited line numbers (e.g. ~363, ~393) can drift as the file evolves
Use it when adding a command or dispatch branch to mlcflow, or when investigating why an `mlcr` run or the index is failing.
Avoid it for authoring the automation scripts themselves or for any work outside the mlcflow repository.
Security analysis
SafeThe skill is a development guide for the mlcflow CLI. It contains code snippets and debugging commands, but none are destructive, exfiltrating, or obfuscated. Commands like 'mlc rm cache --tags' are cache management within the tool's own ecosystem. No use of curl|sh, rm -rf /, token exfiltration, or disabling safety mechanisms.
No concerns found
How this analysis is madeExamples
Add a new `mlc docker-build` command to mlcflow that delegates to ScriptAutomation, and register it in build_parser() so it shows up in the general command group.`mlcr my-script --tags=resnet` keeps failing with a ScriptExecutionError. Walk me through diagnosing it: verbose output, checking the script index, and clearing stale cache entries.I want to add a new top-level `cache_timeout` key to meta.yaml and have indexing validate it. Show me where to add it in meta_schema.py and which type constant to use.skill.md — Claude working guide for mlcflow
Compact task playbooks. Read AGENTS.md for full technical detail.
Mental model
mlcr <tags> → mlc_expand_short("run") → main()
→ get_action("script", parent) → ScriptAction.run(run_args)
→ call_script_module_function("run", run_args)
→ find_target_folder("script") # walks registered repos
→ dynamic_import_module(module.py) # loads ScriptAutomation
→ ScriptAutomation(self, path).run(run_args) # engine in mlperf-automations
This repo = CLI driver only. Script logic lives in mlperf-automations/automation/script/module.py, loaded at runtime.
Result dict contract — every action method must return:
{'return': 0}on success{'return': N, 'error': 'message'}on failure (N > 0)
Task playbooks
"I need to add a new mlc command"
-
Add method to the appropriate Action class (hyphens → underscores in name):
# script_action.py — for a command that delegates to ScriptAutomation def my_action(self, run_args): return self.call_script_module_function("my_action", run_args)# script_action.py — for a command handled entirely in mlcflow def my_action(self, run_args): self.action_type = "script" res = self.search(run_args) # ... do work ... return {'return': 0} -
Register the command in
build_parser()(main.py):# General (script/cache/repo): add to the first for-loop ~line 363 for action in ['run', 'pull', ..., 'my-action']: # Script-only: add to the second for-loop ~line 393 for action in ['docker', ..., 'my-action']: -
(Optional) Add a short command in
main.py+pyproject.toml:def mlcx(): mlc_expand_short("my-action")mlcx = "mlc.main:mlcx"
"I need to add a new dispatch branch for ScriptAutomation"
In call_script_module_function() (script_action.py), add an elif branch:
elif function_name == "my_action":
result = automation_instance.my_action(run_args)
"I need to add validation for a new meta.yaml key"
In meta_schema.py:
# Add to TOP_LEVEL_SCHEMA (top-level keys):
"my_new_key": DICT, # or STR, LIST, BOOL, etc.
# Add to DEP_ENTRY_SCHEMA if it goes inside a dep entry
# Add to VARIATION_ENTRY_SCHEMA if it goes inside a variation
Types are sets like STR = {"str"}, LIST = {"list"}, etc. validate_meta()
is called during indexing — errors halt the index build.
"I need to add a new error code or improve error messages"
In error_codes.py:
class ErrorCode(Enum):
MY_ERROR = (2008, "Description of the error")
To show actionable suggestions to the user, add a branch in get_error_guidance():
elif "my error pattern" in message:
guidance["error_message"] = "Likely cause"
guidance["suggestions"] = ["Do X to fix it."]
Error codes 2000–2007 are used; warning codes 1000–1006 are used. Pick the next available number in each range.
"I need to understand why mlcr <tags> fails"
mlcr <tags> --verbose # full debug output including ScriptAutomation logs
mlc find script --tags=<tags> # verify script is indexed
mlc reindex # rebuild index if stale
mlc list repo # verify mlperf-automations is registered
mlc find cache --tags=<failing-dep> # check if a dep is stale
mlc rm cache --tags=<failing-dep> # clear dep cache
Check for ScriptExecutionError in the output — it prints a rerun command, the
error code, likely cause, suggestions, and version info file path.
"I need to debug why the index is not picking up a script"
- Check
meta.yamlhas all four required keys:alias,uid,automation_alias,automation_uid - Run
mlc reindexto force a full rebuild - Check
~/MLC/repos/index_script.jsondirectly if needed - Run
mlcr <tags> --verbose— validation errors are logged during indexing
"I need to understand how args reach the automation engine"
convert_args_to_dictionary() in utils.py parses sys.argv extras:
--key=val→{"key": "val"}--flag→{"flag": True}--adr.compiler.tags=gcc→{"adr": {"compiler": {"tags": "gcc"}}}-v→{"v": True}(unless it matcheslog_flag_aliases)
The resulting run_args dict is passed directly to ScriptAutomation.run().
"I need to call mlcflow from Python"
from mlc.action import access
result = access({
'action': 'run',
'target': 'script',
'tags': 'detect,os'
})
if result['return'] > 0:
print(result['error'])
Or use the instance method on an Action object:
from mlc.action import Action
a = Action()
result = a.access({'action': 'find', 'target': 'script', 'tags': 'detect,os'})
"I need to write a test"
Look at existing tests for patterns:
tests/test_cache_mark_tmp.py
tests/test_action_invalid_meta_entries.py
Run tests with:
pip install -e .
python -m pytest tests/
Quick reference: key classes and where they live
| Class / function | File | What it does |
|---|---|---|
| main() | main.py | CLI entry point; parses args, dispatches to action |
| mlcr(), mlcd(), … | main.py | Short-form entry points registered in pyproject.toml |
| get_action(target, parent) | action_factory.py | Maps "script"/"cache"/"repo" → Action class |
| Action | action.py | Base: repo loading, index, CRUD (add/rm/cp/mv/search) |
| Action.access(i) | action.py | Python API: call any action programmatically |
| ScriptAction | script_action.py | Script actions; delegates to ScriptAutomation via call_script_module_function |
| ScriptExecutionError | script_action.py | Exception with script context; formatted by _report_error() |
| RepoAction | repo_action.py | pull/add/rm/find for repos |
| CacheAction | cache_action.py | find/rm/show/prune/list/mark-tmp for caches |
| Index | index.py | Incremental tag-based index; file-locked JSON |
| validate_meta() | meta_schema.py | Validates script meta.yaml; called during indexing |
| get_error_guidance() | error_codes.py | Pattern-matches error text → actionable suggestions |
| get_new_uid() | utils.py | Generates a 16-hex UID |
Don'ts
- Don't raise exceptions for recoverable errors in action methods — return
{'return': 1, 'error': '...'} - Don't call
print()for user-facing messages — uselogger.info/warning/error - Don't add
.in flat arg key names —.triggers nested dict parsing inconvert_args_to_dictionary() - Don't push directly to
main— open a PR; usedevonly for urgent merges without approval - Don't hard-code
~/MLC/repos— useself.repos_path(which readsMLC_REPOSenv var) - Don't edit
index_script.jsonormodified_times.jsonby hand — usemlc reindex - Don't call
ScriptAutomationdirectly — always go throughcall_script_module_function()
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 filesThis 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.mdFrom the root of a test project, save the file as .skill-downloads/mlcflow-cli-development-guide-mrwakda7/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/mlcflow-cli-development-guide-mrwakda7' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mlcflow-cli-development-guide-mrwakda7/download' --output '.skill-downloads/mlcflow-cli-development-guide-mrwakda7/SKILL.md.part' && mv '.skill-downloads/mlcflow-cli-development-guide-mrwakda7/SKILL.md.part' '.skill-downloads/mlcflow-cli-development-guide-mrwakda7/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: key classes and where they live
| Class / function | File | What it does |
|---|---|---|
main() | main.py | CLI entry point; parses args, dispatches to action |
mlcr(), mlcd(), … | main.py | Short-form entry points registered in pyproject.toml |
get_action(target, parent) | action_factory.py | Maps "script"/"cache"/"repo" → Action class |
Action | action.py | Base: repo loading, index, CRUD (add/rm/cp/mv/search) |
Action.access(i) | action.py | Python API: call any action programmatically |
ScriptAction | script_action.py | Script actions; delegates to ScriptAutomation via call_script_module_function |
ScriptExecutionError | script_action.py | Exception with script context; formatted by _report_error() |
RepoAction | repo_action.py | pull/add/rm/find for repos |
CacheAction | cache_action.py | find/rm/show/prune/list/mark-tmp for caches |
Index | index.py | Incremental tag-based index; file-locked JSON |
validate_meta() | meta_schema.py | Validates script meta.yaml; called during indexing |
get_error_guidance() | error_codes.py | Pattern-matches error text → actionable suggestions |
get_new_uid() | utils.py | Generates a 16-hex UID |
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/mlcflow-cli-development-guide-mrwakda7/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.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.