Coding agents

Prepare

Install the CLI first. Schema inspection and Skills generation need no key. Configure account authentication yourself before allowing real paid operations. Do not paste your key into the coding assistant.

kitta skills generate --output-dir .agents/skills/kitta-audio
kitta audio tts --schema

Review the generated Skills files and enable them according to your coding assistant's instructions. Writing the directory does not prove the assistant has loaded the skill.

Inspect before execution

kitta audio tts --voice VOICE_ID --text "Hello from Kitta" --dry-run

Replace the voice ID. Dry-run locally validates and displays the request without network access or submission records. Authorization is redacted, but input text appears in the output. It does not check live model availability, balance or prices.

Suggested assistant instructions

Before paid operations, confirm the text, voice, output file and scope. Do not read or display secrets. Retain a business idempotency key for new TTS operations and reuse the original key and input for recovery. Report task IDs on failure; do not automatically resubmit cloning, design or transcription.

The CLI provides terminal commands and Skills files; do not describe it as a deployed MCP service.

Failure and next steps

Fix invalid inputs before making a real submission. If the assistant does not know the remote outcome, inspect the task first. Recovery guide · Automation