gilbreth-preflight

Validate GPU quotas, environments, and paths for Gilbreth SLURM submissions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/j-mckerracher/agent-research --skill gilbreth-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gilbreth-preflight
Source: https://github.com/j-mckerracher/agent-research/tree/main/skills-main/gilbreth-preflight
Command: npx skills add https://github.com/j-mckerracher/agent-research --skill gilbreth-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before submitting any SLURM job to Gilbreth, this preflight checks quotas, environment readiness, and paths to prevent wasted runs and queue delays.

Core Features & Use Cases

  • Verifies GPU quota and available partitions for the user account.
  • Validates environment activation and required modules or conda environments.
  • Checks input/output paths and ensures SLURM script headers are correct.

Quick Start

Run the Gilbreth preflight check before submitting a SLURM job to verify quotas, environment, and paths.

Frequently Asked Questions about gilbreth-preflight

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate my SLURM job script before submitting it to Gilbreth?

You can validate a SLURM job submission on Gilbreth by running preflight checks that verify GPU quotas, active conda environments or modules, and existing file paths before the job enters the queue.

What does a SLURM preflight check for HPC submissions verify?

A SLURM preflight check for HPC submissions verifies that your GPU quotas are available, the correct conda environment or module is loaded, and all required input/output paths and SLURM headers are valid before submission.

Do I need SSH access to run preflight checks on Gilbreth SLURM jobs?

Yes, SSH access to Gilbreth is required to run these preflight checks, because the validation process queries live queue state via squeue and verifies file paths directly on the cluster.

Why does my Gilbreth SLURM job fail before running?

Your Gilbreth SLURM job may fail before running if you have exceeded your GPU quota, failed to activate the correct conda environment or modules, or specified invalid input/output paths in your script headers.

Can I check my GPU quota and partition availability before submitting an HPC job?

Yes, you can check your GPU quota and available partitions before submitting an HPC job by running a preflight validation that queries your account limits and live queue state via squeue.