Video Maker Free For Kids
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The provider token can authorize video sessions and jobs for this service.
The skill creates or uses a bearer token and sends it to the NemoVideo API. This is expected for the stated service, with no evidence of unrelated credential use.
Check if `NEMO_TOKEN` is set... POST to `https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token`... The response `data.token` is your NEMO_TOKEN... Include `Authorization: Bearer <NEMO_TOKEN>` ... on every request
Use a dedicated token for this service if possible, avoid sharing logs that contain tokens, and let the anonymous token expire or rotate it if you no longer use the skill.
Files you provide may leave your device and be processed by NemoVideo's cloud service.
User-selected images, videos, or audio are uploaded to a third-party cloud API for processing. This is purpose-aligned but may involve private or children's media.
Drop your images or clips in the chat... I'll handle the AI video creation on cloud GPUs... **Upload**: POST `/api/upload-video/nemo_agent/me/<sid>` — file: multipart `-F "files=@/path"`
Only upload files you are comfortable sending to the provider, avoid private identifying information in children's media, and review the provider's privacy/retention terms if available.
Opening the skill can initiate a backend connection and session setup.
The skill may make an external setup call when opened, before a specific file upload or render request. The behavior is disclosed and tied to the video workflow.
When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").
Install/use it only if you are comfortable with automatic setup calls to the NemoVideo backend.
A submitted render may keep running on the provider after you leave the session.
The workflow keeps session state and cloud render jobs may continue outside the visible chat/tab. This is limited to the rendering task and not evidence of hidden background behavior.
Store the returned `session_id` for all subsequent requests... closing the tab before completion orphans the job.
Do not submit media unless you intend it to be processed, and wait for completion or use any available cancel/cleanup option if you change your mind.