Skip to content

topprismdata/cultivating-ml-agent / skills/examples/kaggle-oof-lb-validation-protocol

kaggle-oof-lb-validation-protocol

Verified

Use when: (1) Your OOF score improved but LB didn't (or got worse), (2) You need to decide whether to submit based on OOF alone, (3) You're comparing models for ensemble inclusion and unsure which OOF signal to trust, (4) You see OOF/LB gap larger than 1% and don't know if it's overfitting or distribution shift. Covers: 5 sources of OOF/LB gap, the "OOF → LB confirmation protocol" (submit only after OOF + adversarial validation + format check), asymmetric gap patterns (OOF optimistic on small data, pessimistic on large), and the "3-strike rule" (if 3 consecutive OOF improvements don't improve LB, stop tuning and pivot). Validated across 20+ competitions including tabular (House Prices, SST, s6e7), simulation (PTCG), code (ROGII, Biohub, NeuroGolf), and time series.

Security report

Verified

Static analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.

Commit
df4705c431813acf8919cbfb5fbfe8e43fca3e26
Content hash
0bf643805b3a0a25135ecff9acd8d383d5c0aa35514a8935150e1ff467ae1f60
Scanned
2026-11-18
Scanner version
skillxone-scan-1.0.0
Policy version
0.1-draft
Decision
Every required check completed with no open blocking or medium findings.
Verification expires
2026-12-18

Findings (none)

No findings were recorded.

Checks run

  • prompt-injection
  • dangerous-commands
  • credentials
  • network
  • file-access
  • integrity

Checks skipped

  • dependencies: No dependency manifest in the skill directory.
  • gitleaks: gitleaks is not installed on this host.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall