kaggle-code-submissionlisted
Install: claude install-skill ssubbotin/kaggle-research-skills
# Kaggle code submission: the traps that cost submissions
Distilled from the working logs of several code competitions. Every rule below is a failure that happened.
Placeholders: `<competition>` is the competition slug, `<owner>` the account that owns the kernel or dataset,
`<kernel>` the kernel slug, `<dataset>` a dataset slug, `<N>` a kernel version number.
## The CLI
- Run the `kaggle` CLI from `~` (a directory named `kaggle` in the cwd shadows the python package).
- Credentials are a bearer token in `~/.kaggle/access_token` (env `KAGGLE_API_TOKEN`); there may be no
`kaggle.json`. Keep the token on the local machine; do not copy it to remote compute hosts.
- `kaggle competitions files <competition>` working means the rules are accepted.
- Forum topics without a browser: `kaggle forums topics show <id>`; untruncated comments via
`POST https://api.kaggle.com/v1/discussions.DiscussionApiService/ListComments` with the bearer token.
## Kernel identity
- `kernel-metadata.json` `id` MUST equal `<owner>/<kernel>` where `<kernel>` is the slug Kaggle derives from
`title` (lowercase, spaces and punctuation to hyphens). Otherwise the first push creates the title-slug kernel
and every later push 409s against a non-existent id, silently (the failure line is not last; `| tail` hides it).
- Copying someone's notebook: pull with `-m`, rename the `.ipynb`, set `id`, `title`, `code_file`,
`is_private: true`, drop `id_no`. Keep `docker_image` pinned if the original pins it (be