Data cleaning
AuraScore 81/100

Quantitative Dataset Outlier Triaging and Distribution Normalization Brief

Design a rigorous mathematical triage strategy for handling extreme outliers, distributional skew, and noise in high-dimensional empirical datasets.

Use this template when preparing raw numerical or experimental research data for downstream statistical modeling. It produces a concise outlier treatment and variance-stabilization strategy.

Template

Role: Senior Quantitative Statistician and Data Integrity Specialist

Context

  • Target Domain: {{raw_dataset_domain}}
  • Dimensions and Sample Scale: {{sample_size_and_dimensions}}
  • Suspected Anomaly Profile: {{suspected_anomaly_types}}
  • Distributional Hypotheses: {{target_distribution_assumptions}}
  • Downstream Estimators: {{downstream_analytical_models}}

Task

Synthesize the statistical anomalies within the empirical dataset and construct an actionable outlier triage brief that outlines exact mathematical transformation, robust filtering, and variance-stabilization procedures to support {{downstream_analytical_models}}.

Method

  1. Profile the empirical probability density against {{target_distribution_assumptions}} to detect heavy tails, multi-modality, and heteroskedasticity.
  2. Evaluate {{suspected_anomaly_types}} using robust distance metrics (e.g., Mahalanobis distance, Minimum Covariance Determinant) appropriate for {{sample_size_and_dimensions}}.
  3. Differentiate between measurement artifacts (noise to purge) and valid extreme phenomena (signals to preserve).
  4. Formulate explicit truncation, Winsorization, or robust weighting thresholds for univariate and multivariate outliers.
  5. Select optimal mathematical transformations (e.g., Box-Cox, Yeo-Johnson, log-modulus) to stabilize dispersion across {{raw_dataset_domain}} covariates.
  6. Specify an imputation or deletion protocol for corrupted coordinates that guarantees variance preservation.
  7. Define quantitative pre- and post-cleaning diagnostic tests to verify distributional stability.

Constraints

  • MUST specify formal mathematical criteria (e.g., specific IQR multipliers, Z-score cutoffs, or distance percentiles) for every proposed exclusion.
  • MUST NOT recommend naive row-wise deletion without measuring resulting statistical power loss.
  • Recommendations MUST directly address compatibility with {{downstream_analytical_models}}.
  • Keep the final brief dense, analytical, and under 800 words.

Output format

Provide a structured brief using exactly these sections:

  1. Distributional Diagnostic Summary
  2. Anomaly Classification & Threshold Matrix
  3. Mathematical Transformation & Cleaning Directives
  4. Post-Cleaning Verification Metrics

Self-review

  • Confirm every anomaly type listed in {{suspected_anomaly_types}} has a deterministic handling rule.
  • Verify that power loss and sample degradation risks are explicitly quantified.
  • Check that all mathematical formulas and statistical criteria are unambiguous.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

data-analytics
data-cleaning
complex-reasoning-analysis-math
data cleaning
statistics
outlier detection