← ClaudeAtlas

kg-finallisted

Choose the final Kaggle submissions to maximise expected private leaderboard score — evidence table, LB noise estimate, CV-vs-LB weighting, hedge selection and robustness checks.
TranBaDat2607/claude-code-kaggle-grandmaster · ★ 2 · AI & Automation · score 78
Install: claude install-skill TranBaDat2607/claude-code-kaggle-grandmaster
# /kg-final 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). Follow the `final-submission-selection` skill. 1. Evidence table from `python -m kgkit ledger best -n 20` + all submissions with LB scores: id, CV ± std, honest blend CV, public LB, risk elements, correlation with the top candidate. Records tagged `public-lb-fitted` (files tilted toward an estimate of the public labels; `kgkit status` marks them `[public-LB fitted]`) go in their own group, "display only": never pick 1, pick 2 or the hedge. A file that is fitted but not tagged yet: `python -m kgkit ledger tag <id> public-lb-fitted`. Blends whose weights or members were picked by comparing public scores get `public-tuned` (`kgkit final` lists groups of blend variants that look probed): mark them `[public-tuned]` in the table. 2. Estimate public-LB noise per pair of candidates (`python -m kgkit ledger compare <a> <b> --public-n <rows>`: paired SE of their LB gap; not the SE of one score, see `cv-lb-debugging`) and the CV-LB correlation. LB-only records (blends with public files) are left out of that correlation; in a `holdout+lb` workspace compare candidates on their stored holdout predictions (`kgkit status` prints the measured paired noise). A pair with an LB-only record has no OOF to r