Video Maker For Laptop Free

edit video clips into polished MP4 files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. students and casual creators use it for editing a...

Security Scan

The skill appears to be a cloud-based video editor (which explains network calls and a token), but there are internal inconsistencies about required config/env items and the instructions will upload user video files and automatically mint an anonymous token — you should verify the service and privacy implications before installing.

Purpose & Capability

Name/description (cloud video editing) matches the API calls and upload/export flows in SKILL.md. Requesting a single service token (NEMO_TOKEN) is proportionate for a cloud backend. However, there is an inconsistency: registry metadata lists no required config paths, while the skill frontmatter (SKILL.md) declares a config path (~/.config/nemovideo/) and requires NEMO_TOKEN. Also the registry marks NEMO_TOKEN as required, but SKILL.md provides an anonymous-token fallback — this mismatch should be clarified.

Instruction Scope

SKILL.md explicitly instructs the agent to POST video files (multipart) and URLs to an external API (mega-api-prod.nemovideo.ai), create sessions, poll render jobs, and include attribution headers. Those actions are expected for a cloud editing service. The instructions reference local file paths for uploads and suggest auto-detecting the install path for the 'X-Skill-Platform' header — that triggers filesystem inspection (install path detection) which is broader scope than purely network calls and should be confirmed. The skill also auto-requests/creates an anonymous token if no NEMO_TOKEN is present, which has privacy implications because it will send identifying headers (X-Client-Id).

Install Mechanism

No install spec and no code files — instruction-only. This minimizes on-disk persistence and prevents arbitrary third-party code being installed by the skill itself.

Credentials

Only one credential is declared (NEMO_TOKEN / primaryEnv), which is expected for a hosted video-processing API. But SKILL.md will obtain an anonymous token via a POST if NEMO_TOKEN is not present, making the 'required' designation confusing. The SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) while the registry previously reported none — that discrepancy should be reconciled. No other unrelated secrets are requested.

Persistence & Privilege

always:false (default) and no install steps. The skill keeps ephemeral session IDs for jobs, which is normal. It does not request permanent privileged presence or modification of other skills or global agent config in its instructions.

What to consider before installing

This skill is a cloud-based video editor and will upload your video files to https://mega-api-prod.nemovideo.ai for processing; that is expected but has privacy implications — don't send sensitive footage unless you trust the service. Note two inconsistencies to ask the publisher about before installing: (1) the registry marks NEMO_TOKEN as required but SKILL.md will automatically request an anonymous token if none is present (ask whether the skill will silently create/store tokens or require user consent), and (2) SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while the registry reported no required config paths. Also confirm the service's privacy/retention policy and whether uploads are deleted after processing. If you need stronger assurance, request the skill's source/homepage or an explicit privacy statement and confirm where session tokens are stored and for how long.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "trim the intro, add transitions, and"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Video Maker for Laptop Free — Edit and Export Videos Online

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

Say you have a 2-minute screen recording from a laptop and want to trim the intro, add transitions, and export as MP4 — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster in the browser.

Matching Input to Actions

User prompts referencing video maker for laptop 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.

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

Header	Value
X-Skill-Source	video-maker-for-laptop-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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.

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

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)

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 → "trim the intro, add transitions, and export as MP4" → 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 "trim the intro, add transitions, and export as MP4" — 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 devices and platforms.