What problem does it solve? Compliance analysts reviewing transaction monitoring alerts need a complete, ordered account of the facts, but poorly written narratives that jump to conclusions or omit negative findings distort the decision and create regulatory risk. ## Core Features & Use Cases - Structured fact assembly: Organizes the narrative around what the rule fired on, the triggering transactions with dates, amounts, counterparties and channels, expected activity from onboarding, observed deviations, customer explanations, and prior alert history. - Neutral language enforcement: Keeps the narrative descriptive (e.g., "six transfers of 9,800 over eight days to three new counterparties") and excludes conclusions, typology labels, and filing recommendations. - Negative findings inclusion: Records the checks that found nothing so the analyst knows what has already been examined. - Use Case: A transaction monitoring rule flags a customer for repeated sub-threshold transfers; use this Skill to draft the alert narrative an analyst can decide on without the writer having pre-judged the outcome. ## Quick Start Write the alert narrative for the attached monitoring alert, covering the triggering transactions, expected versus observed activity, prior alerts, and all negative findings.
