Sarvam AI

v1.0.1

Use Sarvam AI for Indian language Text-to-Speech (TTS), Speech-to-Text (STT), Translation, and Chat.

2· 651·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Sarvam AI TTS/STT/Translate/Chat) align with the bundled CLI script and the single required secret (SARVAM_API_KEY). The required binary points to a local Python virtualenv that the instructions reference, which is consistent with running the included script.
Instruction Scope
Runtime instructions are limited to calling the local CLI script and setting SARVAM_API_KEY. The CLI reads/writes only the audio files you pass and posts data to https://api.sarvam.ai. Minor mismatch: validate_filename blocks absolute paths and '..' but does not forbid directory separators, so relative subpaths (e.g., dir/file.wav) are allowed despite wording that it validates for a 'simple filename'.
Install Mechanism
No install spec (instruction-only) — the skill relies on a local virtualenv and the included Python script. No downloads or external installers are specified.
Credentials
Only SARVAM_API_KEY is required and is appropriate for a third-party API client. No unrelated credentials or config paths are requested.
Persistence & Privilege
Skill is not always-on, does not request elevated privileges, and does not modify other skills or system-wide settings.
Assessment
This skill appears coherent and limited to the Sarvam AI service, but review and consider the following before installing: 1) The script will send text/audio to https://api.sarvam.ai — only provide an API key you trust and do not reuse highly privileged keys. 2) The SKILL.md suggests storing SARVAM_API_KEY in a .env in the workspace; ensure workspace env files are not shared or committed to source control. 3) validate_filename prevents absolute paths and '..' but still allows relative paths (subdirectories) — be careful what file paths you pass to avoid accidental disclosure of sensitive local files. 4) The required binary path is Windows-specific (\.venv\Scripts\python.exe) while examples include Unix paths; confirm the expected virtualenv layout before running. 5) Because there is no install step, the included script will be executed directly — you already reviewed it, but if you did not, inspect the script and verify the network endpoints and behavior before use. If you want to be more cautious, run the CLI in an isolated environment or with a scoped API key you can rotate.

Like a lobster shell, security has layers — review code before you run it.

latestvk977c1wbw7wmtt5dnwmyt7ddg181d8cj

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🧘 Clawdis
Binsskills/sarvam/.venv/Scripts/python.exe
EnvSARVAM_API_KEY
Primary envSARVAM_API_KEY

Comments