← ClaudeAtlas

kg-statuslisted

Show where the competition stands — metric, deadline, accepted baseline, best CV, best LB, CV-LB correlation, recent experiments and decisions, top of the backlog, submissions left today — and recommend the next actions.
TranBaDat2607/claude-code-kaggle-grandmaster · ★ 2 · AI & Automation · score 78
Install: claude install-skill TranBaDat2607/claude-code-kaggle-grandmaster
# /kg-status Run kgkit with the Bash tool, as `PYTHONPATH="${CLAUDE_PLUGIN_ROOT}" python -m kgkit <command>`: this command pre-approves that form for the kgkit calls it makes. Submitting, pushing or publishing still asks (so does a PowerShell `$env:` assignment). 1. `python -m kgkit status -n 15` (kgkit home from the session context or `$KGKIT_HOME`). It prints the deadline with days left and the endgame phase (see `final-submission-selection`), submissions logged today (UTC) against the daily limit (plus Kaggle's own count when the last submit printed one) and the cached GPU quota. It first adds to the log the submissions Kaggle lists that the hooks never saw (a script, the website, a teammate) and says whether the count was "checked against Kaggle's list" or is "local log only" (no CLI or login, or `--offline`): trust a local-only count no further than that. 2. If the Kaggle CLI is authenticated: `kaggle competitions submissions <slug> --format json` → the latest scores not yet attached to the ledger. Offer to attach them: `python -m kgkit ledger sync-lb` does it for every submission that names its record; `python -m kgkit ledger lb` does one by hand. 3. If the GPU quota is stale or missing and remote runs are planned: `python -m kgkit gpu quota`. 4. `python -m kgkit backlog list` and CLAUDE.md `## Current state` (`reports/journal.md` for the history). Flag experiments that were run but never decided (no `decision` in the ledger table) and offer