cekura-flag-call-log-failures

Triage production call logs to flag agent failures and compute outcome distributions.

7|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/cekura-ai/cekura-skills --skill cekura-flag-call-log-failures-cekura-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cekura-flag-call-log-failures
Source: https://github.com/cekura-ai/cekura-skills/tree/main/cekura/skills/cekura-flag-call-log-failures
Command: npx skills add https://github.com/cekura-ai/cekura-skills --skill cekura-flag-call-log-failures-cekura-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Voice agent teams need to know which production calls failed, why, and how often, but manually reviewing hundreds of call transcripts is slow and error-prone. This Skill automates the triage of recent Cekura call logs against your KPIs, producing failure rates and a mutually-exclusive outcome breakdown with verbatim evidence. ## Core Features & Use Cases - Failure flagging with evidence: Identifies call IDs that hit each specified KPI or issue, quoting verbatim transcript slices and classifying failures against a taxonomy (loop, hallucination, workflow miss, ASR capture, and more). - Attribution-aware outcome distribution: Buckets every reviewed call into categories like not-answered, vetted, caller-side, or agent-issue, ensuring caller-side endings and recovered calls are not miscounted as agent failures. - Cost-efficient batch analysis: Uses cheap heuristics (call_ended_reason, duration, metric scores) first and only pulls full transcripts for ambiguous candidates, keeping token usage under control. - Use Case: Ask what percentage of the last 100 calls ended before all vetting questions were asked, and receive a report with per-issue failure rates, linked call IDs, and the share of answered calls that are improvable on the agent side. ## Quick Start Analyze the last 100 production calls for agent 1234 and tell me which calls failed to complete vetting and what percentage of answered calls are improvable.

Frequently Asked Questions about cekura-flag-call-log-failures

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find failing calls in my voice agent's production logs?

Provide the agent ID, a window of recent calls, and the KPIs or issues to measure. The skill batches through call logs via the Cekura MCP, classifies each call, and reports flagged call IDs with verbatim evidence and per-issue failure rates.

How to calculate what percentage of calls have a specific agent problem?

Each flagged issue is reported as a count divided by total reviewed calls, or by answered calls if you frame it that way. The denominator is always stated explicitly, and results are marked as audited (metric-evaluated) or heuristic-estimated.

Does call log triage require the Cekura MCP server?

Yes, it reads through Cekura MCP tools including aiagents_retrieve, call_logs_list, call_logs_retrieve, and metrics_list. If these are not connected, the skill stops and directs you to set up the Cekura MCP first.

Why are caller-ended calls not counted as agent failures?

Attribution rules exclude calls ended by the caller or simulated caller, plus recovered calls and legitimate early exits, from agent failure counts. These land in separate outcome buckets so failure rates reflect only issues the agent actually caused.

Can this skill create regression tests from flagged calls?

It does not create scenarios itself; it is strictly read-only triage. After reporting, it offers to hand the flagged call set to cekura-generate-scenarios, which clusters failures and builds one evaluator per pattern.