executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
auto-pytorchRoute Auto-PyTorch tabular and forecasting workflows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Auto-PyTorch is an AutoML toolkit for PyTorch-based tabular classification, tabular regression, and time series forecasting. Use this skill when you need to search over pipeline components, tune hyperparameters, inspect ensembles, or validate data shapes before a run.
Use the public package name:
pip install autoPyTorch
pip install autoPyTorch[forecasting]
Use the forecasting extra whenever you need the time-series APIs, validators, or forecasting metrics.
Run the bundled install check script after installation:
python scripts/check_install.py
That script prints the installed version, importability of the public modules, and the most important API signatures.
sub-skills/tabular-automl/Use this route for:
TabularClassificationTask and TabularRegressionTaskget_dataset(...), get_search_space(...), fit_pipeline(...), search(...), and refit(...)include_components, exclude_components, and search_space_updatesshow_models(), sprint_statistics(), and plot_perf_over_time()Read sub-skills/tabular-automl/SKILL.md when the task is about tabular classification or regression, even if the user also wants custom configs, portfolios, or result inspection.
sub-skills/forecasting/Use this route for:
TimeSeriesForecastingTaskstart_times, freq, series_idx, known_future_features, and n_prediction_stepsmean_MASE_forecasting and mean_MAPE_forecastingRead sub-skills/forecasting/SKILL.md when the task names time series forecasting, sequence validation, known future features, or forecast horizon setup.
Most tasks follow the same shape:
If you need the detailed API surface, open references/package-overview.md first for a compact summary, then open the closest sub-skill reference instead of trying to infer it from the router.
feat_types when dtype inference is ambiguous.series_idx, start_times, and known_future_features to preserve sequence identity.search(...) returns the fitted task object after the search completes.fit_pipeline(...) returns a fitted pipeline plus run metadata for a single configuration.predict(...) and score(...) operate on the fitted task or pipeline.Read references/troubleshooting.md for cross-cutting install, import, data-shape, optional-dependency, and package-resolution issues.
The most common problems are:
automl_common submodule when using a source checkoutscikit-learn, torch, or compiled dependency version mismatchesreferences/package-overview.md — compact package API and task summaryreferences/troubleshooting.md — cross-cutting install and import problemsreferences/repo-provenance.md — source commit and package version snapshotreferences/repo-routing-metadata.json — router metadata for managed importsscripts/check_install.py — lightweight install and import smoke checksub-skills/tabular-automl/ — tabular classification and regression workflowssub-skills/forecasting/ — time series forecasting workflows