Video Editing For Beginners

Get edited MP4 videos ready to post, without touching a single slider. Upload your raw video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "tr...

Security Scan

The skill's runtime instructions largely match a cloud-based video-editing service, but there are mismatches in declared requirements (NEMO_TOKEN listed as required even though the SKILL.md generates an anonymous token if missing) and an unexplained config-path metadata entry; the skill will also upload user video files to an external API — review trust and privacy implications before installing.

Purpose & Capability

The skill's stated purpose (cloud video editing) aligns with the network calls and upload behavior in SKILL.md. However, registry metadata declares NEMO_TOKEN as a required env var/primary credential while the instructions explicitly describe generating an anonymous token automatically if NEMO_TOKEN is not present — this is an internal inconsistency. The frontmatter also lists a config path (~/.config/nemovideo/) even though registry 'Required config paths' reported none, which is unexplained.

Instruction Scope

The instructions are focused on interacting with the nemo API: acquiring (or using) a token, creating a session, uploading user media, streaming edits via SSE, and polling export status. Those actions are consistent with editing. The skill instructs the agent to upload local files (uses multipart files=@/path) and to auto-connect on first open, which means it will read user-supplied files and send them to the external service. The SKILL.md also asks the agent to auto-detect an 'install path' to set X-Skill-Platform — implying access to local environment metadata. These behaviors are expected for a cloud editor but worth noting from a privacy/exfiltration perspective.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing is written to disk by an installer. That is the lowest-risk install profile.

Credentials

Only one credential (NEMO_TOKEN) is declared, which is reasonable for an external API. However, metadata/config inconsistency is concerning: the SKILL.md treats NEMO_TOKEN as optional (creates anonymous token when absent) while the registry lists it as required/primary. The frontmatter also references a user config directory (~/.config/nemovideo/) — requesting access to a home-config path should be justified (e.g., persistent session storage). Because the skill both uploads user media and may read local paths, ensure the requested token and config access are intentional and minimal.

Persistence & Privilege

The skill does not request always:true and is user-invocable only. It stores session_id for ongoing operations, which is normal for a remote service. It does not declare modifications to other skills or system-wide configuration.

What to consider before installing

Before installing: 1) Understand that this skill uploads any video files you provide to https://mega-api-prod.nemovideo.ai — do not send sensitive content you wouldn't want processed by a third party. 2) The skill can create an anonymous token automatically; if you already have a NEMO_TOKEN, confirm which token will be used and where tokens/sessions are stored (the metadata hints at ~/.config/nemovideo/). 3) The registry metadata and SKILL.md disagree about whether NEMO_TOKEN is required — ask the publisher to clarify storage and lifecycle of tokens (how to revoke/delete). 4) Verify the service domain and privacy policy/outbound behavior (who has access to uploaded media, retention, deletion). 5) If you prefer, avoid giving the agent direct file-system paths; upload via URLs or a trusted upload dialog so you control what is sent. If you cannot verify the service/operator, treat this skill as higher-risk and avoid uploading private content.

Getting Started

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

Try saying:

• "edit my raw video clips"
• "export 1080p MP4"
• "trim the pauses, add background music,"

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.

Video Editing for Beginners — Edit and Export Polished Videos

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

Here's a typical use: you send a a 2-minute unedited phone recording, ask for trim the pauses, add background music, and put text titles at the start, 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 — keep clips under 3 minutes for faster processing and more accurate AI edits.

Matching Input to Actions

User prompts referencing video editing for beginners, 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.

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

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

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

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

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.

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 pauses, add background music, and put text titles at the start" — 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 YouTube, TikTok, and Instagram.

Common Workflows

Quick edit: Upload → "trim the pauses, add background music, and put text titles at the start" → 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.