kaggle-clilisted
Install: claude install-skill TranBaDat2607/claude-code-kaggle-grandmaster
# Kaggle CLI / API
## Authentication
- Kaggle CLI 2.x accepts an API token (`KAGGLE_API_TOKEN`, else `~/.kaggle/access_token`, the "Generate New
Token" file), an OAuth login (`kaggle auth login`, stored in `~/.kaggle/credentials.json`), or the legacy
`~/.kaggle/kaggle.json` (`{"username": ..., "key": ...}`) / `KAGGLE_USERNAME` + `KAGGLE_KEY`. On Windows the
folder is `C:\Users\<user>\.kaggle\`.
- **Never print, commit, or paste a credential.** Do not read those files, do not run
`kaggle auth print-access-token`, and never set `VERBOSE` / `VERBOSE_OUTPUT`: with either on, the CLI prints
every request's headers, bearer token included. The plugin's hook blocks all of these, and `kgkit` drops
both variables from its own Kaggle CLI calls. If auth fails, ask
the user to create a token at kaggle.com → Settings → API and place it themselves.
- Your username (for `"id": "<username>/<slug>"` in kernel/dataset metadata): `python -m kgkit whoami`.
It reads `KAGGLE_USERNAME`, the `username` field of kaggle.json, or the `username` line of
`kaggle config view` (which resolves token and OAuth logins), never the key. The hook blocks
other ways of reading those files.
- You must have joined the competition and accepted its rules on the website before downloading
or submitting (403 otherwise) — only the user can do that.
- Check installation: `kaggle --version`; install with `pip install kaggle`.
## Competitions
```bash
kaggle competitions list -s "keyword"