Create A Video
ReviewAudited by ClawScan on Apr 30, 2026.
Overview
This instruction-only video skill is broadly aligned with its purpose, but it sends user media and prompts to a remote NemoVideo cloud agent/API and uses a bearer token or auto-created anonymous token.
Install only if you are comfortable sending your media and prompts to the NemoVideo cloud service. Use non-sensitive assets, verify the provider/domain, monitor credits or plan limits, and start fresh sessions for unrelated projects.
Findings (8)
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 cloud service can influence intermediate video-editing actions without every step being separately shown to the user.
Remote backend text is treated as instructions for API actions. This is purpose-aligned for translating a GUI video service into API calls, but it means external service responses can steer agent behavior inside the workflow.
Backend says: "click [button]" / "点击" | You do: "Execute via API"
Use the skill for intended video tasks only and review final state, exports, and downloads before relying on the result.
Files you provide may be transferred to the remote video service for processing.
The skill instructs the agent to upload user-provided local files or URLs to the cloud backend. This is expected for video creation, but it is still a high-impact file-transfer operation.
Upload: POST `/api/upload-video/nemo_agent/me/<sid>` — file: multipart `-F "files=@/path"`, or URL: `{"urls":["<url>"],"source_type":"url"}`Only provide files and URLs you intend to upload to the NemoVideo backend.
The skill may create or use a NemoVideo service identity and consume free or account-linked credits.
The skill uses a bearer token and can automatically obtain an anonymous token for the service. The credential is declared and purpose-aligned, but it still grants access to credits/session operations.
If found, skip to session creation. Otherwise: Generate a UUID as client identifier; POST `https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token`; Extract `data.token` ...
Use a dedicated token where possible and monitor credit usage or account state if you connect a registered account.
Users have limited registry-provided provenance information for the service behind the skill.
There is no local package or code dependency, but the registry does not provide source or homepage provenance for a skill that relies on a remote cloud service.
Source: unknown; Homepage: none
Confirm the provider and domain are expected before sending important media or account-linked tokens.
Previously generated or uploaded session content can influence the current video project.
The skill relies on cloud session state and draft data for later actions such as export. This is normal for video editing, but stale or incorrect session state could affect subsequent outputs within the session.
Session state: GET `/api/state/nemo_agent/me/<sid>/latest` — key fields: `data.state.draft`, `data.state.video_infos`, `data.state.generated_media`
Start a new session for unrelated projects or when you do not want prior draft state to carry over.
Your media instructions and project state may be processed by a remote agent/service, not just the local assistant.
The skill communicates with a remote agent-like backend over SSE and API calls. This is central to the skill's design, but user prompts, media references, and workflow state cross a provider boundary.
Create session: POST `/api/tasks/me/with-session/nemo_agent` ... Send message (SSE): POST `/run_sse` ... `app_name":"nemo_agent"`
Avoid sending sensitive, confidential, or regulated media unless you trust the NemoVideo service and its handling of uploaded content.
Users could be surprised by credit, free-plan, or subscription limitations during export.
The skill describes export as free/no-credit, while also documenting subscription-tier blocking. This is not necessarily deceptive, but the cost and plan behavior may not be obvious to users.
`Export` (free, no credits) ... `402` — free plan export blocked; not a credit issue, subscription tier
Check the credit balance and plan behavior before relying on the service for time-sensitive exports.
A render job may continue in the cloud after you stop watching the session.
Cloud render jobs may continue or become orphaned if the user leaves before completion. This is consistent with asynchronous rendering, but it is a form of backend activity that can outlive the active interaction.
The session token carries render job IDs, so closing the tab before completion orphans the job.
Wait for completion when possible and avoid starting renders you do not intend to finish.