cxas-composite-voice-agent-optimizer

CXAS Composite Voice Agent Optimizer

This skill audits, optimizes, and remediates Google Cloud CX Agent Studio (CXAS) and Customer Engagement Suite (CES) agent configurations for Gemini Composite V1 voice naturalness, persona stability, and multi-language parity.

All core operations execute purely on local workspace files (app.json, agents/*/instruction.txt, tools/). The cxas CLI can be used to manage local agent workspace (cxas pull, cxas lint, cxas push).

---

When to Use This Skill

Activate this skill when:

• Adapting to Composite Models: Evaluating or migrating an existing or new CXAS agent configuration to Gemini Composite V1.
• Generating Readiness Reports: Generating a prioritized (P0/P1/P2) HTML/Markdown assessment report of required voice adaptations when upgrading CXAS agent to use Gemini Composite V1.
• Optimizing for Composite Models: Optimizing a CXAS agent to use the best practices when using Gemini Composite V1.

When NOT to use this skill:

• Standard text-only chat agents without voice/audio synthesis.
• Non-composite standard TTS/STT pipelines.
• Generic non-voice dialog flow refactoring.

---

⚠️ Fundamental Rule: Non-Destructive Preservation of Existing Instructions

CRITICAL — DO NOT REMOVE EXISTING INSTRUCTIONS: When optimizing an agent for Gemini Composite V1, you MUST NOT delete, remove, or strip existing business logic, domain instructions, taskflows, steps, or operational rules from global_instruction.txt, agents/*/instruction.txt, or tool docstrings.

All adaptations must be strictly additive and non-destructive:

1. Preserve Full Instruction Sets: Retain all existing domain instructions, guardrails, step transitions, and business logic verbatim.
2. Relocate Voice & Speech Guidance to Director's Notes (P0): Identify voice, speech delivery, accent, vocal tone, and acoustic pacing instructions inside global_instruction.txt and agents/*/instruction.txt, migrate/consolidate them into the global Director's Note in app.json (synthesizeSpeechConfigs), and remove them from agent text prompts to prevent context waste and instruction dilution.
3. Rephrase Prohibited Tags Without Deleting Logic: When resolving prohibited platform XML tags (e.g., <context>, <state_update>), rephrase the tag references into plain natural language descriptions (e.g., "system context", "state update") rather than deleting the surrounding rules or instructions.
4. Augment Tool Docstrings Additively (Only if Insufficient): In tools/*/python_function/python_code.py, preserve all existing descriptions, parameter documentation, and implementation details. Only append or integrate explicit When to Call: and When NOT to Call: execution boundaries if the existing docstring or description is missing, ambiguous, or insufficient.
5. Harmonize Conflicting Directives Collaboratively: When resolving contradictory instructions across scopes, ask the user which behavior to preserve and adjust the wording to eliminate the contradiction without deleting core domain logic.
6. Enrich Spoken Cues Incrementally: Add natural voice cues (ellipses ..., brief bridge words like "umm...") into response instructions without altering the core messaging or domain content.