Docker conventions for running NVIDIA GPU container workloads — NGC authentication, --gpus flag, mount patterns, env-var passthrough, container inspection, data-root relocation for split-disk hosts, and common error modes. Use when another skill requires running an nvcr.io container or any docker run command on a GPU host. Trigger keywords — docker, docker run, nvcr.io, NGC, --gpus, nvidia-container-toolkit, container image, docker login, docker pull.
One-to-three-sentence description of what this data transformation does. Use when the user asks to "REPLACE-WITH-INTENT", or mentions REPLACE-WITH-DOMAIN-TERMS. Include literal trigger phrases the user is likely to say.
One-to-three-sentence description of what the model does and when to use it. Use when the user asks to "fine-tune REPLACE-WITH-NETWORK", "train REPLACE-WITH-NETWORK on REPLACE-WITH-DATA-TYPE", or mentions REPLACE-WITH-DOMAIN-TERMS. Include literal trigger phrases.
Where and how GPU jobs run on this platform. One-to-three-sentence summary. Use when the user asks to "deploy on REPLACE-PLATFORM", "run on REPLACE-PLATFORM", or mentions the platform's distinctive concepts (e.g., resource shape, instance, node group).
Full PAIDF AnomalyGen pipeline — fine-tune on a new anomaly dataset, generate synthetic anomaly images (SDG), evaluate quality (nn_score), and search per-sample (guidance, crop_ratio) parameters. Three modes: full (Phase 0→7: finetune then generate), finetune_only (Phase 0→1: train only), inference_only (Phase 0, 2→7: generate from an existing checkpoint). Use when the user asks to "fine-tune AnomalyGen", "generate anomaly images", "run PAIDF SDG", "evaluate SDG output quality", "run per-sample search", or run any part of the AnomalyGen pipeline, even if they only mention one phase.
One-to-three-sentence description of what the skill does and when to use it. Use when the user asks to "REPLACE-WITH-INTENT-1", "REPLACE-WITH-INTENT-2", or mentions REPLACE-WITH-DOMAIN-TERMS. Include literal trigger phrases the user is likely to say.
Top-level workflow orchestrator for <use case>. Runs an end-to-end pipeline of <N> stages: <stage 1> → <stage 2> → … → <stage N>. Use when the user asks to "REPLACE-WITH-INTENT-1", "REPLACE-WITH-INTENT-2", or mentions REPLACE-WITH-DOMAIN-TERMS. Include literal trigger phrases.