Video Editing Ai Tool
PassAudited by ClawScan on May 10, 2026.
Overview
This is a coherent cloud video-editing skill, but it will contact Nemovideo, use or create a token, upload user-selected media, and keep a remote editing session.
Install only if you are comfortable sending selected videos to Nemovideo's remote API for processing. Keep the token private, avoid uploading sensitive footage unless you trust the provider, and confirm final exports or credit-consuming operations.
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 or media URLs the user provides will leave the local environment and be processed by the remote provider.
The skill sends user-provided media or URLs to a remote API for processing, which is central to the stated cloud video-editing purpose.
Upload — `POST /api/upload-video/nemo_agent/me/<sid>` — multipart file or JSON with URLs.
Only upload footage you are comfortable sending to the provider, especially if it contains private, client, or confidential content.
The agent will use an existing NEMO_TOKEN or create an anonymous provider token to run editing and export jobs.
The skill uses a bearer token for provider API access. This is expected for the service, and the artifact also says not to print tokens.
All requests must include: `Authorization: Bearer <NEMO_TOKEN>`
Treat NEMO_TOKEN as a secret, avoid pasting it into chat, and rotate or revoke it if you suspect exposure.
If the backend response is wrong or unexpected, the agent could perform extra in-scope editing or export steps.
Remote backend responses are treated as operational instructions for follow-up API calls. This appears purpose-aligned, but it means the provider can influence the workflow within the editing session.
The backend responds as if there's a visual interface. Map its instructions to API calls: "click" or "点击" → execute the action via the relevant endpoint
For credit-consuming or final export actions, confirm the intended result before proceeding.
Drafts, media metadata, and render jobs may remain associated with a remote session after the immediate chat step.
The skill relies on remote session state and render job identifiers. This is expected for a cloud editing workflow, but it is persistent task context.
Save `session_id` from the response... The session token carries render job IDs, so closing the tab before completion orphans the job.
Avoid starting renders you do not intend to finish, and check whether the provider offers project deletion or token reset controls.
Users have fewer registry-level trust signals to verify who maintains the skill before sending media to its API.
The registry metadata gives limited provenance for the skill or provider, although no local code or install script is present.
Source: unknown; Homepage: none
Verify the provider and terms independently before using it with sensitive or commercial footage.