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
model-integrationsRoute SAHI model loading across supported detector and segmenter frameworks and optional dependencies.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task needs to choose, configure, or debug a SAHI detection model wrapper before prediction. It covers AutoDetectionModel.from_pretrained(...), framework-specific model loading, optional dependency gates, device selection, category mapping, preloaded models, and credential/local-weight distinctions.
model_type for Ultralytics/YOLO, YOLOE, YOLO-World, YOLOv5, RT-DETR, HuggingFace detection or segmentation, TorchVision, MMDetection, Detectron2, Roboflow Universe, or local RF-DETR.model_path, config_path, model, device, image_size, category_mapping, category_remapping, HuggingFace text labels/tokens, or Roboflow API-key behavior.get_prediction, get_sliced_prediction, CLI prediction, slice sizes, overlap, or export calls: route to sliced-inference.postprocess-backends.dataset-tools.Identify the detector family and desired source of weights: local file, framework model name, hosted Hub/Universe id, or a preloaded Python model object.
Open references/model-matrix.md to map the family to model_type, required arguments, source-backed caveats, and category mapping rules.
Open references/optional-dependencies.md before installing or importing optional frameworks. Treat optional wrappers as source-backed unless checked in the target runtime.
Run the safe checker when you only need dependency visibility:
python scripts/check_model_dependencies.py
The checker uses metadata and import-spec probes only; it does not load models or contact remote services.
If loading still fails, use references/troubleshooting.md to separate missing optional packages, missing model weights, credential problems, model/config mismatches, device issues, and category-id mapping mistakes.
token argument or HF_TOKEN at runtime.api_key argument or ROBOFLOW_API_KEY at runtime.Core SAHI source, model wrappers, docs, tests, and demo notebooks were inspected. Optional detector frameworks were not all installed in the construction environment, so framework-specific runtime behavior should be treated as source-backed until the checker and a minimal model load are run in the target environment.