← ClaudeAtlas

kg-gpulisted

Run training on Kaggle's GPUs within the weekly quota — plan the GPU budget, screen ideas on one fold (two per 2xT4 session, with pruning), promote winners to full-fold remote runs, resume timed-out runs, collect results into the ledger with GPU-hour accounting.
TranBaDat2607/claude-code-kaggle-grandmaster · ★ 2 · AI & Automation · score 81
Install: claude install-skill TranBaDat2607/claude-code-kaggle-grandmaster
# /kg-gpu: quota-aware remote training Run kgkit with the Bash tool, as `PYTHONPATH="${CLAUDE_PLUGIN_ROOT}" python -m kgkit <command>`: this command pre-approves that form for the kgkit calls it makes. Submitting, pushing or publishing still asks (so does a PowerShell `$env:` assignment). Request: `$ARGUMENTS` (default: `plan`). Load the `kaggle-gpu` skill first and follow its protocol. Commands below are `python -m kgkit gpu ...` (PYTHONPATH=$KGKIT_HOME). ## Always first 1. `gpu quota` and `gpu log`: GPU and TPU hours plannable, reset time, runs in flight (and which pushes hold a reservation), measured cost per fold. With several accounts registered in the Kaggle pane, `gpu quota --all` (the hours on each) and `gpu plan` (quota-bound or time-bound, counting them all). 2. `python -m kgkit status` and `python -m kgkit ledger baseline`: the accepted baseline, its fold scores and std. ## plan `gpu plan`, then propose a concrete schedule until the next reset and until the deadline: which screens (paired two per session), which promotions, and what is reserved for finals and inference. Flag use-it-or-lose-it hours before the reset. ## screen <idea> [<idea2>] 1. Implement each idea behind a flag in the training script and run `--smoke` locally. Commit. A new script, or a change to its input pipeline: run its `--bench` first (locally, or in a 0.3 h session) and fix an INPUT-BOUND or GPU IDLE verdict before spending hours of quota on it (skill `compute-efficiency