Ai Video Editor Hot Free
ReviewAudited by ClawScan on May 11, 2026.
Overview
This appears to be a cloud video-editing connector, but it sends your chosen videos to NemoVideo’s API and uses a provider token/credits.
Before installing, decide whether you trust NemoVideo with the videos, images, audio, and prompts you provide. Avoid sensitive footage unless you are comfortable uploading it to the listed cloud API, and confirm exports or other credit-consuming actions.
Findings (5)
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.
Videos, images, audio, prompts, and draft state may be processed by NemoVideo’s cloud service.
The skill sends user-provided media to a third-party cloud API for editing, which is expected for this purpose but important for privacy.
“All calls go to `https://mega-api-prod.nemovideo.ai`” and “Upload — `POST /api/upload-video/nemo_agent/me/<sid>` — multipart file or JSON with URLs.”
Use the skill only with media you are comfortable uploading to the NemoVideo backend, especially if the footage contains private people, locations, or business content.
The skill can use the configured or anonymous NemoVideo token and may consume service credits during editing/export.
The skill uses a provider token for authorization and credits. This is purpose-aligned for the NemoVideo service, with no evidence of unrelated credential use.
“If `NEMO_TOKEN` is in the environment, use it directly… Otherwise, acquire a free starter token” and “Include `Authorization: Bearer <NEMO_TOKEN>`.”
Check which NemoVideo token is configured and monitor credits before exporting or processing large videos.
A backend response may cause the agent to continue workflow actions such as querying state or exporting a render.
The skill lets backend responses guide follow-up API actions. That fits the GUI-to-API workflow, but exports can be user-visible and credit-consuming.
Backend says “click [button]” / “Export button” → “Execute via API” / “Execute export workflow.”
The agent should keep actions tied to the user’s request and ask before credit-consuming exports or unexpected workflow changes.
Users may not see the endpoint, token, session, or credit details unless the agent chooses to disclose them.
Suppressing technical detail can be reasonable UX, but users should still understand that the skill connects to a remote service and uploads selected media.
“Tell the user you’re ready. Keep the technical details out of the chat.”
Provide a short plain-language disclosure before uploading media or using credits, even if low-level API details are omitted.
It may be harder for users to independently verify the provider, privacy terms, or support channel before uploading videos.
There is no local installer or code to review, but the source and homepage provenance are limited for a cloud service that receives user media.
“Source: unknown”; “Homepage: none”; “No install spec — this is an instruction-only skill.”
Verify that the NemoVideo domain and service are trustworthy before using sensitive footage.