Subtitle Video Free
v1.0.0Turn a 3-minute YouTube tutorial video into 1080p captioned videos just by typing what you need. Whether it's adding subtitles to videos for free or quick so...
⭐ 0· 51·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 cloud subtitle/rendering and all declared requirements (NEMO_TOKEN and calls to a nemo video API) align with that purpose. One minor inconsistency: the registry metadata lists no required config paths, but the skill's YAML frontmatter declares a config path (~/.config/nemovideo/) and requires NEMO_TOKEN — the SKILL.md also contains logic to obtain an anonymous token if NEMO_TOKEN is missing. These are plausible design choices but the mismatch between registry metadata and the frontmatter should be noted.
Instruction Scope
The runtime instructions focus on uploading videos, creating sessions, using SSE, and polling render status — all consistent with a remote render/subtitle service. The skill instructs the agent to read its own frontmatter and to detect the install path (checking ~/.clawhub/ and ~/.cursor/skills/) in order to set attribution headers; that implies the agent will inspect parts of the user's home filesystem. It also auto-generates an anonymous token via a public API if no NEMO_TOKEN is present. These file-system probes and the automatic token creation are scope-expanding behaviors that are not strictly dangerous but are privacy-relevant and should be acceptable to the user.
Install Mechanism
This is an instruction-only skill with no install spec or code files. No packages are downloaded or written to disk by a declared installer, which is the lowest-risk install model.
Credentials
The skill requests a single credential, NEMO_TOKEN, which is appropriate for a cloud rendering service. However, the SKILL.md includes logic to obtain an anonymous token from the service if NEMO_TOKEN is not set, so the declared requirement is somewhat flexible. The metadata also mentions a config path (~/.config/nemovideo/) even though the registry lists none — another small mismatch to be aware of. No unrelated secrets or multiple unrelated credentials are requested.
Persistence & Privilege
The skill does not request persistent platform-wide privileges (always:false) and uses session tokens for operations. It does instruct including attribution headers derived from install path detection, which requires reading the environment/install location but does not modify other skills or system-wide settings.
Assessment
This skill connects to a remote service (mega-api-prod.nemovideo.ai), uploads your video files, and uses a session token (NEMO_TOKEN) for operations. Before installing or invoking it: 1) confirm you trust the nemo video service and its privacy/retention policy for uploaded videos (sensitive content should not be uploaded unless you accept the risk); 2) be aware the skill may read its own frontmatter and probe common install directories in your home (~/.clawhub, ~/.cursor/skills) to set attribution headers — this is a small privacy intrusion but not a direct data exfiltration by itself; 3) if you prefer, set NEMO_TOKEN yourself (rather than letting the skill request an anonymous token) and avoid providing long-lived credentials you don't want used; 4) if you need stronger assurance, request the skill author publish a homepage or source repository and confirm the exact behavior of token generation, retention, and any logging on the backend. The inconsistencies between registry metadata and the SKILL.md (config path vs none, and auto-generation of token despite NEMO_TOKEN being required) are worth asking the author to clarify.Like a lobster shell, security has layers — review code before you run it.
latestvk97bbrvv2d5vmwj84nfwp0pwhh84m82s
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN