Kaggle
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is transparent about being a Kaggle integration, but it can automatically mutate your Kaggle account and set up recurring badge/streak activity, so it warrants review before use.
Install only if you want broad Kaggle automation. Start with credential checks and dry-runs, review the badge collector scripts before running phases, avoid `--phase all` unless you understand every account action, and do not enable Phase 5 recurring automation unless you know how to disable it.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent could create competition submissions under the user's Kaggle account, affecting account history, leaderboard participation, or platform reputation.
The badge collector can submit to Kaggle competitions automatically once a phase is run, which is a high-impact account action without visible per-submission confirmation in the script.
"competitions", "submit", "-c", "titanic", "-f", str(submission_file), "-m", "Badge Collector automated submission"
Do not run badge phases or full workflows unless you explicitly want those account actions; use dry-run first and require user confirmation before any submission or publishing action.
The skill may set up recurring activity that continues to log in or submit on Kaggle after the initial request.
The skill documents scheduled daily automation for badge streaks, which is persistent behavior beyond a single interactive task.
using kagglehub, kaggle-cli, Playwright, and cron/launchd automation ... Phase 5 | Streaks ... Setup only (runs daily)
Review the Phase 5 script before running it, confirm where cron/launchd jobs are installed, and ensure there is a clear way to disable or remove them.
Anyone or anything with access to those credentials may be able to act as the user on Kaggle.
Kaggle credentials are expected for this integration, but they authorize actions on the user's Kaggle account and are stored in local credential files.
Store your API token in `~/.kaggle/access_token` (recommended) or as an env var ... optionally `.env` and `~/.kaggle/kaggle.json`.
Use only the credentials needed, keep them out of shared repositories, and revoke or rotate the Kaggle token if you no longer trust the environment.
Users may need to rely on local scripts and manually installed dependencies without the protection of a pinned, reproducible install process.
The registry does not provide a pinned install spec or verified source provenance, even though the skill includes runnable helper scripts and references third-party Python packages.
Source: unknown ... Install specifications: No install spec — this is an instruction-only skill.
Verify the GitHub source, inspect scripts before running them, and install dependencies in an isolated environment.