Demo Video Free

Skip the learning curve of professional editing software. Describe what you want — trim the intro, add title cards, and export as a free demo video — and get...

Security Scan

The skill's declared requirements and runtime instructions are coherent with a cloud-based demo-video service — it needs a NEMO_TOKEN (or will obtain an anonymous one) and calls a nemovideo.ai API — but there are minor inconsistencies and privacy/visibility points you should review before installing or using it.

Purpose & Capability

The name/description (create/export demo videos) matches the instructions (upload video, create session, render/export). The only small mismatch is that the registry metadata at the top lists no config paths while the SKILL.md's YAML frontmatter advertises a config path (~/.config/nemovideo/). Other required items (NEMO_TOKEN, API endpoints) are appropriate for a cloud video-rendering integration.

Instruction Scope

SKILL.md instructs the agent to use NEMO_TOKEN if present or obtain an anonymous token via a POST to the service, create sessions, upload video files, poll render status, and return download URLs — all consistent with the stated purpose. Minor concerns: it asks the agent to detect an install path to set X-Skill-Platform (this implies reading the agent's environment / filesystem path), and it explicitly tells the agent to 'keep the technical details out of the chat', which can obscure network activity from the user. No instructions request unrelated system credentials or files.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That minimizes installation risk.

Credentials

The skill requests a single credential (NEMO_TOKEN) which is directly used for Authorization with the backend — proportional to the task. It will create an anonymous token if no NEMO_TOKEN is present, which reduces the need to supply sensitive credentials. No unrelated secrets or multiple external credentials are requested.

Persistence & Privilege

The skill does not request always: true and is user-invocable only. It does not attempt to modify other skills or system-wide settings. Autonomous invocation is permitted by default (disable-model-invocation: false) — normal for skills — but this is not combined with elevated privileges.

Assessment

This skill appears to be what it says: a cloud-based demo video creation front end that uses a NEMO_TOKEN to call nemovideo.ai. Before installing/using it: - Be aware that your video files (which may contain sensitive or personal data) will be uploaded to an external service; review the service's privacy/retention terms if possible. - If you don't want to provide a long-lived token, let the skill obtain an anonymous starter token (it supports that). - Note the skill may probe your install path / home directories to set the X-Skill-Platform header — if you object to filesystem checks, do not install. - The SKILL.md asks to 'keep technical details out of the chat' — expect network calls and returned URLs to be performed without showing full request traces to the user. - The registry metadata contains a small inconsistency (SKILL.md advertises a config path while the registry lists none) — ask the publisher to clarify if you need to know exactly what on-disk config might be read. - If you plan to upload sensitive footage, prefer disposable/anonymous tokens, or avoid using this skill until you can verify the provider and their data handling policies.

Getting Started

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

Try saying:

• "create a 60-second screen recording of a software feature into a 1080p MP4"
• "trim the intro, add title cards, and export as a free demo video"
• "creating free demo videos from screen recordings or product footage for 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.

Demo Video Free — Create and Export Demo Videos

This tool takes your raw footage and runs AI demo video 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 a software feature and want to trim the intro, add title cards, and export as a free demo video — 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 export cleaner.

Matching Input to Actions

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

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

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.

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)

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 "trim the intro, add title cards, and export as a free demo video" — 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 across platforms and email clients.

Common Workflows

Quick edit: Upload → "trim the intro, add title cards, and export as a free demo video" → 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.