Showing 46051–46079 of 46079 skills
Control Godot Editor via OpenClaw Godot Plugin. Use for Godot game development tasks including scene management, node manipulation, input simulation, debugging, and editor control. Can modify, save, and delete scenes/nodes and capture project metadata and screenshots — destructive operations should be confirmed with the user. Use only on explicit Godot Editor requests like inspecting scenes, creating nodes, taking screenshots, testing gameplay, or controlling the editor, in trusted local projects.
TomLeeLive/openclaw-godot-skill
Correct implementation of adversarial validation for Kaggle competitions. Use when: (1) Selecting training samples that match test distribution, (2) Reducing synthetic data artifacts by filtering, (3) Preparing data subsets for better generalization. Covers train vs test classification, sample selection method, and common pitfalls.
topprismdata/cultivating-ml-agent
Agent Nurture Framework: a systematic methodology for training AI agents from novice to expert through conversational knowledge crystallization. Use when: (1) designing an agent training pipeline, (2) consolidating fragmented skills into organized knowledge architecture, (3) integrating external learning resources (books, notebooks) into agent memory, (4) measuring agent capability growth over time. Based on 2 months of real-world experimentation with 156 skills and 51 memory documents across multiple ML competitions and projects.
topprismdata/cultivating-ml-agent
Use when: (1) Starting a long-running experiment that may span multiple sessions/disconnects, (2) Resuming work after a break and needing to recover context, (3) Handing off to another agent or session, (4) You realize you've lost track of what was tried and why. Provides a structured 4-file session memory system that captures goal, timeline, files touched, and handoff instructions — lightweight (pure markdown, no infrastructure), works alongside AutoMem or standalone. Inspired by NVIDIA's nemo-rl-session-memory, adapted for Kaggle competition workflows.
topprismdata/cultivating-ml-agent
Use when encountering a new ML technique not covered by existing 43+ skills, when needing citations for a paper/report, when comparing recent (last 6 months) approaches to a known problem, or when the existing knowledge feels stale. Triggers on phrases like "latest paper on X", "SOTA in Y", "what does the literature say about Z".
topprismdata/cultivating-ml-agent
AutoGluon-First Strategy: Always run AutoGluon `best_quality` preset as the first step in any tabular ML competition (5-15 min baseline). Validated 3/4 times vs manual ensembles on small/medium tabular datasets. Use when: (1) Starting any new tabular competition, (2) Need a strong baseline in <15 minutes, (3) Manual GBDT work takes hours but gives similar results, (4) Want to focus manual effort on complementary techniques (deep learning, external data, special features) rather than reimplementing what AutoGluon already does automatically. Covers 5 core reasons for success (multi-algorithm diversity, multi-level stacking, automated preprocessing, bagging/multi-fold, Bayesian optimization), when to AVOID AutoGluon (text/image data, multi-output regression, >1M rows with limited RAM), and how to use it as a Silver signal in custom pipelines.
topprismdata/cultivating-ml-agent
AutoGluon preset selection strategy: when to use medium/good/high/best_quality, when EDA is unnecessary, and how to tune within a preset. Validated on s6e7 (AG high_quality 600s → OOF=0.8739, LB=0.87458, gap=0.0007 — perfect alignment). Use when: (1) Deciding which AutoGluon preset to start with, (2) Wondering whether to do manual EDA before fitting, (3) Wanting to know which hyperparameters to tune first, (4) Deciding time budget for tabular training. Differs from `autogluon-first` (which says "just use best_quality"): this skill explains the preset tradeoffs and where manual intervention pays off vs not.
topprismdata/cultivating-ml-agent
AutoGluon TimeSeriesPredictor: special API and presets for time series forecasting (different from TabularPredictor). Validated on Store Sales (N=3M, 33 families × 54 stores × 1684 days): AG 1.5 Chronos-2 + Chronos + onpromotion covariates → **LB RMSLE 0.39525** (best historical, vs AG 1.4 0.41852, vs manual 3.0+). Use when: (1) Working on time series competitions (forecasting), (2) Have multi-series data with optional covariates (promotions, holidays, prices), (3) Want AG 1.5 Chronos-2 zero-shot OR fine-tuned, (4) Need to bypass HF download errors. Differs from `autogluon-preset-strategy` (which covers TabularPredictor). Key breakthrough: using `model_path=LOCAL_PATH` to bypass `hf-mirror.com` download errors.
topprismdata/cultivating-ml-agent
CatBoost-First Strategy: When manual GBDT work is needed, start with CatBoost (not LightGBM or XGBoost). CatBoost has native categorical feature handling, robust to overfitting, and consistently outperforms other GBDTs on small/medium tabular datasets. Use when: (1) AutoGluon is not available or too slow, (2) Need to add CatBoost as a Silver signal in custom pipeline, (3) Manual GBDT baseline required, (4) Categorical features are dominant (more than 5-10 high-cardinality columns). Validated: Spaceship Titanic 0.8124 OOF acc (vs XGBoost 0.8003, LightGBM 0.8048), House Prices V17 CatBoost alone stronger than XGBoost. Covers native categorical handling, ordered boosting, robust default parameters, ensemble sweet spot (5 CatBoost variants > 10+ same-family variants).
topprismdata/cultivating-ml-agent
Extract reusable knowledge from work sessions into new Claude Code skills. Use when: (1) /claudeception command to review session, (2) "save this as a skill" or "extract a skill", (3) "what did we learn?", (4) After non-obvious debugging, workarounds, trial-and-error discovery, or counterintuitive solutions. Do NOT trigger for routine fixes or straightforward tasks with obvious solutions.
topprismdata/cultivating-ml-agent
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