计划执行与检查节点
executing-plans
按既定实施计划完成工作,保持过程检查和反馈。
cli-and-model-registry【效率与协作】Guides Autodistill CLI runs, model registry inspection, plugin selection, and safe dry-run troubleshooting.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this sub-skill when a task asks for an autodistill ... command, model alias selection, plugin package requirements, model support matrix interpretation, registry inspection, or a safe dry run before downloads/training.
The core CLI orchestrates plugin base models and target models. It can import or install plugin packages, label an image folder, train a target model, and optionally upload to Roboflow. Treat full CLI runs as side-effectful unless the user explicitly approves plugin installs, model downloads, training time, hardware use, output paths, and credentials.
--model_type mismatch, Roboflow credentials, and training side effects.python scripts/autodistill_cli_smoke.py \
--ontology-json '{"milk bottle": "bottle"}'
python scripts/inspect_model_registry.py
If these pass, the core CLI/registry is importable. They do not prove that a concrete plugin can download weights, run inference, train, or upload.
autodistill images \
--base grounding_dino \
--target yolov8 \
--ontology '{"milk bottle": "bottle"}' \
--output ./dataset \
--epochs 200 \
--upload-to-roboflow false
Before running a full command, verify the input image folder, ontology JSON, selected plugin packages, target model training requirements, and output directory. Avoid -y true until plugin installation side effects are approved.
--models, --upload-to-roboflow, -y, and --test are Click boolean options that expect explicit values in this snapshot's help output, for example --upload-to-roboflow false.SUPPORTED_MODEL_TYPES is ['detection', 'segmentationclassification'] because "segmentation" "classification" is missing a comma. The docs mention detection, segmentation, and classification, but --model_type classification may fail in this snapshot.import_requisite_module may call pip install autodistill_<alias> when noninteractive install is enabled. That package naming does not match every published plugin's hyphenated distribution spelling in documentation, so inspect before relying on auto-install.