Ai Demo Video

create product footage into polished demo videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. marketers use it for turning raw screen r...

Security Scan

The skill's requirements and instructions are consistent with a cloud-based video-processing tool, but it will automatically obtain and store an anonymous token and will upload user media to a third-party service — review privacy before use.

Purpose & Capability

Name/description (AI demo video creation) align with the declared requirement (NEMO_TOKEN) and the SKILL.md, which describes uploading video files and calling a rendering API. No unrelated credentials or binaries are requested.

Instruction Scope

The SKILL.md instructs the agent to automatically obtain an anonymous token (POST to /api/auth/anonymous-token) when NEMO_TOKEN is not present, create sessions, upload files, stream SSE, and poll render state. These actions are within the stated purpose but involve sending user media and session tokens to an external domain (mega-api-prod.nemovideo.ai). The doc also mandates attribution headers and platform-detection via install path, and asks to 'store the returned session_id' (storage location not specified). These are expected for a cloud render pipeline but are worth noting for privacy and persistence implications.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. Nothing is written to disk by a packaged installer here; runtime behavior will perform network calls. From an install perspective, risk is low; runtime network activity is the primary surface.

Credentials

Only one env var is required (NEMO_TOKEN), which is proportional to a third-party API. However, the skill will generate an anonymous token itself if NEMO_TOKEN is absent (100 free credits, 7-day expiration). Metadata also lists a config path (~/.config/nemovideo/) even though the SKILL.md does not explicitly require reading/writing that path — this mismatch is minor but worth noting. No unrelated secrets are requested.

Persistence & Privilege

always is false and the skill does not request system-wide privileges. It asks to store session state and may persist an anonymous token to enable subsequent requests, which is normal for a session-based cloud service. It does not request modification of other skills or global agent settings.

Assessment

This skill will upload your videos and related metadata to a third-party rendering service (mega-api-prod.nemovideo.ai). If you do not provide a NEMO_TOKEN, the skill will request an anonymous token on your behalf and store session state for up to 7 days of free credits. Before installing: (1) Confirm you're comfortable uploading potentially sensitive footage to an external service; (2) Prefer supplying your own NEMO_TOKEN from an account you control if you want clearer credential ownership; (3) Note the skill requires attribution headers and will read the agent install path to determine platform — this is for the service's telemetry but is not a secret leak in itself; (4) The metadata lists a config path (~/.config/nemovideo/) — check whether the agent actually writes there if you want to control persistence. If any of the above is unacceptable, do not install or run the skill.

Getting Started

Share your product footage and I'll get started on AI demo creation. Or just tell me what you're thinking.

Try saying:

• "create my product footage"
• "export 1080p MP4"
• "trim the footage, add captions, and"

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 Demo Video — Create and Export Demo Videos

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

Say you have a 2-minute screen recording of a software feature and want to trim the footage, add captions, and highlight key moments with callouts — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter demo clips under 3 minutes process significantly faster.

Matching Input to Actions

User prompts referencing ai 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.

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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-demo-video
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the footage, add captions, and highlight key moments with callouts" — 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 presentation and sharing platforms.

Common Workflows

Quick edit: Upload → "trim the footage, add captions, and highlight key moments with callouts" → 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.