flag-call-log-failures

Go through an agent's recent production call logs and produce three things:

1. Flagged calls — the call IDs that hit each specified KPI/issue/goal failure, with verbatim evidence.
2. Failure rates — what percentage of all reviewed call logs each failure represents.
3. Outcome distribution — every remaining call bucketed into a mutually-exclusive outcome taxonomy (e.g. not-answered / vetted / non-vetted caller-side / non-vetted agent-issue), with per-bucket percentages, so the flagged failures are framed against the whole population.

It is the triage front-end: hand the flagged set to cekura-generate-scenarios to build evaluators, or give the user the distribution for a customer-facing quality report.

This skill is strictly read-only — it never creates, updates, or deletes anything.

The single most important job is attribution: a call is an agent failure only when the agent under test caused it. Caller-side endings, simulated-caller disconnects, and recovered calls must NOT be counted as agent failures — they belong in their own buckets.

Step 0 — Prerequisites

Reads through the Cekura MCP. Confirm these are present: