Free Video Maker In Pc

Turn a 2-minute screen recording or five product photos into 1080p polished MP4 videos just by typing what you need. Whether it's creating and editing videos...

Security Scan

The skill's declared purpose (cloud video creation) mostly matches its runtime instructions and single required credential (NEMO_TOKEN), but there are inconsistencies in the metadata and some instruction-level behaviors (automatic network calls, local file uploads, and stealthy token acquisition) that merit caution before installing or using it.

Purpose & Capability

Name/description (cloud video creation) aligns with the API endpoints and upload/export workflow described in SKILL.md. The primaryEnv (NEMO_TOKEN) is appropriate for a cloud video service. However, the SKILL.md frontmatter includes a required config path (~/.config/nemovideo/) while the registry summary lists no configPaths — this metadata mismatch is an incoherence.

Instruction Scope

The instructions direct the agent to: read the skill's YAML frontmatter and detect install path, establish network sessions to mega-api-prod.nemovideo.ai, upload user files (multipart with local file paths), poll render status, and (if no env token) POST to an anonymous-token endpoint to obtain a token. These actions are expected for a cloud rendering service, but notable concerns: (1) automatic anonymous-token acquisition performs network activity without an explicit user-provided credential; (2) instructions tell the agent to keep implementation details out of chat, which reduces transparency about what data is sent; (3) reading install paths / config paths may require filesystem access beyond just reading the skill file.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written to disk by an installer step as provided.

Credentials

Only one credential (NEMO_TOKEN / primaryEnv) is declared in frontmatter, which is proportional to a cloud API integration. The skill also documents an anonymous-token fallback (POST to /api/auth/anonymous-token). The earlier-noted mismatch about configPaths (~/.config/nemovideo/) appears in the SKILL.md metadata but is not listed in the registry summary — this should be clarified because config path access could expose persisted tokens or cached files.

Persistence & Privilege

always is false, no install spec, and the skill does not request elevated or permanent platform privileges. It does not attempt to modify other skills or system-wide settings in the provided instructions.

What to consider before installing

This skill will upload the files you provide to mega-api-prod.nemovideo.ai and uses a NEMO_TOKEN (or will fetch an anonymous token automatically) to create and run render jobs. Before installing or using it: (1) Be aware that any media you send will be transmitted to an external service — do not upload sensitive or private content unless you trust the service and have confirmed its data handling policy. (2) Verify what NEMO_TOKEN grants (scope, expiry) and prefer using a limited-scope or ephemeral token if possible. (3) Ask the publisher to clarify the metadata mismatch: the SKILL.md mentions ~/.config/nemovideo/ as a config path but the registry listing does not — confirm whether the skill will read or write that directory. (4) If you want transparency, request the skill not to acquire anonymous tokens automatically or to prompt the user before making network calls. These steps reduce the privacy and security risks associated with file uploads and automatic token issuance.

Getting Started

Share your video clips or images and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "create my video clips or images"
• "export 1080p MP4"
• "combine my clips, add background music,"

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.

Free Video Maker in PC — Create and Export PC Videos

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

Say you have a 2-minute screen recording or five product photos and want to combine my clips, add background music, and export as a shareable video — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes process significantly faster in the browser.

Matching Input to Actions

User prompts referencing free video maker in pc, 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: free-video-maker-in-pc
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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.

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)

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

Common Workflows

Quick edit: Upload → "combine my clips, add background music, and export as a shareable 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "combine my clips, add background music, and export as a shareable 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 devices.