Auto Caption - AI Subtitle Generator for TikTok YouTube and Reels

v1.0.0

One-click automatic captions for any video. Drop a file, get perfectly timed subtitles in seconds. Built-in presets for TikTok, YouTube, and Instagram Reels...

0· 127·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
medium confidence
Purpose & Capability
Name/description match the instructions: the skill uploads video files to a remote captioning API, requests/uses a NEMO token, and persists a client_id under ~/.config/nemovideo/. Minor metadata inconsistency: registry lists no required env vars while a primaryEnv (NEMO_TOKEN) is declared — the SKILL.md treats NEMO_TOKEN as optional and auto‑generated, which explains the discrepancy.
Instruction Scope
The SKILL.md explicitly instructs the agent to POST user videos and related requests to nemovideo API endpoints and to create/persist a client_id under ~/.config/nemovideo/. This is coherent with captioning functionality, but it does mean user media and derived captions are transmitted to an external service by design.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is installed or written beyond the client_id and token files the instructions explicitly create. This is the lower-risk installation pattern.
Credentials
Only credential referenced is NEMO_TOKEN (declared as primary). SKILL.md treats it as optional and shows an anonymous-token flow to obtain one; that aligns with the service's needs. No unrelated secrets or cloud provider credentials are requested.
Persistence & Privilege
always is false and the skill does not request system-wide settings or attempt to modify other skills. It persists a client_id and expects a token file under ~/.config/nemovideo/, which is reasonable for this purpose.
Assessment
This skill appears to do what it says: it uploads videos to a third‑party captioning service (API host: mega-api-prod.nemovideo.ai / nemovideo.com) and may persist a client_id and token under ~/.config/nemovideo/. Before installing/use, consider: (1) Privacy — your videos will be transmitted to an external service; avoid uploading sensitive content unless you trust the provider and have reviewed their privacy/terms. (2) Token persistence — a token may be stored locally and used for requests (it expires after 7 days per the docs); know how to revoke/delete it. (3) Source trust — the skill has no homepage and an unknown source; verify the service/owner if you need stronger assurance. (4) Test with non-sensitive videos first and monitor network activity. The only minor inconsistency is that registry metadata lists no required env vars while a primaryEnv (NEMO_TOKEN) is declared — SKILL.md explains NEMO_TOKEN is optional/auto‑generated, which mitigates that discrepancy.

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

latestvk97csrbp82wq65cetabs9vrzxn83b5zy

License

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

Runtime requirements

Clawdis
Primary envNEMO_TOKEN

Comments