DeepGram Speech platform
v1.0.1Command-line tool for fast, accurate speech-to-text transcription from local files, URLs, or live audio using Deepgram’s API with customizable options.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The SKILL.md describes CLI-based speech-to-text using @deepgram/cli and examples match the stated purpose (local files, URLs, stdin, microphone). There are no unrelated requirements (no extraneous cloud credentials or unrelated binaries).
Instruction Scope
Instructions stay within the transcription domain (install CLI, login, run deepgram listen). They implicitly transmit audio/transcripts to Deepgram's service (expected for this purpose) and require microphone/device access for live capture — users should note that audio and transcripts leave the local machine to the Deepgram service.
Install Mechanism
The registry contains no install spec; the README tells the user to run npm install -g @deepgram/cli. This is a normal, common install route but does involve pulling code from the npm registry and installing a global binary — users should verify the package publisher and be comfortable with global npm installs.
Credentials
The skill declares no environment variables or secrets. The CLI does require a Deepgram API key (obtained via deepgram login) — this is proportional and expected for a speech-to-text integration; no unrelated secrets are requested.
Persistence & Privilege
always is false and the skill does not request system-wide configuration changes. disable-model-invocation is false (agent may call it autonomously), which is the platform default — not a red flag by itself.
Assessment
This skill appears to be a straightforward guide for using the official Deepgram CLI. Before installing or using it: 1) verify you're comfortable installing a global npm package and that @deepgram/cli is the official package (check the npm publisher and repository); 2) understand that audio and transcripts will be sent to Deepgram's servers — avoid sending sensitive audio unless your Deepgram account and policy permit it; 3) create and scope a separate Deepgram API key if you want to limit exposure, and revoke it if no longer needed; 4) be aware microphone access is needed for live capture and that the CLI stores your API key locally via its login flow. If you need the agent to run this skill autonomously, consider whether you trust the agent's prompts to send audio to an external cloud service.Like a lobster shell, security has layers — review code before you run it.
latest
Deepgram CLI Skills Guide
Tool
@deepgram/cli — command-line interface for Deepgram speech-to-text.
Install
npm install -g @deepgram/cli
Auth
deepgram login
Uses your Deepgram API key (stored locally).
Core Skill: Speech → Text
Transcribe a Local Audio File
deepgram listen prerecorded audio.wav
Transcribe with Options
deepgram listen prerecorded audio.wav \
--model nova-2 \
--language en \
--punctuate \
--diarize
Core Skill: Read / Reach Content
From URL (remote audio)
deepgram listen prerecorded https://example.com/audio.mp3
From STDIN (pipes)
cat audio.wav | deepgram listen prerecorded -
From Microphone (live)
deepgram listen microphone
Stop with Ctrl+C. Congrats, you just dictated reality.
Output Handling
Save Transcript
deepgram listen prerecorded audio.wav > transcript.json
Plain Text Output
deepgram listen prerecorded audio.wav --format text
Useful Flags (Memorize These)
--model–nova-2,general, etc.--language–en,tr,de, …--punctuate– adds punctuation--diarize– speaker separation--format–json,text,srt,vtt
Typical Workflow
- Reach content (file / URL / mic)
- Run
deepgram listen - Capture output (JSON or text)
- Post-process (search, summarize, subtitle)
Skill Summary
- CLI-based speech-to-text
- Local, remote, and live audio
- Scriptable, pipe-friendly
- Fast, accurate, no UI nonsense
Deepgram CLI: because keyboards are overrated.
Comments
Loading comments...
