cekura-onboarding

Guides new users through Cekura platform setup from agent connection to first verified test result.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up a voice agent testing or observability workflow on the Cekura platform involves many steps — connecting a provider, configuring metrics, generating evaluators, and running a first call — and it is easy to end up with records created but nothing actually verified. This Skill walks a new user through a structured, phase-by-phase onboarding that only ends at a verified working loop: a completed test call with a visible transcript, or an ingested and scored production call. ## Core Features & Use Cases - Two onboarding paths: a testing path (generate evaluators and run simulated calls against the agent) and an observability path (ingest production call logs and evaluate them with metrics). - Provider-aware agent connection: supports VAPI, Retell, ElevenLabs, Synthflow, LiveKit, Pipecat, Bland, KoreAI, Genesys, Cisco, and self-hosted stacks, with auto-import of agent configuration where available and a credential matrix per provider. - Verification gates at every phase: each step has an explicit gate condition (agent created, metrics enabled, evaluators generated, call connected with a two-sided transcript) so misconfigurations surface during onboarding rather than later. - Use Case: A team that just built a voice agent on VAPI signs up for Cekura. The Skill auto-imports the agent from their VAPI API key, confirms default metrics, generates ten behavioral evaluators from the agent's system prompt, runs one test call, and shows the transcript and metric scores — all in one guided session. ## Quick Start Ask your AI assistant to help you get started with Cekura and walk you through connecting your voice agent and running your first test call.

Frequently Asked Questions about cekura-onboarding

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

FAQPage Schema
How do I get started with Cekura for voice agent testing?

Invoke the onboarding flow and choose the testing path. The Skill connects your agent by provider, verifies default metrics, generates evaluators from your agent's system prompt, and runs one verification call with a visible transcript before finishing.

Which voice agent providers does Cekura onboarding support?

Supported providers are VAPI, Retell, ElevenLabs, Synthflow, LiveKit, Pipecat, Bland, KoreAI, Genesys, Cisco, and self-hosted custom stacks. VAPI, Retell, ElevenLabs, Bland, and Synthflow support auto-import of the agent's name, system prompt, and tools via provider API key.

What is the difference between the testing and observability onboarding paths?

The testing path generates evaluators and runs simulated calls against your agent. The observability path ingests real production call logs via upload, webhook, or provider auto-fetch, then scores them with metrics like latency, interruption score, and talk ratio.

Can I onboard a LiveKit or Pipecat agent without the Cekura SDK?

Yes. LiveKit and Pipecat agents connect via a phone number or SIP endpoint with no credentials, or via WebRTC dispatch using provider API credentials. The Cekura SDK is an optional post-onboarding upgrade that adds agent-side traces and tool-call visibility.

Why does onboarding require my agent's full system prompt?

The agent description drives evaluator generation and description-based metrics, so a short summary produces low-quality evaluators. On the testing path the complete system prompt is a hard gate; onboarding pauses until the real prompt is provided or auto-imported.

What happens if the first verification call fails during onboarding?

The failure is surfaced with a diagnosis, such as a wrong phone number, unreachable SIP endpoint, or LiveKit agent name mismatch, and you are offered an immediate fix and re-run. Onboarding never reports success without a completed call and a two-sided transcript.