sw-triage
Use when the user reports a bug, failure, error, regression, incident or unexpected behavior in a Superwiki project and wants to know whether it happened before, what was learned, or what the likely causes are, or invokes sw-triage.
38,472 Skills
Search uses this published catalog; rankings and counts are snapshots.
Use when the user reports a bug, failure, error, regression, incident or unexpected behavior in a Superwiki project and wants to know whether it happened before, what was learned, or what the likely causes are, or invokes sw-triage.
Use when a Superwiki task's work is finished and it has to be closed with evidence, when the user asks what a task did, what it changed or how it was verified, or invokes sw-verify with a task id. sw-implement runs it as the gate before `done`.
Use when the user wants to see, open, browse or visualize the Superwiki vault, task board, dependency waves or wiki in a browser, or invokes sw-view.
Combinatorial Purged CV generates a distribution of backtest paths instead of a single estimate. Use when quantifying strategy robustness and overfitting probability.
Adjust the Sharpe ratio for multiple testing bias when selecting from many trials. Use when reporting strategy performance after parameter or model search.
Transition from backtest to live trading with zero code changes. Use when deploying a validated strategy to paper or live trading via broker APIs.
Test portfolios against historical crises and hypothetical shocks. Use when quantifying tail risk before deployment or during risk reviews.
Prepare a project for public collaboration — license, code of conduct, docs, branch rulesets, templates, and git-cliff releases. Use when open-sourcing a repository, onboarding contributors, or cutting a tagged release.
Convert notebook prototypes into a distributable Python package with a src layout, a domain/io/application split, and validated OmegaConf plus Pydantic configuration. Use when moving code out of notebooks or designing entrypoints.
Make an ML system a glass box with reproducible runs, MLflow dataset lineage, drift monitoring, alerting, and SHAP explanations. Use when a deployed model needs traceability, monitoring, alerting, or explanation.
Add the validation layers that gate a merge — ty typing, Ruff linting, pytest coverage, structured logging, and the trivy, pip-audit, and gitleaks scans. Use when hardening code quality or wiring the mise run check task.
Always invoke before answering any request to create, compare, design, or review a user-facing map, even if the request is terse or underspecified. Covers publi
Change analysis, once the observations are comparable. Not for cases whose blocker is comparability itself: mixed sensors, product levels or processing baseline
Invoke before recommending, training, or auditing a neural method for geospatial imagery, including vision transformers, U-Net/DeepLab/SegFormer, object detecti
Route genuinely ambiguous or multi-stage geospatial work across specialist skills while enforcing shared CRS, validity, leakage, units, verification, and reprod
Turn scattered point measurements into continuous surfaces with quantified uncertainty: variogram modeling, ordinary/universal/regression kriging, IDW, and spat
Catalog captured:2026-11-21