Overlaying Video
ReviewAudited by ClawScan on May 13, 2026.
Overview
This appears to be a purpose-aligned cloud video compositing skill, but it sends selected media and prompts to NemoVideo's backend and uses or obtains a service token.
This skill is coherent for cloud video overlaying and shows no artifact-backed malicious behavior. Before installing, be comfortable with NemoVideo receiving selected media files and editing prompts, using a token or free anonymous token, and retaining session/render state while jobs run.
Findings (4)
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 skill may use NemoVideo account credits or a temporary anonymous token when creating sessions and exports.
The skill uses a provider token for all API calls and can obtain an anonymous token when one is not present. This is expected for the stated cloud-rendering service, but it is credential and credit-bearing access.
If `NEMO_TOKEN` is in the environment, use it directly... Otherwise, acquire a free starter token... Every API call needs `Authorization: Bearer <NEMO_TOKEN>`
Use a dedicated NemoVideo token if possible, monitor credit usage, and avoid sharing broader credentials than the service needs.
Videos, images, audio, and prompt text selected for editing may leave the local environment and be processed by the provider.
The skill clearly discloses that media files and editing instructions are sent to the external NemoVideo cloud backend for processing.
This tool takes your video clips and runs video layer compositing through a cloud rendering pipeline. You upload, describe what you want, and download the result.
Upload only media you are comfortable sending to NemoVideo, especially if clips contain private, client, or regulated content.
A render job or project state may continue to exist on the provider side after the local conversation ends.
The provider keeps session and timeline state for render jobs. That persistence is normal for cloud rendering, but it may outlive the immediate chat interaction.
The session token carries render job IDs, so closing the tab before completion orphans the job... Fetch current timeline state (`draft`, `video_infos`, `generated_media`).
For sensitive projects, check the provider's retention and deletion options and avoid abandoning jobs with confidential media.
Users have less external information to confirm who operates the skill and backend before uploading media.
The artifact does not provide an independent source repository or homepage for verification. There is no install code, so the local supply-chain risk is limited, but provider provenance is still something users may want to verify.
Source: unknown; Homepage: none
Verify that the NemoVideo backend is the intended service before using the skill with sensitive content.