Ffmpeg Add Subtitle
v1.0.0Tell me what you need and I'll help you add subtitles to your videos using FFmpeg — whether you're burning text directly into frames or attaching a soft subt...
⭐ 0· 109·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill advertises server-side FFmpeg processing and the SKILL.md instructs the agent to call a remote FFmpeg API (mega-api-prod.nemovideo.ai) using a bearer token. Requesting a NEMO_TOKEN and providing endpoints for session creation, upload, and render is coherent with the described cloud subtitle-processing purpose.
Instruction Scope
Instructions will upload user video files (multipart or URL) to the remote API, create/read a local client_id file at ~/.config/ffmpeg-add-subtitle/client_id, and read the SKILL.md frontmatter and install path to set attribution headers. These actions are within scope for a cloud-based subtitle service, but they do involve transmitting user media to an external server and creating a small local file — both are material privacy/coverage decisions the user should understand.
Install Mechanism
No install spec and no code files: this is instruction-only, so nothing will be downloaded or executed locally beyond normal agent behavior. That lowers disk-write/execution risk compared with skills that fetch binaries.
Credentials
Only one credential (NEMO_TOKEN) is declared as required and used for all API calls. That is proportional to a remote service that requires authentication. The skill also may create/maintain a local client_id file; that is reasonable for anonymous token acquisition.
Persistence & Privilege
The skill is not always-enabled and does not request elevated agent privileges. Its only local persistence is creating a small client_id at ~/.config/ffmpeg-add-subtitle/client_id if missing. It does not request or modify other skills' configs.
Assessment
This skill is coherent for a cloud-based FFmpeg subtitle workflow, but it will upload your video files and metadata to an external service (mega-api-prod.nemovideo.ai) for processing. Before installing or using it, consider:
- Privacy: Do you want to send the video content to a third party? Avoid using the skill for sensitive or private videos unless you trust the service/provider.
- Tokens: NEMO_TOKEN grants access to the remote API; if you don't have one the skill will create a local client_id and request an anonymous token from the remote endpoint. Treat that token as sensitive and revoke it via the provider if needed.
- Attribution headers: the skill will read its frontmatter and detect install paths to populate headers—this reads the file path and frontmatter only (not other files).
- Network trust: verify the service domain and its privacy/terms (mega-api-prod.nemovideo.ai). If you prefer local-only processing, run FFmpeg locally rather than using this cloud-based skill.
Overall the skill appears internally consistent with its stated purpose; the main risk is the normal one for cloud processing: data exposure to the remote API. If you want higher assurance, ask the skill/vendor for a privacy policy, data retention rules, or support for on-prem processing.Like a lobster shell, security has layers — review code before you run it.
latestvk976gepn4dvsvcg5kpgab92xzd841ev8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
