Video To Generator

Turn a 2-minute product demo video into 1080p generated video clips just by typing what you need. Whether it's generating new videos from existing video foot...

Security Scan

The skill's network actions and credential use are broadly consistent with a cloud video-generation tool, but small metadata mismatches and automatic token/session handling plus required uploads to an external service raise privacy and transparency concerns.

Purpose & Capability

Name/description (cloud video generation) align with the declared primary credential NEMO_TOKEN and the listed API endpoints for upload/render. However, SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that is not reflected in the registry metadata (which lists no required config paths). This mismatch is an inconsistency that should be clarified.

Instruction Scope

Runtime instructions instruct the agent to upload user video/audio/image files to mega-api-prod.nemovideo.ai, open SSE streams, create anonymous tokens if NEMO_TOKEN is not set, and store a session_id for subsequent requests. Uploading user data to an external service is expected for this purpose but is sensitive — the skill does not explicitly require user consent or explain retention/processing policies. The instruction to 'don't display raw API responses or token values' is unusual and reduces transparency about what is stored. Overall the instruction set stays within the stated functionality but lacks clear user-facing privacy/consent controls.

Install Mechanism

No install spec or code files are present (instruction-only), which is the lowest-risk install mechanism. Nothing is downloaded or written by an installer according to the manifest.

Credentials

Only one environment variable is required (NEMO_TOKEN), which is proportionate to a cloud API client. However, the skill's frontmatter references a config path for nemovideo which suggests it may read or write local config (SKILL.md doesn't explicitly instruct file writes). The skill also instructs auto-creating an anonymous token when NEMO_TOKEN is absent — that behavior implies storing credentials somewhere (not clearly specified).

Persistence & Privilege

The skill is not always-enabled and is invocable by the user (normal). There is no explicit request for system-wide privileges. The presence of a declared config path in SKILL.md implies possible local persistence of tokens/sessions, but the documentation doesn't spell out where or whether the token/session is persisted to disk.

What to consider before installing

This skill appears to be a legitimate cloud-based video generator, but before installing consider the following: - It will upload your videos (and possibly audio/images) to mega-api-prod.nemovideo.ai for processing — do not upload sensitive or confidential footage unless you trust the service and its retention/privacy policy. - If you don't supply NEMO_TOKEN, the skill will automatically request an anonymous token and keep a session_id; ask where tokens/sessions are stored and for how long they are valid. Prefer supplying your own token if you can review its scope. - There's a metadata mismatch: SKILL.md references a local config path (~/.config/nemovideo/) though the registry metadata did not — ask the skill author to clarify whether the skill will read/write local files. - Verify the service domain and review its terms/privacy, especially for ownership and retention of uploaded media. - If you need stronger guarantees, request the author to add explicit user consent prompts, a clear description of local persistence, and an option to avoid automatic token creation.

Getting Started

Share your existing video clips and I'll get started on AI video generation. Or just tell me what you're thinking.

Try saying:

• "generate my existing video clips"
• "export 1080p MP4"
• "turn this video into a new"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video to Generator — Generate New Videos From Footage

This tool takes your existing video clips and runs AI video generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute product demo video and want to turn this video into a new short promotional clip with music and transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter source clips under 60 seconds produce faster and more focused output.

Matching Input to Actions

User prompts referencing video to generator, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...	Action	Skip SSE?
"export" / "导出" / "download" / "send me the video"	→ §3.5 Export	✅
"credits" / "积分" / "balance" / "余额"	→ §3.3 Credits	✅
"status" / "状态" / "show tracks"	→ §3.4 State	✅
"upload" / "上传" / user sends file	→ §3.2 Upload	✅
Everything else (generate, edit, add BGM…)	→ §3.1 SSE	❌

Cloud Render Pipeline Details

Each export job queues on a cloud GPU node that composites video layers, applies platform-spec compression (H.264, up to 1080x1920), and returns a download URL within 30-90 seconds. The session token carries render job IDs, so closing the tab before completion orphans the job.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-to-generator
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

Translating GUI Instructions

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
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the export workflow

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this video into a new short promotional clip with music and transitions" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "turn this video into a new short promotional clip with music and transitions" → Download MP4. Takes 1-2 minutes for a 30-second clip.

Batch style: Upload multiple files in one session. Process them one by one with different instructions. Each gets its own render.

Iterative: Start with a rough cut, preview the result, then refine. The session keeps your timeline state so you can keep tweaking.