kg-cvlisted
Install: claude install-skill TranBaDat2607/claude-code-kaggle-grandmaster
# /kg-cv
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).
Arguments: `$ARGUMENTS` (optional strategy override and group column).
Follow the `validation-strategy` skill.
If decisions in this competition are made on a fixed labelled holdout plus the public LB (no K-fold OOF:
e.g. a small expert-labelled set, or an accepted baseline forked from public inference notebooks), do not
invent folds. Record the mode and the holdout labels instead:
`python -m kgkit config validation=holdout+lb holdout_n=<rows> eval_truth=<FILE>:<label cols, comma-separated>`
(plus `eval_groups=<FILE>:<col>` when several rows share a patient/study), so the session brief stops
asking for `data/folds.csv`. Log each candidate with its holdout predictions
(`kgkit ledger add <name> auto --pred <FILE>:<cols>`): the score is recomputed from them and compared,
paired, against the accepted baseline. Do not judge differences by the holdout size alone: two models
scored on the same rows differ far less by chance than one score varies.
1. Determine how train/test were split (recon report, data page, adversarial validation, time
columns, entity ids). State the evidence.
2. Pick the scheme from the decision table; if groups are suspected but not explicit, look for them
(duplicate feature vectors, entity-like