Video Maker Linkedin
ReviewAudited by ClawScan on May 3, 2026.
Overview
This appears to be a coherent cloud video-rendering skill, but it sends user media and prompts to NemoVideo and uses or creates a Nemo API token.
Install only if you are comfortable sending selected clips, headshots, screen recordings, and prompts to `mega-api-prod.nemovideo.ai`. Use a limited Nemo token where possible, avoid confidential media, and confirm any export or credit-impacting step.
Findings (3)
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 can act within the NemoVideo service using the supplied or generated token.
The skill uses a Nemo provider token for sessions and render requests. This is expected for the video service, but it gives the skill provider-session and potential credit/account authority.
If `NEMO_TOKEN` is in the environment, use it directly and create a session... Include `Authorization: Bearer <NEMO_TOKEN>` ... on every request
Use a scoped token if available, monitor credits or subscription impact, and avoid sharing the token outside the intended environment.
Uploaded files, prompts, render state, and generated media may leave the local environment and be processed by NemoVideo.
The skill clearly discloses that user media and instructions are sent to an external cloud rendering backend. This is purpose-aligned, but screen recordings and headshots can contain sensitive personal or business data.
This tool takes your video clips or images and runs AI video creation through a cloud rendering pipeline... API base: `https://mega-api-prod.nemovideo.ai`
Do not upload confidential screen recordings, private documents, or sensitive images unless you are comfortable with NemoVideo processing them.
Some video-service actions may be performed based on backend responses rather than separate step-by-step user prompts.
The skill instructs the agent to convert backend UI-style responses into follow-up API actions. This is part of the intended integration, but it means external backend messages can steer the workflow inside the video session.
Backend Response Translation... "click [button]" / "点击" | Execute via API
Keep API actions limited to the current user-requested video task, and confirm any action that could spend credits, publish content, or expose additional files.