Parakeet Stt
v1.1.0Local speech-to-text with NVIDIA Parakeet TDT 0.6B v3 (ONNX on CPU). 30x faster than Whisper, 25 languages, auto-detection, OpenAI-compatible API. Use when transcribing audio files, converting speech to text, or processing voice recordings locally without cloud APIs.
⭐ 1· 2.3k·5 current·7 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 and description (local Parakeet STT) match the runtime instructions: clone the GitHub repo and run the service via Docker or Python/uvicorn. No unrelated credentials or binaries are requested.
Instruction Scope
SKILL.md stays within scope: it describes installation, running a local HTTP/OpenAI-compatible API, example curl and Python usage, and Docker management commands. It does instruct network operations (git clone, docker compose, pip install) which are expected for installing the stated software.
Install Mechanism
The registry contains no formal install spec, but the README-like instructions tell the user to clone a GitHub repo and run Docker or pip. Running code and containers pulled from an external repo is the primary risk here — the source is a GitHub repo (homepage provided), which is a normal release host, but the skill will cause arbitrary code to execute on the host if followed without review.
Credentials
The skill declares no required secrets or config paths. The only runtime environment hint is PARAKEET_URL (to point at the local service). There are no unexplained credential requests.
Persistence & Privilege
always is false and the skill is instruction-only (no code installed by the registry). It does not request persistent presence or modify other skills or system agent settings.
Assessment
This skill is coherent for running a local Parakeet STT service, but it tells you to fetch and run third-party code and containers. Before following the instructions: 1) inspect the GitHub repo (Docker Compose file, Docker images referenced, requirements.txt, and startup scripts) to ensure no unexpected network calls, telemetry, or privileged operations; 2) prefer running the Docker compose in an isolated/test environment (or VM) and avoid exposing the service port to the public Internet; 3) verify the provenance of Docker images (use images from trusted registries or build locally from the repo); 4) don't run as an elevated user if avoidable; 5) if you require additional assurance, run static review or use a sandboxed environment. If you only need transcription and cannot audit the repo, consider using a well-vetted packaged distribution instead.Like a lobster shell, security has layers — review code before you run it.
latestvk97a0dgngk90dqbm43rvtaksgn7zdexm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🦜 Clawdis