计划执行与检查节点
executing-plans
按既定实施计划完成工作,保持过程检查和反馈。
mljar-supervised【效率与协作】Use MLJAR AutoML for tabular classification, regression, fairness-aware training, reports, persistence, and generated Mercury apps.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this repo skill when a task involves mljar-supervised, supervised.AutoML, MLJAR AutoML, automated tabular machine learning, MLJAR reports, fairness-aware AutoML, or generated Mercury prediction apps.
MLJAR Supervised trains supervised AutoML pipelines for tabular binary classification, multiclass classification, and regression. It handles common preprocessing, model search, reports, explainability outputs, fairness options, persistence, and app generation through the Python package imported as supervised.
Confirm the package is installed and importable:
from supervised import AutoML
print(AutoML)
For a more detailed local check, run scripts/check_mljar_supervised_install.py.
Identify whether the user wants to train a model, prepare data, inspect an existing run, add fairness constraints, or build an app.
Route to the focused sub-skill below before giving detailed API, data, report, or deployment instructions.
Keep user examples bounded: disable expensive feature engineering and explanations for smoke checks; use larger Perform, Compete, or Optuna runs only when the user accepts the runtime.
| User intent | Read |
|---|---|
Train/configure AutoML, choose mode, algorithms, validation, metrics, time limits, ensembling/stacking, predict/score/retrain | training-core |
Prepare X, y, sample_weight, custom CV, missing/categorical/text/datetime columns, target inference, preprocessing and feature-engineering flags | data-preprocessing |
Inspect results_path, load saved runs, use leaderboards, reports, structured reports, explainability artifacts, SHAP/importance/learning curves, persistence | artifacts-reports |
Configure fairness-aware training with sensitive_features, fairness metrics, thresholds, privileged/underprivileged groups, fairness reports | fairness-workflows |
Generate app files, preview locally with Mercury, or prepare guarded publishing with app(), local_app(), publish_app() | app-deployment |
mljar-supervised; import name: supervised.supervised.AutoML.Explain, Perform, Compete, and Optuna.Baseline, Linear, Decision Tree, Random Forest, Extra Trees, LightGBM, Xgboost, CatBoost, Neural Network, and Nearest Neighbors.Read references/package-overview.md for install prerequisites, high-level capabilities, optional dependencies, and safe smoke-test strategy. Read references/troubleshooting.md for cross-cutting install/import/dependency failures.
AutoML(mode="Explain", algorithms=["Baseline", "Decision Tree"], explain_level=0, train_ensemble=False, stack_models=False, golden_features=False, features_selection=False, total_time_limit=30) and a disposable results_path.mode="Perform", set a realistic total_time_limit, and keep results_path stable for later reports and reload.mode="Compete" or mode="Optuna" only after discussing runtime, validation, stacking, and per-algorithm tuning budgets.AutoML(results_path="..."); do not load learner files directly unless a sub-skill explicitly says why.fit(..., sensitive_features=...) and choose task-compatible fairness metrics.automl.app() to create files first; do not start Mercury or publish without explicit user approval.scripts/check_mljar_supervised_install.py: import/version/signature and optional dependency probe.sub-skills/training-core/scripts/mljar_automl_smoke.py: tiny synthetic training/prediction smoke.sub-skills/data-preprocessing/scripts/inspect_preprocessing_behaviour.py: lightweight preprocessing utility checks.sub-skills/artifacts-reports/scripts/structured_report_smoke.py: tiny structured-report and reload smoke.sub-skills/fairness-workflows/scripts/fairness_smoke.py: tiny fairness-aware fit and report signal check.sub-skills/app-deployment/scripts/generate_app_workspace_smoke.py: tiny app-workspace generation check without serving or publishing.Read references/repo-provenance.md before deciding whether this skill is current for a checkout. If the package version, commit, public AutoML signatures, docs, examples, or test-backed behavior changed, run refresh-repo-skill instead of relying on this snapshot.