Google Video Editor

Skip the learning curve of professional editing software. Describe what you want — trim the footage, add transitions, and include background music — and get...

Security Scan

The skill's declared purpose (cloud video editing) matches its runtime instructions and required credential (NEMO_TOKEN); it uploads user video files to an external service and can obtain an anonymous token automatically, which is coherent but has privacy implications to consider.

Purpose & Capability

Name/description describe a cloud video editor and the instructions call out endpoints, uploads, session creation, SSE, and export APIs on mega-api-prod.nemovideo.ai. Requesting a single service token (NEMO_TOKEN) is appropriate for this purpose. Minor inconsistency: the top-level registry said no required config paths, but the skill frontmatter references a config path (~/.config/nemovideo/).

Instruction Scope

The SKILL.md explicitly instructs the agent to upload user video files and call the remote API, create or reuse a session, stream SSE, poll render status, and include attribution headers. All actions are consistent with a cloud editing service. Important privacy note: user media and metadata will be sent to an external domain; the instructions also include an automatic anonymous-token acquisition flow if NEMO_TOKEN is not present.

Install Mechanism

No install spec and no code files — instruction-only skill. This is the lowest-risk install model and consistent with the described cloud-only behavior.

Credentials

Only one environment variable (NEMO_TOKEN) is required, and that's proportionate to a remote API integration. However, the skill tells the agent how to auto-create an anonymous NEMO_TOKEN via a network call if none is present, meaning the agent can obtain credentials without explicit user-provided tokens. Also, the frontmatter references a local config path (~/.config/nemovideo/) even though registry metadata showed none — verify whether the skill will read or write that path.

Persistence & Privilege

always:false and no install actions; the skill does not request permanent platform presence or system changes. Model invocation is allowed (default), which is normal for skills. There are no instructions to modify other skills or system-wide settings.

Assessment

This skill appears coherent for a cloud-based video editor, but it will upload any videos you provide to mega-api-prod.nemovideo.ai and will use or obtain a NEMO_TOKEN that authorizes those operations. Before installing or using it: (1) avoid uploading sensitive/privileged footage until you confirm the service's privacy/security posture; (2) verify the service identity and privacy policy (the skill has no homepage and unknown owner); (3) confirm whether the skill will read/write ~/.config/nemovideo/ or persist tokens locally; (4) if your organization restricts outbound media uploads or automatic credential creation, do not install or require explicit approval; (5) if you need higher assurance, ask the publisher for a homepage, docs, or a verified registry entry before use.

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

• "edit a 2-minute screen recording or phone video into a 1080p MP4"
• "trim the footage, add transitions, and include background music"
• "editing and polishing raw video clips quickly online for casual creators and marketers"

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.

Google Video Editor — Edit and Export Polished Videos

Drop your video clips in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute screen recording or phone video, ask for trim the footage, add transitions, and include background music, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing google video editor, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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	google-video-editor
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

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

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.

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 footage, add transitions, and include background music" → 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 footage, add transitions, and include background music" — 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.