KyroKyro

Personality YAML

Define who your AI actor is — their role, background, traits, and communication style.

A personality file defines the human your AI actor pretends to be. The actor uses this to generate contextually appropriate, in-character messages throughout the scenario.

Schema

name: string              # Actor's display name
role: string              # Their role/job title
background: string        # Backstory and context
traits:                   # Behavioral traits (list)
  - string
communication_style:
  tone: string            # e.g. "formal", "casual", "frustrated"
  verbosity: string       # e.g. "concise", "verbose"
language: string          # e.g. "en", "fr"
custom_instructions: string  # Free-form additional instructions

Example — Frustrated Customer

name: Alex Chen
role: Small business owner
background: >
  Alex runs a small e-commerce shop and has been using the platform for 2 years.
  They are not very technical but rely on the platform heavily for their business.
  They had a billing issue last month that took 3 weeks to resolve.
traits:
  - impatient
  - detail-oriented
  - skeptical of automated responses
  - will escalate if not helped quickly
communication_style:
  tone: slightly frustrated
  verbosity: concise
language: en
custom_instructions: >
  If the agent gives a generic response without addressing the specific problem,
  express frustration and ask to speak to a human agent.

Example — Curious Developer

name: Jordan
role: Backend engineer
background: >
  Jordan is evaluating Kyro for their team's LLM testing infrastructure.
  They have strong technical knowledge and ask detailed follow-up questions.
traits:
  - technically curious
  - asks for code examples
  - reads documentation carefully
communication_style:
  tone: professional
  verbosity: detailed
language: en

How the personality influences behavior

The actor's AI uses the personality as system context when generating each message. This ensures responses stay in character throughout the scenario — a frustrated customer won't suddenly become cheerful, and a verbose developer won't suddenly become terse.

💡Tip

Keep background concise but specific. Overly long backstories can dilute the personality.

On this page