Showing 38941–38970 of 60014 skills
Use when: (1) Entering a Kaggle Code Competition that requires notebooks with no internet access, (2) Need to fork a public baseline that depends on external artifact datasets (pre-trained models, feature matrices, wheels), (3) Your fork fails with "module not found" or "file not found" errors, (4) Need to identify and attach the correct Kaggle datasets as notebook inputs. Key lessons: search kaggle datasets list for artifact bundles, check kernel-metadata.json dataset_sources field, the notebook's find_artifacts() function reveals expected paths. Validated on ROGII (7159→Pipeline A), Biohub (LB810 fork), NeuroGolf (7228 fork).
topprismdata/cultivating-ml-agent
Use when: (1) You need to rapidly iterate across MANY competing approaches in a single Kaggle competition (NeuroGolf-style: 7+ different public kernels forked in <2 hours), (2) You must decide which public dataset/kernel to spend your limited submission quota on, (3) Your highest-scoring submission might be a public dataset's submission, not your own engineered one, (4) You see sub-1.0 "0.0 placeholder" submissions that look like errors but are actually correct. Key lessons: from 7228→7269.68 (+41) in 4 hours via public kernel forking; from 0.0→62.64 in 12h via TensorLiu's BUDGET-FILLING strategy; submission batching is essential to avoid "pending" serialization. Validated against NeuroGolf 2026, AI Agent Security 2026-07, Biohub Cell Tracking (0.0→pending), PTCG AI Battle (final-2 strategy).
topprismdata/cultivating-ml-agent
Use when context window is getting crowded, when dealing with long training logs, or when preparing prompts with mixed-priority content (system / task / skills / examples). Triggers when assembling prompts >4000 chars, or when observing "Lost in the Middle" symptoms (model ignores mid-prompt content).
topprismdata/cultivating-ml-agent
Use when: (1) a new submission scores worse than baseline and the reason is unclear, (2) multiple changes were made simultaneously (new model + new post-processing + new features), (3) need to isolate which component caused a regression, (4) CV improves but LB degrades, (5) comparing "smart" vs "simple" approaches, (6) verifying that model improvements are real vs artifacts of post-processing changes. CRITICAL: Never change more than one variable between submissions without controlled comparison.
topprismdata/cultivating-ml-agent
Use when starting a new ML task that structurally resembles a known competition (recommendation ↔ retail, demand ↔ supply, churn ↔ fraud, segmentation ↔ classification). Triggers when your task feels "not novel" — there is likely a top solution you can borrow features from. Especially valuable at the start of a project before inventing custom features.
topprismdata/cultivating-ml-agent
CV-LB Gap Acknowledgment: CV improvement does NOT equal LB improvement. This is one of the most important MLOps principles. Use when: (1) OOF score keeps improving but LB score plateaus or drops, (2) Spending days tuning hyperparameters without LB improvement, (3) Comparing models on CV only without LB validation, (4) Trusting cross-validation as the "final" metric. Covers the mathematical reasons for CV-LB gap (overfitting to OOF noise, distribution shift train vs test, hyperparameter over-tuning to CV), empirical validation (0.005-0.01 gap observed in tabular competitions), the 5-stage validation pipeline (CV → submission → LB → analysis), when to stop iterating on CV alone, and the 80/20 rule for time allocation between CV optimization and LB validation.
topprismdata/cultivating-ml-agent
Avoid applying domain knowledge constraints that hurt ML model performance. Use when: (1) Considering medical/physical/logical constraints on training data, (2) Adversarial validation AUC changes significantly after applying constraints (>0.10 shift), (3) CV score drops after adding "reasonable" domain rules, (4) Train/test distributions become misaligned after filtering.
topprismdata/cultivating-ml-agent
Diagnose when ensemble/stacking will fail due to high model correlation. Use when: (1) Stacking or ensemble shows no improvement over single models, (2) Considering weighted average of multiple models, (3) Model predictions are nearly identical, (4) AUC/RMS gains plateau despite complex ensembling. Critical for tabular ML competitions where model diversity determines ensemble success.
topprismdata/cultivating-ml-agent
Use when you have run 3+ feature engineering experiments with no improvement, or when distance to theoretical upper bound is <15pp. Triggers when you suspect "I should stop optimizing features and try something else" — the most common failure mode is wasting weeks past the saturation point.
topprismdata/cultivating-ml-agent
Use when: (1) Considering switching from CPU to GPU for a Kaggle competition, (2) GPU quota is running low and you need to prioritize which competitions deserve GPU time, (3) About to start a model training run and unsure if GPU is worth the 30h/week quota cost, (4) Deciding between CPU AutoGluon vs GPU neural network. Provides a 5-gate assessment framework that produces a verdict: READY (GPU will help significantly), MARGINAL (GPU helps but ROI is low), or SKIP (CPU is sufficient). Inspired by NVIDIA's cupynumeric-migration-readiness, adapted for Kaggle GPU quota management.
topprismdata/cultivating-ml-agent
Apply GSD Core's loop-engineering methodology to ML/data-science tasks. Use when: (1) You have a multi-step ML pipeline (data → features → train → verify → submit), (2) Context is growing long and quality is drifting, (3) You want auditable verification at each step, (4) You want fresh-context subagents to handle heavy work without polluting the main session. Validated against: gsd-build/get-shit-done (64K stars, deprecated), open-gsd/gsd-core (canonical, 4.4K stars, active 2026-06).
topprismdata/cultivating-ml-agent
Use when: (1) You have limited daily submission quota and 50+ skill files to explore, (2) Most Kaggle experiments cost 1 quota each but only the 1-2 BEST actually matter for your final score, (3) You waste hours doing redundant experiments because the EXISTING public kernels (rank 4-9 players) have already solved 80% of the problem, (4) You're tempted to re-submit "to see what happens". Key insight from 4+ months, 20+ competitions: **0.6 × BEST_PUBLIC ≥ 0.8 × OPTIMAL_OWN**, i.e. the best public kernel + small tuning > optimal own work in 90% of cases. Most Kaggle competition success comes from picking the right public kernel and spending quota wisely, not from complex custom work.
topprismdata/cultivating-ml-agent
Kaggle竞赛最佳实践和RAG知识库管理。使用时: (1) 开始任何Kaggle竞赛项目前建立规划, (2) 需要查询竞赛策略、获胜方案、特征工程技巧, (3) 需要为竞赛创建NotebookLM知识库。 涵盖完整的竞赛工作流:从数据探索、特征工程、模型训练到提交策略。包含Stage1/Stage2 规则、获胜方案解析、ELO/Massey排名、评分函数优化等核心知识。
topprismdata/cultivating-ml-agent
Use when: (1) Entering a new Kaggle competition and unsure what type it is, (2) Need to choose between forking public kernels vs building custom, (3) Deciding how to allocate submission quota across the competition lifecycle, (4) Determining which evaluation/validation strategy to use. Covers 6 competition types (Standard Tabular, Code Competition, Simulation, Research, Prediction, Playground), each with distinct: submission mechanism, scoring system, public kernel value, GPU requirements, and optimal strategy. Includes a decision tree for first-48h actions and a quota allocation framework. Validated across 20+ competitions Jun-Sep 2026.
topprismdata/cultivating-ml-agent
Prevent wasted research by verifying Kaggle competition data format BEFORE investing in RAG, technical planning, or model architecture design. Use when: (1) Starting any new Kaggle competition, (2) Competition name/size is ambiguous about data format, (3) Planning to do extensive research before implementation, (4) Download size doesn't match expected data structure. Critical for competitions where name suggests one format (e.g., "3D Surface Detection") but actual data is different (e.g., 2D images).
topprismdata/cultivating-ml-agent
Use when looking for top-solution tricks on a Kaggle competition, when needing CV-LB gap discussions, when validating a strategy against community experience, or when seeking hyperparameter advice from competition winners. Triggers on phrases like "what did top scorers do", "CV-LB gap in this competition", "winning trick for X", or when starting any Kaggle competition.
topprismdata/cultivating-ml-agent
Standard Operating Procedure for ANY Kaggle experiment or competition entry. Execute sequentially from Phase 0 to Phase 3. Each phase has explicit checklist items with pass/fail criteria. Covers: memory recall, competition type identification, public kernel evaluation, baseline establishment, controlled iteration, OOF/LB validation, submission format verification, and post-experiment knowledge crystallization. This SOP synthesizes 4+ months and 20+ competitions of experience into a single repeatable workflow.
topprismdata/cultivating-ml-agent
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.
topprismdata/cultivating-ml-agent
Optimal blending strategy for Kaggle competitions: 80/20 rule (re-ranking vs raw). Use when: (1) Re-ranking gives unexpected results, (2) Simple average blending underperforms, (3) Single model dominates ensemble. Avoids the trap of 100% re-ranking or equal-weight ensembles. **UPDATED 2026-06-14**: Added asymmetric-blending principle (30/70 rule) for general tabular ensembles. When one model family dominates (e.g., CatBoost in Spaceship Titanic 0.8124 OOF acc), weight it higher than other families. Validated: 30% Silver + 70% Top-5 = 0.8132 OOF (best on SST V3).
topprismdata/cultivating-ml-agent
Match the submission file format to the competition's evaluation metric BEFORE submitting. For ranking-based metrics (AUC, log_loss, MAP, NDCG, RMSLE) you MUST submit continuous probability/score values, not 0/1 class labels or rounded integers. Use when: (1) Preparing the final submission for any Kaggle competition, (2) AutoGluon's default `predict()` returns class labels for classification (must use `predict_proba()`), (3) Unsure whether to threshold predictions, (4) CV score is excellent but LB score is near-random. Real failure case: S6E2 Heart Disease rerun 2026-06-14 — OOF AUC 0.95554 dropped to Public LB 0.88403 with 0/1 submission, recovered to 0.95357 with probability submission.
topprismdata/cultivating-ml-agent
Systematically replicate and learn from top Kaggle performers. Use when: (1) Stuck at a plateau and need new ideas, (2) Want to understand how top performers achieved their scores, (3) Looking for proven techniques from successful submissions, (4) OOF keeps improving but LB stays same or gets worse. Covers: code analysis workflow, Frequency+Target encoding, Meta-learning with rank-transformed predictions, Temperature Scaling, and Multi-seed training.
topprismdata/cultivating-ml-agent
Use when: (1) You've completed a competition or experiment and want to extract reusable knowledge, (2) Your agent keeps repeating the same mistakes across competitions because lessons weren't crystallized, (3) You have 50+ memory files but can't find relevant knowledge when starting a new task, (4) You need to decide what to remember vs what to forget. Covers the complete crystallization cycle: Experiment → Identify Outcome → Extract Pattern → Classify (feedback/ learned/project/reference) → Store with triggers → Activate on match. Includes the "3-layer architecture" (L1 core, L2 domain skills, L3 cross-domain principles) and the "forgetting protocol" for stale knowledge. Validated across 4+ months, 20+ competitions, 109+ crystallized memories.
topprismdata/cultivating-ml-agent
Use when: (1) Entering an LLM-based Kaggle competition (open-source model required, prompt engineering, few-shot), (2) Need to choose between base models (Qwen, DeepSeek, LLaMA), (3) Designing a prompt strategy (zero-shot, few-shot, chain-of-thought), (4) Deciding whether fine-tuning is worth the GPU cost vs prompt engineering alone, (5) Setting up closed-book inference (no RAG, no internet). Covers the full pipeline: base model selection → prompt engineering → few-shot curation → evaluation → (optional) SFT/PEFT → submission. Inspired by NVIDIA's nemotron-customize pipeline structure, adapted for Kaggle LLM competition constraints.
topprismdata/cultivating-ml-agent
Use when exploring hyperparameter combinations for ML models, when doing Top-1% push on Kaggle, when grid search is too expensive, or when needing systematic exploration of pipeline variants. Triggers for neural architecture search, ensemble weight tuning, or feature subset selection.
topprismdata/cultivating-ml-agent
Use when extracting entities and relationships from text, when building dynamic knowledge graphs, when wanting to upgrade from static OKF to entity-aware memory, or when analyzing papers/discussions for concepts. Triggers when ingesting new papers, processing Kaggle writeups, or when existing skills can't capture connections between concepts.
topprismdata/cultivating-ml-agent
Use when context window is getting crowded, when agent needs to recall past experiences, or when starting a long-running task that spans multiple sessions. Triggers when you have 43+ skills and can't fit them all in context, when you need to decide "what should be in working memory right now", or when persisting new learnings for future sessions.
topprismdata/cultivating-ml-agent
Use when designing a multi-agent system, when a single agent has too many responsibilities, when planning complex ML pipelines, or when observing "agent attention fragmentation" symptoms. Triggers when a task involves planning + coding + review steps.
topprismdata/cultivating-ml-agent
Use when: (1) Competing in ONNX-based competitions (NeuroGolf, model compression), (2) Need to design minimal neural networks as ONNX graphs, (3) Want to replace verbose agent-generated circuits with compact hand-designed nets. Key principles: single-node graphs have zero memory cost (output is free), Conv is a linear classifier (cannot separate nonlinear rules), Gather implements color permutations (10 params), use LogisticRegression to solve Conv weights for local 3×3 rules. Sparse initializers are rejected by ONNX strict checker for Conv nodes. Validated on NeuroGolf 2026 (7228 baseline, independent toolkit).
topprismdata/cultivating-ml-agent
Per-category/per-family models can produce WORSE leaderboard scores than a single global model, even when per-category CV is better. Use when: (1) Considering training separate models per product category/family/store in tabular competitions, (2) Per-category CV improves but LB degrades, (3) Each category has <100K rows from a larger dataset. Covers data volume thresholds, hybrid fallback strategies, and when per-category modeling is appropriate vs counterproductive.
topprismdata/cultivating-ml-agent
Progressive verification methodology for debugging complex systems. Use when: (1) Facing mysterious crashes or errors with no clear cause, (2) System works in some environments but not others, (3) Multiple potential failure points exist, (4) Need to isolate whether issue is environment configuration vs code bug. Core principle: Start with simplest test, gradually increase complexity to pinpoint exact failure point.
topprismdata/cultivating-ml-agent