Video Erstellen Ki

marketers, content creators, small business owners create text or images into AI-generated videos using this skill. Accepts MP4, MOV, JPG, PNG up to 500MB, r...

Security Scan

The skill's instructions generally match a cloud video-rendering service and only request a single API token, but there are small inconsistencies in declared config paths/metadata and a few runtime behaviors (reading install path, auto-generating/storing anonymous tokens) that deserve scrutiny before use.

Purpose & Capability

The name/description (AI video generation) aligns with the runtime actions (upload, render, poll, return download URL) and the single required env var NEMO_TOKEN is appropriate for a backend API. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — this mismatch is unexplained and should be clarified.

Instruction Scope

Instructions remain within the stated purpose (session creation, uploads, SSE chat, export polling). They also instruct the agent to detect the agent install path (to set X-Skill-Platform) and to generate an anonymous token if NEMO_TOKEN is absent. Those filesystem checks and token-generation steps are small scope expansions worth noting: they require reading the agent's environment/home and making network calls to the anonymous-token endpoint.

Install Mechanism

This is instruction-only with no install spec and no code files — no files are written to disk by the skill itself. That lowers risk compared with downloadable installs.

Credentials

The skill only declares a single credential (NEMO_TOKEN), which is appropriate. But the SKILL.md also references configPaths and reads the install path for attribution headers; those imply access to user home/config directories even though the registry said none. Confirm whether the skill will read or write ~/.config/nemovideo/ or other local files and whether the anonymous token is persisted.

Persistence & Privilege

always is false and the skill is user-invocable. There is no install script or request for permanent system-wide privileges. Autonomous invocation is enabled by default but not combined with other high-risk behaviors here.

What to consider before installing

This skill appears to do what it says (send uploads to a cloud rendering service and return MP4s) and only requests one API token. Before installing, confirm the skill's origin (no homepage is listed) and whether you trust mega-api-prod.nemovideo.ai. Ask the publisher to explain the metadata mismatch about ~/.config/nemovideo/, and whether the skill will read or persist any files or the anonymous token it may acquire. Avoid supplying highly sensitive files or a broadly-scoped NEMO_TOKEN until you verify the provider and token permissions. If you want extra caution, use anonymous mode (no long-lived NEMO_TOKEN) or create a scoped/test token with minimal permissions.

Getting Started

Share your text or images and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "create my text or images"
• "export 1080p MP4"
• "Erstelle ein 30-Sekunden-Video aus meinem Text"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Video Erstellen KI — Create Videos with AI

Send me your text or images and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a short product description text and three product photos, type "Erstelle ein 30-Sekunden-Video aus meinem Text und diesen Bildern", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter scripts with clear sentences produce more accurate AI-generated scenes.

Matching Input to Actions

User prompts referencing video erstellen ki, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-erstellen-ki
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute export workflow

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "Erstelle ein 30-Sekunden-Video aus meinem Text und diesen Bildern" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and websites.

Common Workflows

Quick edit: Upload → "Erstelle ein 30-Sekunden-Video aus meinem Text und diesen Bildern" → 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.