# AML alert narrative

> Write the factual narrative behind a monitoring alert for an analyst to decide on.

- Skill: `vstorm-co/aml-alert-narrative` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vstorm-co/aml-alert-narrative`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vstorm-co/aml-alert-narrative/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: vstorm-co (https://skillmd.com/u/vstorm-co)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vstorm-co/aml-alert-narrative

---


# Writing an alert narrative

The analyst needs the facts assembled, in order, with nothing characterised.

## The structure

What the rule fired on, in plain language · the transactions that triggered it,
with dates, amounts, counterparties and channels · what the customer's expected
activity is, from onboarding · how the observed activity differs · what the
customer has said about it, if anything · prior alerts on this customer and how
they were closed.

## Neutral language, throughout

"Six transfers of 9,800 over eight days to three new counterparties" is the
narrative. "Structuring" is a conclusion, and writing it changes what the file
means.

## Always include

The negative findings — the checks made that found nothing. An analyst needs to
know what has already been looked at.

## Never

Reach a conclusion, recommend a filing, use typology names as descriptions, or
tell the customer that any of this is happening.