Free Demo Video

Skip the learning curve of professional editing software. Describe what you want — trim the intro, add captions, and export a clean demo video — and get poli...

Security Scan

The skill's declared purpose (cloud video editing) matches most of its runtime instructions, but there are a few incoherences and privacy/runtime concerns (automatic anonymous token creation, implied filesystem/config access, and a mismatch between metadata and registry) that warrant review before installing.

Purpose & Capability

The skill is a cloud video-processing frontend and requires a single service token (NEMO_TOKEN), which is coherent with its stated purpose. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that is not declared in the registry metadata, which is an inconsistency: either the skill expects local config files (more access) or the registry record is incomplete.

Instruction Scope

Most instructions stay within the video-editing scope (upload, SSE-based edit commands, export polling). Two behaviors require attention: (1) the skill instructs the agent to automatically connect to an external service on first open and obtain an anonymous token without explicit per-use consent, and (2) it derives an X-Skill-Platform header by inspecting install paths (~/ .clawhub/, ~/.cursor/skills/), which implies the agent may read filesystem paths to detect install location. Both are reasonable for a networked cloud service but expand the skill's runtime actions beyond simple, on-demand calls.

Install Mechanism

Instruction-only skill with no install spec and no code files. This minimizes risk from downloaded/installed code; all risky behavior would be from runtime network calls described in SKILL.md.

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportionate to a third-party cloud service. Caveats: the skill instructs generating and storing an anonymous token automatically (100 free credits, 7 days) — it's not explicit where the token/session_id will be persisted. Also, SKILL.md metadata includes a configPaths entry (~/.config/nemovideo/) not declared in the registry 'required config paths'; this mismatch should be clarified because it affects what local files the skill may read/write.

Persistence & Privilege

always:false and model invocation is default (allowed). The skill does not request permanent platform-wide privileges or changes to other skills. The main persistence concern is vague: it tells the agent to 'store' session_id and NEMO_TOKEN but doesn't specify storage location, retention, or encryption.

What to consider before installing

Before installing: (1) Confirm you trust the external service domain (mega-api-prod.nemovideo.ai) because the skill will automatically request an anonymous token and upload videos to that service. (2) Ask the author to clarify where NEMO_TOKEN and session_id are persisted (environment, local config file, or memory) and how long they remain; persistent storage could expose tokens. (3) Clarify the conflicting metadata: SKILL.md lists ~/.config/nemovideo/ as a config path but the registry showed none — if the skill reads or writes that directory, it has broader filesystem access. (4) Be aware that the skill may perform automatic background network calls when first opened and may derive headers by checking common install paths (this implies filesystem access). (5) Avoid sending sensitive or proprietary footage until you verify the service's privacy policy and token handling. If the developer can confirm where tokens/sessions are stored and remove or document the configPath requirement, the remaining issues are minor.

Getting Started

Send me your video clips and I'll handle the AI demo creation. Or just describe what you're after.

Try saying:

• "create a 60-second screen recording of your product into a 1080p MP4"
• "trim the intro, add captions, and export a clean demo video"
• "creating free product demo videos without editing software for marketers"

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.

Free Demo Video — Create and Export Demo Videos

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

Say you have a 60-second screen recording of your product and want to trim the intro, add captions, and export a clean demo video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: keep your demo under 2 minutes for fastest processing and best viewer retention.

Matching Input to Actions

User prompts referencing free demo video, 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.

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

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

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

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

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.

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 "trim the intro, add captions, and export a clean demo video" — 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 email, web, and social platforms.

Common Workflows

Quick edit: Upload → "trim the intro, add captions, and export a clean demo video" → Download MP4. Takes 30-60 seconds 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.