Detecting Data Anomalies

Positioning

Treat this skill as an explicit/manual helper. In governed ML routing, anomaly-detection ownership normally belongs to anomaly-detector.

When to Use

Use this skill when:

• Reviewing outlier transactions, fraud candidates, sensor spikes, or rare failures
• Comparing isolation forest, one-class SVM, LOF, or threshold-based anomaly workflows
• Turning suspicious records into a shortlist for human inspection

Not For / Boundaries

• Null/duplicate/schema/range validation: use data-quality-checker
• Full model training or end-to-end pipeline ownership: use training-machine-learning-models
• Publication-grade figure production: use scientific-visualization

Typical Outputs

• Candidate anomaly-detection methods and thresholds
• A review checklist for false positives and false negatives
• Suggested tables or plots for the suspicious subset

Related Skills

• anomaly-detector as the governed routed owner
• creating-data-visualizations after anomalies are identified