Video In Filmora
ReviewAudited by ClawScan on May 3, 2026.
Overview
The skill appears coherent for cloud video editing, but users should know their videos, prompts, and NEMO_TOKEN are sent to a third-party NemoVideo backend.
Use this skill only if you are comfortable sending the video, edit instructions, and generated outputs to nemovideo.ai. Prefer non-sensitive footage, use a dedicated token, monitor credits, and verify the provider/Filmora affiliation before relying on it for private or commercial work.
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.
You have less provenance context before trusting the service with uploads and API tokens.
The registry does not provide a public source or homepage to independently verify the publisher or provider relationship.
Source: unknown Homepage: none
Verify the publisher and backend service before uploading sensitive media.
The skill can use the provided or generated token for video-editing sessions and may consume service credits.
The skill uses a bearer token or obtains an anonymous token for the NemoVideo backend; this is expected for the service but still grants API access.
If `NEMO_TOKEN` is in the environment, use it directly ... Otherwise, acquire a free starter token ... Include `Authorization: Bearer <NEMO_TOKEN>`
Use a dedicated token, avoid sharing it, and monitor any credit or subscription impact.
Private footage, prompts, and generated outputs may be processed by nemovideo.ai.
User media is uploaded to an external provider for remote processing, which is central to the skill but creates a third-party data-sharing boundary.
AI video editing runs on remote GPU nodes ... **Upload**: POST `/api/upload-video/nemo_agent/me/<sid>` — file: multipart `-F "files=@/path"`
Upload only videos you are comfortable sharing with the provider, and check the provider's privacy and retention terms for sensitive content.
A user could mistake the skill for an official Filmora/local editing integration when it actually uses a separate cloud service.
The branding references Filmora while the documented backend is NemoVideo. The backend is disclosed, so this is a transparency note rather than evidence of deception.
displayName: "Video in Filmora — Edit and Export Polished Videos" ... **API base**: `https://mega-api-prod.nemovideo.ai`
Confirm the service affiliation and make clear to users that uploads go to nemovideo.ai before sending media.