Install
$ agentstack add skill-danielrosehill-claude-data-analyst-plugin-anomaly-analysis ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Anomaly Analysis
Identify significant anomalies in a dataset across three layers: value-level, distribution-level, and relational.
Inputs
- Path to a dataset file or folder.
- Optional: timestamp column name (enables temporal anomaly checks).
- Optional: group-by column (for per-segment anomaly detection).
Recommended CLI tooling
duckdb— percentile, z-score, and windowed queries.uv run --with pandas --with scikit-learn python -c '...'— IsolationForest and LOF for multivariate anomalies.csvstat(csvkit) — quick min/max/null sanity check.
Procedure
Layer 1 — Value-level sanity
For each column:
- Nulls: count and percentage; flag columns >20% null.
- Duplicates: flag rows duplicated on a natural key, or full-row duplicates.
- Impossible values: negative ages, dates in the future, percentages >100, etc. Use column name hints.
- Type coherence: mixed types in one column (e.g. numbers stored as strings with stray text).
Layer 2 — Distribution-level outliers
For each numeric column:
- IQR method: flag values below Q1 − 1.5·IQR or above Q3 + 1.5·IQR.
- Z-score: flag |z| > 3.
- Top/bottom 5: list the extreme values explicitly so the user can eyeball them.
For categorical columns:
- Rare categories (-anomalies.md`:
- Summary: one-line severity (low / medium / high) and headline anomaly count.
- By layer: sections for value-level, distribution, and multivariate.
- Evidence: concrete example rows (with row numbers / keys) for each flagged anomaly.
- Recommendations: which anomalies warrant investigation vs. are likely expected tail behaviour.
Be specific — "17 rows have negative order_total" is useful; "there are some outliers" is not.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: danielrosehill
- Source: danielrosehill/Claude-Data-Analyst-plugin
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.