← Back to Skills Marketplace
Openclaw Mlx Audio
by
gandli-2025
· GitHub ↗
· v0.2.1
· MIT-0
304
Downloads
1
Stars
1
Active Installs
3
Versions
Install in OpenClaw
/install openclaw-mlx-audio
Description
Local TTS/STT integration for OpenClaw using mlx-audio - Zero API keys, Zero cloud dependency
Usage Guidance
What to consider before installing:
- Verify the upstream source: SKILL.md and docs reference a GitHub repo; confirm the repository (and commit history) before running install.sh. The registry record lacks a homepage, so validate the source yourself.
- Inspect install.sh and the external installer URLs (astral.sh and uv tool) before running. The installer uses curl | sh and uv tool install to fetch mlx-audio binaries — this will download and execute code from the network. If you are uncomfortable, download the repo and examine artifacts offline or run install in a sandbox/VM.
- Decide whether you need the Python servers. The package claims CLI-only in some places but includes python-runtime/*.py (HTTP endpoints that accept uploads). If you want minimal attack surface, disable or avoid starting the Python servers and use the CLI-only paths.
- Check what environment variables your agent exposes. The plugin spawns child processes that inherit process.env; any sensitive env values accessible to the agent could be seen by the invoked CLI tools. Remove or isolate secrets where possible before running.
- Run the tests locally in a controlled environment (bash test/run_tests.sh) to verify behavior. Prefer manual verification of mlx_audio CLI commands (which the plugin will call) before integrating into your main OpenClaw instance.
- If you require higher assurance, ask the maintainer for an authoritative repo URL and a signed release or for an explanation of why Python servers are present despite CLI-only claims. That will raise confidence and resolve the architectural inconsistency.
Additional info that would raise confidence: a public GitHub repo with release tags, commit history, and community reviews; an install path that avoids curl|sh (or a documented, auditable release tarball); clarification whether python-runtime servers are optional and how to disable them.
Capability Analysis
Type: OpenClaw Skill
Name: openclaw-mlx-audio
Version: 0.2.1
The skill bundle provides local Text-to-Speech (TTS) and Speech-to-Text (STT) integration for Apple Silicon devices using the mlx-audio framework. The core logic in `src/index.ts` and the Python servers in `python-runtime/` safely use command-line interface (CLI) calls via `spawn` and `subprocess.run` to perform audio processing. While the bundle contains an unusually large amount of documentation and scripts related to an 'autoresearch' or 'auto-improve' workflow (e.g., `scripts/auto-improve.sh`, `AUTORESEARCH_PLAN.md`), these appear to be artifacts of an AI-assisted development process aimed at improving code quality and success rates rather than malicious prompt injection. No evidence of data exfiltration, unauthorized persistence, or intentional backdoors was found.
Capability Assessment
Purpose & Capability
The stated purpose (local TTS/STT via mlx-audio) matches the plugin code: the JS plugin invokes local mlx_audio CLI commands and there are Python helper servers and tests for local TTS/STT. Minor mismatch: SKILL metadata and README emphasize a CLI-only approach, but the package also includes python-runtime/tts_server.py and stt_server.py and openclaw.plugin.json contains ports/pythonEnvMode settings — this is inconsistent (CLI-only claim vs shipped Python servers).
Instruction Scope
SKILL.md instructs local installation (brew, uv, ffmpeg, uv tool install mlx-audio) and copying the extension into ~/.openclaw/extensions. The runtime code indeed executes local CLI commands and reads/writes temp audio files. Concern: the plugin's runtime checkDependencies requires mlx_audio.tts.generate and mlx_audio.stt.generate even though those CLI binaries are not listed in the SKILL.md 'required bins' metadata (only brew, ffmpeg, uv are listed). Also SKILL.md and some docs repeatedly say "No Python API" while python runtime servers are present — that discrepancy grants the code broader runtime surface than the prose describes. The Python servers accept HTTP uploads (local-only but configurable host/port) and parse multipart bodies, which expands the attack/abuse surface relative to a pure CLI plugin.
Install Mechanism
There is no registry install spec, but an included install.sh performs network installs: it runs curl -LsSf https://astral.sh/uv/install.sh (pipelines a remote installer) and then uses 'uv tool install --prerelease=allow' to fetch mlx-audio from the uv ecosystem. Using curl|sh and tool-installers pulls code at install time from external servers — common for CLI managers but higher risk than pure package-manager installs. The script also offers apt/dnf/brew branches (multi-platform) despite the repo declaring darwin-only. The install step will create binaries and run them locally (extract/install).
Credentials
The skill declares no required env vars or credentials (good). The code does read or forward process.env into spawned processes and the Python servers accept STT_MODEL / STT_LANGUAGE env vars (optional overrides). There are no requests for API keys or unrelated cloud credentials. Passing the agent's environment to executed CLI processes is expected but worth noting because any secrets in the agent env would be visible to child processes.
Persistence & Privilege
The registry flags are normal (always: false) and the skill does not request elevated system permissions in metadata. It installs into the user's OpenClaw extension directory per SKILL.md/install.sh which is expected for a plugin. It does not attempt to modify other skills or global agent configuration in the provided files.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openclaw-mlx-audio - After installation, invoke the skill by name or use
/openclaw-mlx-audio - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.2.1
- Initial release of source files, test scripts, documentation, and packaging for version 0.2.1
- Added all core source code, Python runtime scripts, and build artifacts
- Introduced comprehensive documentation and test plans (automation and manual/Discord tests)
- Included installation scripts and full OpenClaw integration files
- Changelog, progress, and release process documentation now available
v0.2.0
**Major update with migration, documentation overhaul, and cleanup.**
- Migrated and modernized SKILL.md with concise structured metadata and improved English/Chinese instructions.
- Expanded usage examples and installation guidance; added details on supported models and testing instructions.
- Unified tool invocation syntax and standardized plugin configuration.
- Removed legacy files and old documentation (17 files deleted), streamlining the repository.
v0.1.0
Initial release: OpenCLaw MLX Audio - Local TTS & STT integration using mlx-audio
Metadata
Frequently Asked Questions
What is Openclaw Mlx Audio?
Local TTS/STT integration for OpenClaw using mlx-audio - Zero API keys, Zero cloud dependency. It is an AI Agent Skill for Claude Code / OpenClaw, with 304 downloads so far.
How do I install Openclaw Mlx Audio?
Run "/install openclaw-mlx-audio" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Openclaw Mlx Audio free?
Yes, Openclaw Mlx Audio is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Openclaw Mlx Audio support?
Openclaw Mlx Audio is cross-platform and runs anywhere OpenClaw / Claude Code is available (darwin).
Who created Openclaw Mlx Audio?
It is built and maintained by gandli-2025 (@gandli-2025); the current version is v0.2.1.
More Skills