Caption Generator Gif

v1.0.0

add GIF or video clips into captioned GIF videos with this skill. Works with GIF, MP4, MOV, WebM files up to 200MB. social media creators use it for adding r...

0· 22·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
The name/description describe cloud captioning and the runtime instructions call a nemovideo.ai backend, require a NEMO_TOKEN, and upload media — these requirements match the stated purpose. Note: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) but the registry summary earlier listed no required config paths; this mismatch should be clarified.
Instruction Scope
Instructions are focused on authenticating, creating a session, uploading media, streaming edits via SSE, and exporting renders. They require generating or using a bearer token and hitting the documented endpoints. The instructions do not request unrelated files or unrelated environment variables, but they do instruct sending user media (up to 200MB) to an external service — this is expected for the skill but is a privacy consideration.
Install Mechanism
No install spec or code files are present (instruction-only), so nothing is downloaded or written by an installer. This minimizes install-time risk.
Credentials
Only NEMO_TOKEN is declared as required and is logically needed to authenticate to the backend. The skill also implements an anonymous-token flow (POST to the service to obtain a short-lived token) which is consistent with its design. Bearer tokens will be sent to an external domain; if you set a long-lived NEMO_TOKEN in environment you are granting that token to the skill.
Persistence & Privilege
The skill does not request 'always: true' or system-wide privileges. However the frontmatter mentions a config path (~/.config/nemovideo/) which implies the agent might persist a client-id or token; the SKILL.md does not explicitly say where/if it writes tokens. Clarify whether tokens/client-id are persisted to disk.
Assessment
This skill is internally consistent with a cloud captioning service, but before installing consider: (1) files you upload (GIF/MP4 up to 200MB) will be sent to mega-api-prod.nemovideo.ai — only proceed if you trust that service and its privacy/terms; (2) the skill uses bearer tokens (NEMO_TOKEN) and may obtain short-lived anonymous tokens if you don't provide one — treat any token as sensitive; (3) clarify whether the agent will write a client-id or tokens to ~/.config/nemovideo/ (frontmatter mentions it but behavior is not explicit); (4) the skill source/homepage is not provided and the owner ID looks opaque — if you require stronger provenance, ask for a repository or vendor page before use. If you only want to test functionality without tying production credentials, avoid setting a persistent NEMO_TOKEN and rely on the anonymous-token flow, but be aware of rate limits and the fact your media still goes to the external service.

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

latestvk979awy53b4468ecp3qjgs7qd984qvpg

License

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

Runtime requirements

🎞️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN

Comments