free-gpu

Execute Python, ML, and inference workloads on Colab or Kaggle GPUs from a local terminal.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/franklinbaldo/skills --skill free-gpu-franklinbaldo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: free-gpu
Source: https://github.com/franklinbaldo/skills/tree/main/free-gpu
Command: npx skills add https://github.com/franklinbaldo/skills --skill free-gpu-franklinbaldo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires google-colab-cli, kaggle, cyclopts, and includes scripts (resource) and references (resource) components.

What problem does it solve? Local machines often lack a GPU, and locked-down Windows machines may lack WSL or administrator rights, blocking ML training, inference, and OCR workloads. This Skill routes those jobs to free Google Colab or Kaggle GPUs, handling CLI installation with uv, authentication, uploads, monitoring, artifact retrieval, and resource cleanup. ## Core Features & Use Cases - Environment-based routing: Chooses Colab CLI on Linux/macOS/WSL, native Kaggle on locked-down Windows, or a documented LiteBox/shim path for Colab without WSL. - Colab workflows: Supports one-shot colab run --gpu T4 job.py execution and named sessions for dependency installs, uploads, downloads, logs, and guaranteed cleanup via colab stop. - Kaggle workflows: Creates private GPU script Kernels with validated metadata, pushes them with an accelerator, polls status, and downloads outputs written under /kaggle/working. - Use Case: On a Windows laptop without admin rights, package a training script as a private Kaggle Kernel, run it on a Tesla T4, and retrieve the resulting model artifacts without installing anything system-wide. ## Quick Start Use the free-gpu skill to run my training script on a free Colab or Kaggle GPU and download the output artifacts.

Frequently Asked Questions about free-gpu

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

FAQPage Schema
How do I run a Python script on a free GPU from the terminal?▼

Use the google-colab-cli one-shot command `uvx --from google-colab-cli colab run --gpu T4 job.py`, which creates, executes, and releases the VM. For jobs needing uploads or downloads, use a named Colab session or push a private Kaggle Kernel with a GPU accelerator.

Colab vs Kaggle for free GPU jobs: which should I use?▼

Use Colab for fast iteration, interactive sessions, and direct file transfer on Linux, macOS, or WSL. Use Kaggle Kernels for long asynchronous jobs and for native Windows machines without WSL, since the Kaggle CLI runs natively on Windows.

Does google-colab-cli work on Windows without WSL?▼

No. google-colab-cli 0.6.0 imports Unix-only termios and tty modules and fails on native Windows. Use Kaggle natively, run the CLI inside WSL, or use the bundled shim only for explicitly chosen non-interactive commands.

How do I install the Kaggle or Colab CLI without administrator rights?▼

Install uv into the user profile with the official PowerShell installer, which needs no admin rights, then run tools via `uvx --from kaggle kaggle` or `uvx --from google-colab-cli colab`. These live in an isolated user cache.

Why is my Kaggle GPU job output missing after the run?▼

Kaggle only exposes files written under /kaggle/working for download. Ensure the script writes artifacts there, then retrieve them with `kaggle kernels output OWNER/slug -p ./output` after the Kernel finishes.

Is it safe to upload data and credentials to Colab or Kaggle?▼

Confirm the data may be uploaded to Google or Kaggle before transfer, and use browser OAuth or provider secret stores. Never commit tokens, credential files, or notebooks containing secrets, and treat remote logs as potentially sensitive.