MAI Voice
v0.1.1Synthesize speech with Microsoft's MAI-Voice-1 voices via Azure AI Speech REST API.
⭐ 0· 66·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description claim TTS via Azure MAI-Voice-1 and the skill only requires bash and curl plus AZURE_SPEECH_KEY and AZURE_SPEECH_REGION. The included scripts implement exactly that (construct SSML, POST to https://{region}.tts.speech.microsoft.com/cognitiveservices/v1). No unrelated services, binaries, or credentials are requested.
Instruction Scope
SKILL.md instructs running scripts/speak.sh which only reads an optional user-provided text file, uses declared env vars, builds SSML, POSTs to Azure, and writes a local output audio file. The script does not read other system config, does not send data to third-party endpoints beyond the documented Azure endpoint, and does not perform broad or vague data collection. Note: the script will write to any --out path provided by the user and will read any --text-file path the user supplies — both are expected behaviors for a CLI tool.
Install Mechanism
No install spec; this is instruction-only plus a small shell script. No downloads or archive extraction occur, so there is no high-risk install mechanism.
Credentials
Only AZURE_SPEECH_KEY (primary credential) and AZURE_SPEECH_REGION are required — exactly what a TTS tool calling Azure REST should need. No extra SECRET/TOKEN env vars or unrelated credentials are requested.
Persistence & Privilege
always:false and user-invocable:true (defaults). The skill does not modify other skills or system-wide settings. It does not store persistent tokens or enable permanent background services.
Assessment
This skill is internally consistent and appears to do exactly what it says: send text (from --text or a user-provided file) to Azure Speech and save the returned audio. Before installing, ensure you: 1) only provide an Azure Speech key that you are willing to use for TTS (treat AZURE_SPEECH_KEY as a secret); 2) limit the key's scope (use a dedicated Speech resource or key, monitor usage, and rotate if needed); 3) be mindful that any text you pass will be sent to Microsoft's Azure endpoint (do not send highly sensitive PII unless your compliance requirements allow it); 4) review the script if you plan to run it unattended because it will write to whatever --out path is supplied; and 5) verify your Azure region supports MAI-Voice-1. The skill does not exhibit hidden endpoints or unrelated credential requests.Like a lobster shell, security has layers — review code before you run it.
latestvk9756wgajv5rtyeegbwta1105d84bw2c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🗣️ Clawdis
Binsbash, curl
EnvAZURE_SPEECH_KEY, AZURE_SPEECH_REGION
Primary envAZURE_SPEECH_KEY
