tts
v1.0.3Use this skill whenever the user wants to convert text into speech, generate audio from text, or produce voiceovers. Triggers include: any mention of 'TTS',...
⭐ 1· 499·6 current·6 all-time
bykusuriuri@ksuriuri
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (text-to-speech, voice cloning, timeline rendering) match the included scripts and capabilities (kokoro local backend, Noiz cloud backend, timeline rendering, SRT handling, voice maps). Requesting NOIZ_API_KEY as primary credential is appropriate for the Noiz cloud features.
Instruction Scope
Runtime instructions and scripts call out network and filesystem operations (downloading reference audio, posting text/audio to Noiz endpoints, reading/writing SRT/audio files, invoking ffmpeg/kokoro-tts). This is expected for a TTS skill, but the code will download arbitrary reference_audio URLs you provide and will access ~/ .noiz_api_key (legacy) for migration; review any URLs and local paths you pass to the tool.
Install Mechanism
There is no install spec (instruction-only), which limits automatic installation risks. However, the scripts depend on external programs/libraries (ffmpeg/ffprobe, kokoro-tts CLI for local backend, and the Python 'requests' package) that are not declared as required binaries in the registry metadata. The code also writes files (temp audio, final outputs).
Credentials
The only cloud credential requested is NOIZ_API_KEY (declared as primaryEnv), which aligns with the cloud backend features. The registry listing shows 'required env vars: none' but metadata/SKILL.md do identify NOIZ_API_KEY as primary credential — this minor mismatch is informational rather than malicious.
Persistence & Privilege
The skill writes the API key to ~/.config/noiz/api_key (0600) and will copy a legacy ~/.noiz_api_key into that location if present (non-destructive copy). It also creates temporary files and output audio under user-specified paths. It does not request always:true or modify other skills; persistence is limited to its own config file.
Assessment
This skill appears to do what it says — convert text to speech using either a local Kokoro CLI or the Noiz cloud API. Before installing, consider the following:
- Credential handling: If you configure a NOIZ_API_KEY it will be normalized and saved to ~/.config/noiz/api_key (permissions forced to 0600). If you have an old ~/.noiz_api_key it will be copied to the new path (not deleted). If you do not trust that legacy file, remove it first.
- Network activity: The skill will call Noiz endpoints (default base https://noiz.ai/v1) and may download reference audio from URLs you supply (or its default sample URLs stored on storage.googleapis.com / noiz.ai). Only provide reference_audio URLs you trust.
- Local dependencies: The timeline/rendering features use ffmpeg/ffprobe and (for the local backend) kokoro-tts; the Python 'requests' package is required for Noiz backends. The registry metadata does not list these required binaries — ensure they are available or use guest mode / Kokoro as appropriate.
- Data flow: Uploaded reference audio or generated audio is sent to Noiz when using the cloud backend (authenticated with your API key). If you want to avoid sending data to the cloud, use the Kokoro backend or avoid providing an API key.
- Review defaults: The script points to default reference audio files hosted externally; if you are concerned about unexpected downloads, replace or remove those defaults.
If any of the above is unacceptable, do not install; otherwise the skill is coherent with its stated purpose. If you want higher assurance, review the included Python files yourself and test guest mode first (no API key required) to validate behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk97d19fbgkr0m57k2te4f4nn7s835k8m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Primary envNOIZ_API_KEY