Video Editing Ai Software Free
ReviewAudited by ClawScan on May 4, 2026.
Overview
This is a coherent cloud video-editing skill, but using it sends your media to nemovideo.ai and uses or creates a service token.
This skill appears purpose-aligned and instruction-only, with no local code or static-scan findings. Before installing, make sure you are comfortable sending your videos, audio, and images to nemovideo.ai, use only a dedicated NEMO_TOKEN, and avoid uploading confidential footage unless you trust the provider’s privacy and retention practices.
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.
Videos, images, and audio provided to the skill may leave the local environment and be processed by nemovideo.ai.
The skill discloses that user media is uploaded to a third-party cloud API for processing. This is expected for cloud video editing, but video/audio files can contain sensitive personal or business data.
This skill connects to a cloud processing backend ... Upload: POST `/api/upload-video/nemo_agent/me/<sid>` — file: multipart `-F "files=@/path"`
Use it only for media you are comfortable uploading to that provider, and check the provider’s privacy/retention terms before sending sensitive footage.
The skill can act within the NEMO video service using the token and may consume available service credits or access the associated session state.
The skill uses a bearer token, or obtains an anonymous service token, to authenticate to the cloud backend. This is coherent with the service integration, and the instructions say not to expose tokens.
Look for `NEMO_TOKEN` in the environment ... POST `https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token` ... Include `Authorization: Bearer <NEMO_TOKEN>`
Use only a service-specific NEMO token, avoid sharing it elsewhere, and rotate or revoke it if you no longer trust the integration.
Some editing or export steps may be carried out based on backend responses rather than each intermediate step being shown to the user.
The skill tells the agent to convert backend UI-style responses into API actions. This is purpose-aligned, but it means remote backend text can drive follow-on actions inside the video-editing workflow.
Backend says | You do ... "click [button]" | Execute via API ... "Export button" / "导出" | Execute export workflow
Keep backend-driven actions limited to the requested video-editing task, and ask for confirmation before uploads, exports, or any action that could cost credits or share a download URL.
It is harder to independently verify who operates the backend or what its data handling policies are.
The provided registry metadata does not identify a source repository or homepage. There is no local code to inspect, so review depends mainly on the visible instructions and the remote API domain.
Source: unknown; Homepage: none
Prefer using this with non-sensitive media unless you can verify the provider’s identity, terms, and privacy practices.