executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
auto-labeling-modelsUse and troubleshoot X-AnyLabeling AI-assisted model configs, registry, custom models, downloads, and optional inference backends.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task involves X-AnyLabeling's AI-assisted model registry, built-in model configuration YAMLs, custom model loading, download source selection, remote inference hooks, or CPU/GPU/TensorRT backend choices.
Identify the target model family in references/model-overview.md. Confirm whether the user needs a local built-in/adapted model, a remote server/API model, or a code-level adapter for an unadapted model.
For built-in or adapted custom models, use references/custom-models.md to check the YAML schema, required fields, custom-name rules, and model-specific config fields.
For downloads, cache layout, ModelScope selection, ONNX Runtime, GPU extras, or TensorRT, use references/backend-and-downloads.md.
If loading fails, route by symptom through references/troubleshooting.md.
For safe registry inspection without model downloads or weight loading, run the bundled helper:
python sub-skills/auto-labeling-models/scripts/inspect_model_configs.py --show-types
python sub-skills/auto-labeling-models/scripts/inspect_model_configs.py --custom-config <config.yaml> --json
type, name, display_name, model path fields,
classes, thresholds, provider, config_file, and YOLO-family engine
values ort, dnn, and trt._custom_
prefixing.Model subclass implementing
predict_shapes and unload.../annotation-ui/SKILL.md.xanylabeling convert tasks: use
../conversion-cli/SKILL.md.../developer-workflows/SKILL.md.The generated skill is grounded in package x-anylabeling-cvhub 4.0.2,
Python >=3.11 with Python 3.12 recommended, and a CPU inspection environment
where ONNX Runtime's CPU provider was verified. CUDA, TensorRT, remote server
operation, model downloads, and training/export workflows were documented from
repo evidence but were not executed during construction.