What problem does it solve?
Before launching a GPU workload, you need to know whether the current machine can run it locally, inside Docker, or through a Slurm cluster. This Skill probes the environment and returns a structured execution scenario with GPU counts and hardware details, removing guesswork from workload placement.
Core Features & Use Cases
- Local GPU Detection: Runs nvidia-smi with a timeout to count available GPUs and identify the device type (e.g., B200, H100, A100).
- Docker vs Direct Execution: Checks whether the Docker CLI and daemon are usable to distinguish
satisfied, local, docker from satisfied, local, direct scenarios.
- Slurm Cluster Resolution: On login nodes without local GPUs, delegates hostname-based cluster identification to the internal-env-info skill to obtain GPU type, GPUs per node, and default storage paths.
- Use Case: An orchestrator needs to schedule a 4-GPU TensorRT-LLM benchmark. It calls this Skill with
required_devices: 4 and receives a scenario such as satisfied, slurm, local along with cluster name and per-node GPU count to route the job correctly.
Quick Start
Check whether this machine can run a workload requiring 4 GPUs and report the execution scenario, GPU count, and device type.