kg-postmortemlisted
Install: claude install-skill TranBaDat2607/claude-code-kaggle-grandmaster
# /kg-postmortem
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).
Competition: `$ARGUMENTS` (default: from `.kaggle-gm/competition.json`).
Every score, rank and final pick below comes from a command's output. Never from notes, memory or the
workspace docs: the endgame often left them wrong.
1. `python -m kgkit ledger sync-lb`: one read of Kaggle's list attaches the public and private score of every
submission whose description or file name gives a ledger id. It lists the submissions it could not link.
Link the ones you can identify with `python -m kgkit ledger lb <id> <public> <private>`, and say which you could
not.
2. `python -m kgkit final`: the outcome. It shows the finals, or the pool Kaggle picked from when nothing was
selected, with their private scores and which of them the team score matches. It also shows the team's
private and public rank, the medal zone (computed from Kaggle's table, not read from the site: say so), how
many teams share our shown score and whether a medal cut-off falls inside that tie, the teams per score within
10 display units of ours with the cut-offs marked, and the best private score of any submission. It caches the
private board for step 3. Was our final pick our best private? If not, by how much? When a crowd of te