Movie Maker Chromebook Free

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

Security Scan

This is an instruction-only cloud video-editing skill that consistently uses a single service credential (NEMO_TOKEN) and API endpoints that match its described purpose; no unrelated credentials, installs, or excessive privileges are requested.

Purpose & Capability

The skill's name/description (cloud video editing, MP4 exports) aligns with the actions in SKILL.md (session creation, uploads, render/export endpoints). Requiring a NEMO_TOKEN and a config path for nemovideo is reasonable. Minor mismatch: registry metadata at the top of the report lists no required config paths, but the SKILL.md frontmatter declares configPaths (~/.config/nemovideo/). This inconsistency should be clarified but does not by itself indicate malicious intent.

Instruction Scope

Instructions stay within the editing/export workflow: check/create token, create a session, send SSE for edits, upload files, poll render status, return download URL. It explicitly directs uploads of user files to the stated nemovideo API and to generate anonymous tokens if none exist. Two things to note: (1) the skill derives some headers from its YAML frontmatter and checks install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform — this may involve probing common install locations but is scoped to determining a header value; (2) the instructions will cause user media to be uploaded to a third-party service (mega-api-prod.nemovideo.ai), which is expected for cloud rendering but is a privacy consideration.

Install Mechanism

No install spec and no code files — instruction-only. This is low risk because nothing is written to disk by an installer.

Credentials

Only one environment credential is declared (NEMO_TOKEN) and it is the logical credential for calling the described API. The SKILL.md also describes creating an anonymous token if none is present (100 free credits, 7-day expiry). That behavior is consistent, but users should be aware the skill will persist/use a token and may store it in the indicated config path. No unrelated secrets or multiservice credentials are requested.

Persistence & Privilege

always:false and user-invocable:true (normal). The skill does not request elevated or permanent platform privileges. Autonomous invocation is permitted by default but is not combined with any high-risk capabilities here.

Assessment

This skill appears coherent for cloud video editing, but consider the privacy and trust implications before uploading videos to the remote service (mega-api-prod.nemovideo.ai). Verify you trust the service owner and that you are comfortable with an anonymous token being created/stored (the skill says anonymous tokens expire in 7 days). Clarify the small metadata mismatch (SKILL.md lists a config path while registry metadata omitted it). Do not provide other unrelated credentials. If you need stronger guarantees, ask the publisher for a privacy/terms link or prefer an editor that runs locally.

Getting Started

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

Try saying:

• "edit three 30-second clips recorded on a Chromebook into a 1080p MP4"
• "trim the clips, add transitions, and export as a single video"
• "editing and combining video clips into a finished movie on a Chromebook for students and casual creators"

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.

Movie Maker Chromebook Free — Edit and Export MP4 Videos

Send me your video clips and describe the result you want. The AI video editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload three 30-second clips recorded on a Chromebook, type "trim the clips, add transitions, and export as a single video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: since Chromebooks run everything in the browser, no download is needed — just upload and start editing.

Matching Input to Actions

User prompts referencing movie maker chromebook 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.

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 movie-maker-chromebook-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).

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

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.

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)

Common Workflows

Quick edit: Upload → "trim the clips, add transitions, and export as a single 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 "trim the clips, add transitions, and export as a single video" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, WebM, MOV, AVI for the smoothest experience.

Export as MP4 for widest compatibility across devices and platforms.