cekura-personality-design

Configure simulated caller personalities for voice agent testing on the Cekura platform.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Voice agent tests often fail silently because voice-layer behaviors like accents, interruptions, background noise, and idle timing are written into evaluator instructions where they have no effect. This Skill routes each request to the correct layer and guides choosing, forking, creating, and patching Cekura personalities so the simulated caller actually sounds and behaves as intended. ## Core Features & Use Cases - Personality vs. Evaluator Routing: Classifies each request by duration — call-wide traits go to the personality, one-moment behaviors go to evaluator instructions, and post-call judgements go to metrics. - Accent and Voice Resolution: Resolves accent requests to concrete voice selections using the ElevenLabs and Cartesia voice catalogs, since accent is a read-only label derived from voice_id and provider. - Choose, Fork, Create Workflow: Prefers existing personalities, forks shared predefined ones before patching, and creates from scratch only when nothing fits, with read-back verification of derived accent and gender. - Use Case: A user says the testing agent keeps asking "are you still there?" mid-test. The Skill identifies the default 10-second idle timeout as the cause and raises message_plan.idle_timeout_seconds on an org-owned personality. ## Quick Start Ask the assistant to create a Cekura personality with an Indian-accented caller who interrupts frequently for your voice agent test suite.

Frequently Asked Questions about cekura-personality-design

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

FAQPage Schema
How do I create a custom caller personality in Cekura?

First list existing personalities with personalities_list filtered by language, then fork a close match or create from scratch with name, prompt, voice_id, voice_model, background_noise, and language. Always send provider alongside voice_id and verify the result with personalities_retrieve.

How do I change the accent of the Cekura testing agent?

Accent is a read-only label derived from the voice, so you change it by selecting a different voice_id. Query personalities_elevenlabs_voices or personalities_cartesia_voices for the target language, pick a voice with the matching accent, and patch the personality with that voice_id and provider.

Why doesn't writing 'speak with an accent' in evaluator instructions work?

Evaluator instructions cannot reach the voice layer, so accent, interruption, volume, silence, and noise instructions change nothing about the audio while the run still passes. Call-wide voice behaviors must be set on the personality instead.

What is the difference between a personality and an evaluator in Cekura?

A personality defines who is calling and how they sound across the whole call, including voice, language, speed, and background noise. An evaluator defines what the caller tries to accomplish in one test, including its turns, conditions, and expected outcome.

Why does the Cekura testing agent keep asking if I'm still there?

The idle timeout defaults to 10 seconds and fires regardless of instructions. Raise message_plan.idle_timeout_seconds on a personality your organization owns, or use a hold step in the evaluator for a bounded scripted pause.

Can I patch a predefined Cekura personality directly?

No, globally available predefined personalities are shared and read-only. Fork one into your project with personalities_fork_create, then apply changes to the fork with personalities_partial_update so other organizations are unaffected.