Video Make

ReviewAudited by ClawScan on May 3, 2026.

Overview

This looks like a coherent cloud video-rendering skill, but it sends user videos and prompts to a NemoVideo backend and uses a service token/session.

This skill appears purpose-aligned for cloud video editing. Before installing or using it, make sure you are comfortable uploading your footage to the NemoVideo API, keep NEMO_TOKEN secure, and avoid sending private or proprietary videos unless you trust the provider and understand its retention policies.

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.

What this means

Raw footage, edit instructions, and generated media details may leave the local environment and be processed by NemoVideo's cloud service.

Why it was flagged

The skill is explicitly designed to upload user-provided media and send prompts to an external cloud video backend.

Skill content
This skill connects to a cloud processing backend... API base: `https://mega-api-prod.nemovideo.ai` ... **Upload**: POST `/api/upload-video/nemo_agent/me/<sid>`
Recommendation

Use this only for videos and prompts you are comfortable sending to that provider, and review the provider's privacy/retention terms if the footage is sensitive.

What this means

The token can authorize video sessions, credit checks, uploads, and render operations for this service.

Why it was flagged

The skill uses a provider-specific bearer token, either supplied by the user or automatically obtained as an anonymous token.

Skill content
Look for `NEMO_TOKEN` in the environment... POST `https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token` ... Extract `data.token` ... Bearer auth
Recommendation

Keep NEMO_TOKEN private, prefer a limited-purpose token, and rotate or remove it if you no longer use the skill.

What this means

Project state may be reused across operations in the same session and may remain associated with the service-side session or token.

Why it was flagged

The workflow relies on remote session state containing drafts, video info, and generated media references.

Skill content
Keep the returned `session_id` for all operations... **Session state**: GET `/api/state/nemo_agent/me/<sid>/latest` — key fields: `data.state.draft`, `data.state.video_infos`, `data.state.generated_media`
Recommendation

Avoid mixing unrelated or sensitive projects in the same session, and clear/delete remote project data if the provider offers that option.

What this means

It may be harder to confirm who maintains the skill or whether the cloud API endpoint is officially associated with the expected service.

Why it was flagged

The registry metadata does not provide an obvious source or homepage for users to verify the publisher or service relationship.

Skill content
Source: unknown; Homepage: none
Recommendation

Verify the publisher and endpoint before sending sensitive or proprietary videos.