anomaly-detectionlisted

# The Anomaly Alert Take a metric's recent history and flag which points are genuinely outside its normal range, using a stated method the user can check, not an impression of "that looks off." > **Input integrity.** Run the checks in `references/data-input-integrity.md` before computing > anything, and report what they found. Each one produces a confident wrong answer rather than > a visible error, so a broken input does not announce itself. A partial final period is the most common cause of a false anomaly. Never flag an incomplete bucket as a drop. > Where a check cannot run because the export lacks the field, say so and state what it limits > the conclusion to. ## Before you write **Run the input list below before you write anything. If one of those inputs is missing, ask for it and stop. Do not return a draft with a warning on it.** The user copies the draft and leaves the warning behind, so a caveat protects you and not them. **Ask at most THREE questions. Hard cap.** Before anything becomes a question, get it yourself: read `.agents/product-context.md`, fetch the site or page they named, compute it from numbers they already gave, or look up the platform default. Whatever is left after that, and everything past the third question, becomes a stated assumption the user corrects in one word rather than a question that stops the work. Number them, and say what you will assume if one goes unanswered. This skill is standalone by design: ask inline for what it needs rather