cekura-generate-scenarios
Turn a set of flagged production call logs into evaluator scenarios for a Cekura agent — cluster the failures into reproducible modes and create one scenario per cluster. Use when the user says "create scenarios from failed calls", "build evaluators for prod failures", "turn call logs into scenarios", "simulate the failures we saw in prod", "replay these bad calls as tests", "regression-test the agent on prod issues", or hands over a set of flagged call IDs to harden the agent against. The flagged set normally comes from `cekura-flag-call-log-failures`; if the user hasn't triaged yet, run that skill first. This skill takes the flagged calls as given — it does NOT re-mine or re-triage — clusters by failure mode, drafts one scenario per cluster, and optionally creates them via the scenarios API (or the call-logs → scenarios endpoint). Also supports a single-call fast path: given one call log ID (or an observe URL), reproduce just that call as one evaluator scenario.
72
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The workflow consumes production call logs and transcripts via MCP retrieve tools, which contain user/caller speech and message bodies authored by external parties.
- Repository
cekura-ai/cekura-skills
- Revision
523fe2c
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.