solo-kaggle-gpu
Skill18 starsChanged 4 months agoMITView on GitHub
Run GPU or TPU work for free on Kaggle from the terminal — push a local folder as a private kernel on 2x T4, P100 or TPU v5e-8, wait, pull the outputs back. Use when user says "обучи модель", "нужен GPU", "посчитать на видеокарте", "бесплатный GPU", "train a model", "fine-tune", "CUDA kernel", "run it on kaggle", "колаб", or a job is GPU-shaped and the Mac has no CUDA or is too slow. Do NOT use for CPU-bound jobs or private data (keep both local), or for exporting trained weights to devices (use /model-shrink).
- Reads credentials
- Installs packages
In this repository62 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- solo-android-releaseSkill
- solo-apple-app-iconSkill
- solo-auditSkill
- solo-boardSkill
- solo-buildSkill
- solo-community-outreachSkill
- solo-content-genSkill
- solo-creator-growthSkill
- solo-customer-finderSkill
- solo-deep-researchSkill
- solo-deploySkill
- solo-diagnoseSkill
- solo-domainSkill
- solo-factorySkill
- solo-github-outreachSkill
- solo-gmail-cliSkill
- solo-grillSkill
- solo-hackathonSkill
- solo-humanizeSkill
- solo-i18nSkill
- solo-index-youtubeSkill
- solo-initSkill
- solo-ios-devSkill
- solo-ios-releaseSkill
- solo-kindleSkill
- solo-knowledgeSkill
- solo-landing-genSkill
- solo-launchSkill
- solo-legalSkill
- solo-memory-auditSkill
- solo-metrics-trackSkill
- solo-mirrorSkill
- solo-model-shrinkSkill
- solo-music-reels-cutSkill
- solo-open-datasetSkill
- solo-paperSkill
- solo-pdf-printSkill
- solo-pipelineSkill
- solo-planSkill
- solo-redditSkill
- solo-researchSkill
- solo-retroSkill
- solo-reviewSkill
- solo-scaffoldSkill
- solo-secretsSkill
- solo-seo-auditSkill
- solo-seo-cliSkill
- solo-setupSkill
- solo-sgrSkill
- solo-skill-auditSkill
- solo-skill-shelfSkill
- solo-stem-splitSkill
- solo-streamSkill
- solo-supervoxSkill
- solo-swiftui-design-systemSkill
- solo-transcribeSkill
- solo-validateSkill
- solo-video-editSkill
- solo-video-promoSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 53
Never paste a token into chat or a file in a repo: auth login stores it for you.
- Very specific: line 57
Put the job in a folder with run.sh as its entry point.
- Very specific: line 88
Use both T4s: torchrun --nproc_per_node=2 train.py, or split a CUDA job by device.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
kaggle-gpu — free NVIDIA and TPU time, one command per run
Kaggle gives every phone-verified account about 30 GPU hours a week (two T4s or one P100) plus TPU time, and its CLI can push a script, run it headless and download what it wrote. That makes it the default for anything that needs CUDA and fits in 12 hours: training and fine-tuning, a custom CUDA kernel, batch inference, embeddings over a corpus. Colab's free tier has no headless run from a CLI, so it is for hand-driven notebooks only.
When it pays, and when it does not
| Job | Kaggle? | Why |
| Train or fine-tune a model, batch inference, embeddings | yes | 2x T4 (15 GB each), PyTorch/JAX in the image |
| Custom CUDA kernel | yes | nvcc 12.8 and g++ 13.3 are there |
| CPU-bound job (C++ DP, search, compile farm) | no | 4 vCPU = 2 physical Xeon cores at 2.2 GHz; one Apple M5 core does the work of ~2.4 of them |
| Anything with personal, client or secret data | no | private kernels are still Google's machines |
| Over 12 h in one go | only with checkpoints | session cap; chain runs (below) |
| Speech-to-text on a Mac | no | local Apple GPU (/transcribe) is fast and keeps audio local |
Measured with scripts/kaggle-run.sh on 2026-10-29 (run.sh probe: nproc, cgroup quota,
free, nvidia-smi, a 10 s busy loop on every core):
| Runtime | CPU | RAM | Accelerator | Busy loop, all cores |
CPU (none) | 4 vCPU Xeon 2.2 GHz, quota 4.0 | 31 GB | none | 115M (M5: 70M per core) |
NvidiaTeslaT4 | 4 vCPU Xeon 2.0 GHz | 31 GB | 2x Tesla T4, 15 GB each, CUDA 12.8 | 142M |
TpuV5E8 | never started: QUEUED for 17+ h (pushed 2026-10-29 ~13:00, still queued 2026-10-30 06:45) |
Reported, not measured here: ~30 GPU h/week (floats; the real number is on
kaggle.com/settings), 12 h sessions for CPU/GPU and 9 h for TPU, 20 GB in /kaggle/working.
Two GPU kernels at once drain the weekly quota twice as fast.
One-time setup
uv tool install kaggle # CLI 2.x
kaggle auth login # opens the browser; token lands in ~/.kaggle/credentials.json
kaggle config view # prints the username: login workedGPU, TPU and internet inside a kernel need a phone-verified account (kaggle.com/settings).
Never paste a token into chat or a file in a repo: auth login stores it for you.
Run
Put the job in a folder with run.sh as its entry point. It runs in /kaggle/working;
whatever it leaves there comes back.
S=${CLAUDE_PLUGIN_ROOT}/skills/kaggle-gpu/scripts/kaggle-run.sh
$S jobs/probe # CPU
$S jobs/train NvidiaTeslaT4 # 2x T4
$S jobs/train NvidiaTeslaT4 --dry # build the kernel, push nothingThe script inlines every file of the folder (except out/) into one generated kernel
(cap 5 MB, KAGGLE_INLINE_MAX), pushes it as private, polls the status every 30 s,
downloads the output to <folder>/out/<accel>/ with run.log, and exits non-zero if the
run failed. Kernel slug: <KAGGLE_PREFIX:-run>-<folder>-<accel>; pushing again makes a new
version of the same kernel.
| Env | Effect |
KAGGLE_INTERNET=1 | pip install, Hugging Face downloads |
KAGGLE_DATASETS=user/slug,... | inputs too big to inline, mounted at /kaggle/input/<slug>/ (create once: kaggle datasets create -p dir) |
KAGGLE_KERNELS=user/prev-slug | an earlier run's output mounted read-only, to resume from its checkpoints |
KAGGLE_TIMEOUT=SECONDS | cap the run |
KAGGLE_PREFIX=train-p2 | a distinct slug per leg of a chained run |
Training longer than one session
run.shsaves a checkpoint to/kaggle/working/ckpt/every 30-60 minutes and on SIGTERM, and resumes from/kaggle/input/<prev-slug>/ckpt/when that exists.- Leg 1:
KAGGLE_PREFIX=train-p1 $S jobs/train NvidiaTeslaT4. - Leg 2:
KAGGLE_PREFIX=train-p2 KAGGLE_KERNELS=<user>/train-p1-train-nvidiateslat4 $S jobs/train NvidiaTeslaT4.
Use both T4s: torchrun --nproc_per_node=2 train.py, or split a CUDA job by device.
(Chaining through kernel_sources follows Kaggle's documented mount layout and has not been
exercised by this skill yet: check ls /kaggle/input in the first chained run.)
Verify
run.logends the wayrun.shmeant it to, and the script printedKernelWorkerStatus.COMPLETE.- First run on a new kind of job: put
nvidia-smiandpython -c "import torch; print(torch.cuda.device_count())"at the top ofrun.sh; a kernel pushed without the accelerator flag silently runs on CPU. - Status by hand:
kaggle kernels status <user>/<slug>; logs and files:kaggle kernels output <user>/<slug> -p dir.
Gotchas
- TPU v5e-8 is not a resource to plan on: the probe sat in
QUEUEDfor 17+ hours and never ran. Use it only for work that can wait days; GPU runs start within a minute. - A status poller on a flaky network (phone hotspot) dies on an SSL error, and
*error*in the case pattern reads it as a failed kernel. Re-checkkaggle kernels statusby hand before concluding. kaggle kernels statusprintsKernelWorkerStatus.QUEUED|RUNNING|COMPLETE|ERROR; the script matches the last word.- Inlined files live in the kernel's source on Kaggle. Keep keys out; if a run truly needs one, use Kaggle Secrets (
kaggle_secrets.UserSecretsClient), set in the web editor. - Mining or other ToS-banned work gets the account blocked; ordinary research and training is what the quota is for.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

