← ClaudeAtlas

kg-grindlisted

Autonomous improvement loop — repeatedly pick the highest-value idea from the backlog, run it as a disciplined experiment against the accepted baseline, decide with a paired comparison, update the backlog, and re-check the CV for overfitting, within a time or experiment budget.
TranBaDat2607/claude-code-kaggle-grandmaster · ★ 2 · AI & Automation · score 81
Install: claude install-skill TranBaDat2607/claude-code-kaggle-grandmaster
# /kg-grind — autonomous grandmaster loop 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). Budget / focus: `$ARGUMENTS` (default: 6 experiments, no specific focus). If the target is a public rank or score ("public top 10", "LB 0.965"), say once that a gain fitted to the public LB has zero expected private value. Grind toward the honest equivalent instead: a validation gain over the accepted baseline beyond the paired noise, which `kgkit status` reports. The loop never fits or probes the public LB. ## Guardrails - **Never submit to Kaggle** unless the user explicitly authorised autonomous submissions in this request; prepare and validate submission files instead. - Never modify `data/` or the frozen folds; never delete ledger entries, backlog items or artefacts. - Commit code at natural points (each record keeps the exact code it ran from either way); one hypothesis per experiment, behind a flag of the existing script, never a copy of it; everything logged and decided (a sweep at once: `kgkit ledger decide 12..20 discard "<why>"`); probes and logs in `work/`. - Stop early and report if: a comparison is flagged as a suspicious jump (run `validation-auditor` first), repeated crashes, disk/GPU memory issues, or the budget is spent. ## Loop 1. **Orient**: `python -m kgk