Text To Video Editing

Skip the learning curve of professional editing software. Describe what you want — cut the pauses, add a title card at the start, and put captions throughout...

Security Scan

The skill's declared requirements and runtime instructions are mostly consistent with a cloud video-editing service, but there are small inconsistencies and privacy-relevant behaviors (anonymous token creation, uploading user videos to an unknown backend) that merit caution before installing.

Purpose & Capability

The name/description match the runtime instructions: the skill uploads video to a cloud render API and returns edited MP4s. Required credential (NEMO_TOKEN) is appropriate for a cloud API. Inconsistency: the registry metadata at the top said no required config paths, but the SKILL.md YAML frontmatter lists a config path (~/.config/nemovideo/). Also the skill's source/homepage are unknown, so the backend domain (mega-api-prod.nemovideo.ai) cannot be confirmed as a reputable vendor from this package alone.

Instruction Scope

SKILL.md stays within editing scope (session creation, SSE chat, upload, export, poll). It explicitly instructs uploading user video files and polling for render results — expected for this purpose but sensitive (user media will be sent to an external service). It also instructs generating an anonymous token if NEMO_TOKEN is not present, and to include various custom headers (including detection of an install path) — the install-path detection is odd for an instruction-only skill but not dangerous by itself.

Install Mechanism

No install spec and no code files (instruction-only). This minimizes on-disk code risk; nothing will be downloaded or installed by the skill itself.

Credentials

Only a single credential (NEMO_TOKEN) is requested, which fits the stated cloud API usage. The skill will fallback to obtaining an anonymous token via the API if no token is provided; that behavior is reasonable but means the agent will make external network calls to acquire credentials automatically. The SKILL.md frontmatter also declares a config path (~/.config/nemovideo/), which was not listed in the registry summary — this mismatch should be clarified.

Persistence & Privilege

The skill does not request always:true, does not require system-wide changes, and (being instruction-only) doesn't persist code or modify other skills. Autonomous invocation is allowed (platform default) but not combined with other high privileges.

What to consider before installing

This skill appears to do what it promises (upload video to a cloud API, run text-driven edits, return MP4s), but take these precautions before installing: 1) The skill will upload your video files to mega-api-prod.nemovideo.ai — only use it with non-sensitive footage unless you trust the service. 2) Supply your own NEMO_TOKEN only if you trust the provider; otherwise the skill will request an anonymous token automatically from the backend. 3) Clarify the apparent metadata mismatch: SKILL.md lists ~/.config/nemovideo/ as a config path while the registry said none. Ask the publisher for a homepage/privacy policy and verify the backend domain. 4) Test with a short, non-sensitive clip to confirm behavior and headers. If you need stronger assurance, ask for a published maintainer/homepage and a privacy/data-retention statement before using with real content.

Getting Started

Ready when you are. Drop your raw video footage here or describe what you want to make.

Try saying:

• "edit a 3-minute unedited screen recording into a 1080p MP4"
• "cut the pauses, add a title card at the start, and put captions throughout"
• "editing videos by typing instructions instead of using a timeline editor for content creators and marketers"

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.

Text to Video Editing — Edit Videos by Typing Instructions

This tool takes your raw video footage and runs AI text-driven editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute unedited screen recording and want to cut the pauses, add a title card at the start, and put captions throughout — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster and give more accurate results.

Matching Input to Actions

User prompts referencing text to video editing, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is text-to-video-editing, 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).

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

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)

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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the pauses, add a title card at the start, and put captions throughout" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the widest playback compatibility across platforms.

Common Workflows

Quick edit: Upload → "cut the pauses, add a title card at the start, and put captions throughout" → 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.