Agent skill · nvidia
cdf-orchestration-preflight
Set up missing Linux prerequisites and audit whether a Cosmos Data Factory (CDF) Orchestration checkout and its Kubernetes or OSMO environment are ready to install the controller and run every packaged DAG. Use for prerequisite, pre-setup, Kubernetes, GPU, RWX/NFS, credential, controller-readiness, and quick-start checks. Not for deploying the controller (use cdf-orchestration-setup, which calls this audit first), authoring payloads, or running workflows.
What it needs
About 6k tokens when loaded.
What this skill does
Cosmos Data Factory Orchestration Preflight Determine what the current environment can install and which packaged DAGs it can run. Report partial readiness precisely; do not collapse a mixed environment into a single pass/fail result. Safety and scope Start with a read-only audit. Never print kubeconfig content, API keys, tokens, AWS credentials, Kubernetes Secret bodies, or raw command output that may contain them. Do not silently use ~/.kube/config: use the supplied KUBECONFIG path for an existing cluster. For a new cluster, bootstrap creates the kubeconfig. This skill may offer prerequisite remediation after the audit. Before changing a host, cluster, or tracked configuration, show the exact target and commands and obtain approval. Stop after prerequisites are ready: do not run make setup, build or push the Airflow image, install the controller Helm release, or trigger a DAG. Those are deployment or workflow tasks. Set up missing prerequisites For a fresh Linux environment, read bootstrap.md. It covers local tools, the Python environment, container runtime, Kubernetes, GPU/storage setup and secrets. Reuse working prerequisites and follow the user's execution preference. Installing the Helm client is prerequisite setup; deploying the controller belongs to the setup skill. Run the audit Run the bundled script from the repository root: Use --format json when a machine-readable report will help. The script is read-only. If KUBECONFIG is unset, ask for its path when a cluster exists; otherwise follow bootstrap. Omit --kubeconfig to run local checks before a cluster exists. AIRFLOWURL and AIRFLOWTOKEN may be exported for authenticated post-install checks; never put the token on the command line. When the user supplies an already-published controller image, pass its exact registry-qualified reference with --prebuilt-controller-image REGISTRY/REPOSITORY:TAG. This switches installation readiness from build/push prerequisites to a read-only docker manifest inspect check. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/cdf-orchestration-preflight