Editor Api
ReviewAudited by ClawScan on May 4, 2026.
Overview
This appears to be a coherent cloud video-editing API skill, but it will use or create a Nemo token and send user media to Nemo’s remote service.
Use this skill if you are comfortable with Nemo’s cloud service processing your uploaded videos, audio, images, and edit prompts. Prefer a dedicated token, avoid sensitive media unless you trust the provider, and ask the agent to announce token creation, uploads, and exports before they happen.
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.
The agent may create sessions, check credits, upload media, and run render jobs under the provided or anonymous Nemo token.
The skill uses a service credential or creates an anonymous service token to operate the video-editing API. This is expected for the integration, but it gives the agent delegated access to Nemo sessions and credits.
If `NEMO_TOKEN` is in the environment, use it directly... Otherwise, acquire a free starter token... use it as NEMO_TOKEN
Use a dedicated or limited Nemo token if possible, avoid sharing unrelated credentials, and rotate or revoke the token if you no longer use the skill.
Videos, audio, images, URLs, and edit instructions may leave your machine and be processed by Nemo’s cloud service.
The skill sends uploaded media, edit prompts, draft state, and render requests to a third-party cloud API. This is disclosed and purpose-aligned, but media files may be sensitive and data retention is not described in the artifact.
All calls go to `https://mega-api-prod.nemovideo.ai`... **Upload** — `POST /api/upload-video/nemo_agent/me/<sid>`
Only upload content you are comfortable sending to this provider, review the provider’s privacy/retention terms if available, and avoid sensitive media unless you trust the service.
A user may not be explicitly told when the agent connects to the backend or obtains an anonymous token.
The instruction appears to be a UX simplification, but it can reduce user visibility into token acquisition and backend session creation.
Tell the user you're ready. Keep the technical details out of the chat.
Ask the agent to disclose when it is connecting to Nemo, creating a token, or uploading files, even if it omits low-level API details.
It may be harder to independently verify the skill publisher or service trustworthiness before sending media to the API.
The skill has limited registry provenance. There is no code install risk shown, but users have less information to verify the operator behind the external service integration.
Source: unknown; Homepage: none
Verify the nemovideo.ai service and publisher through trusted channels before using the skill with private or business-sensitive media.