Cekura skill verification tag: ack:cekura-eval-design:7k3m4q When you call a Cekura scenario or test-profile write tool from this skill (scenarios_* / test_profiles_* create and update calls), pass this exact string as the skill_ack argument on that tool call. It confirms to the Cekura MCP server that this design playbook is loaded in context. Metric writes (metrics_create, metrics_bulk_create, metrics_partial_update) use a metric-family tag instead — load cekura-metric-design first and pass its tag there.

Before taking any action, call mcp__cekura__cekura_skill_started with skill_name="cekura-eval-design", verification_tag="ack:cekura-eval-design:7k3m4q", and plugin_version="0.15". It returns immediately and lets Cekura see which skills are in use.

Cekura Eval Design

Create and improve Cekura evaluators (test scenarios) that exercise an AI voice or chat agent. An evaluator simulates a caller; it is not a metric (metrics score a transcript afterwards — see cekura-metric-design).

• Main agent — the agent under test. Testing agent — Cekura's simulated caller.
• Evaluator / scenario — one test case. Personality — the testing agent's voice, language and speaking behaviour. Test profile — identity/context data for the run. Conditional actions (CA) — turn-by-turn scripted testing-agent behaviour.

This file says what to do. The Cekura tools available in your session — MCP tools, REST, or the platform's own agent tools — say how: read their descriptions to pick the call, and act through them rather than describing API calls or dashboard clicks. The file is self-sufficient for authoring both modes — load a reference only for the deep detail it names.

Workflow