Ai Video Editor From Prompt

Skip the learning curve of professional editing software. Describe what you want — create a 30-second product video from this description: energetic, modern...

Security Scan

The skill's requirements and runtime instructions are internally consistent with a cloud video-generation service: it needs a NEMO_TOKEN (or will obtain an anonymous one), calls nemovideo.ai endpoints, and stores session state — nothing in the instructions appears unrelated to its stated purpose, but the source is unknown and the skill will transmit user uploads and local metadata to an external API, so review privacy/trust before using.

Purpose & Capability

The skill claims to generate videos via a cloud backend and requires a NEMO_TOKEN; that is proportionate. The declared config path (~/.config/nemovideo/) and primaryEnv NEMO_TOKEN align with storing a token/session for the external nemo service.

Instruction Scope

SKILL.md instructs the agent to call nemovideo.ai endpoints, obtain anonymous tokens if NEMO_TOKEN is not set, create sessions, upload files, and stream SSE responses. These actions are expected for a remote render pipeline. Two points to note: (1) the skill will automatically request an anonymous token and use it if the user hasn't supplied NEMO_TOKEN (this creates an outbound network call and issues a bearer token valid for 7 days); (2) the skill derives an X-Skill-Platform header from install paths (which may require reading environment/paths and could leak platform/install info). The instructions explicitly say not to display raw token values to users.

Install Mechanism

No install spec or code is included — this is instruction-only and does not write new binaries to disk. That minimizes install-time risk; however runtime network calls to an external service are required.

Credentials

Only one credential is declared (NEMO_TOKEN), which matches the service being called. The skill will create and use an anonymous token if none is provided, and recommends storing session_id and token (implied in the declared config path). This is proportionate, but users should be aware that uploads and prompt text will be sent to nemo's servers and that the skill may persist a token/session locally.

Persistence & Privilege

The skill does not request always:true, no special platform privileges are declared, and it does not propose modifying other skills. It does imply persisting an ephemeral anonymous token and session_id (normal for a cloud service).

Assessment

This skill appears to do what it says (calls nemovideo.ai to generate videos). Before installing: (1) verify you trust the external domain (mega-api-prod.nemovideo.ai); uploaded media and prompt text will be sent to that service; do not upload sensitive material unless you trust their policies; (2) be aware the skill will obtain/store an anonymous bearer token automatically if you don't set NEMO_TOKEN — consider providing your own token only if you trust the service; (3) the skill may read install/config paths to derive headers (minor metadata leakage); (4) if you install it, monitor where the token/session are stored (e.g., ~/.config/nemovideo/) and delete them when no longer needed. If you need higher assurance, ask the skill author for a source repository, privacy policy, or verification of the nemo service before proceeding.

Getting Started

Send me your text prompt and I'll handle the AI video generation. Or just describe what you're after.

Try saying:

• "generate a short text description like 'a 30-second promo for a coffee shop with upbeat music' into a 1080p MP4"
• "create a 30-second product video from this description: energetic, modern style, with text overlays"
• "generating ready-to-publish videos from a text description alone for marketers, social media creators, small business owners"

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.

AI Video Editor from Prompt — Generate Videos from Text Prompts

Drop your text prompt in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short text description like 'a 30-second promo for a coffee shop with upbeat music', ask for create a 30-second product video from this description: energetic, modern style, with text overlays, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — more specific prompts produce better results — include style, tone, and length in your description.

Matching Input to Actions

User prompts referencing ai video editor from prompt, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-video-editor-from-prompt, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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 "create a 30-second product video from this description: energetic, modern style, with text overlays" — concrete instructions get better results.

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

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

Common Workflows

Quick edit: Upload → "create a 30-second product video from this description: energetic, modern style, with text overlays" → 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.