Editor For Beginners

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

Security Scan

The skill appears to do what it says — remote AI video editing via nemo backend — and its requirements and instructions are generally proportional and consistent with that purpose.

Purpose & Capability

The skill's name and description match the actions in SKILL.md: uploading video files and calling a remote nemovideo.ai API to edit and render. One minor inconsistency: the SKILL.md frontmatter lists a configPaths entry (~/.config/nemovideo/) while the registry metadata reported no required config paths. That mismatch should be clarified but does not by itself contradict the stated purpose.

Instruction Scope

Instructions are focused on establishing a session, uploading media, streaming edits (SSE), polling state, and exporting results from the remote rendering backend. The skill explicitly sends files and metadata to mega-api-prod.nemovideo.ai and directs the agent to check the environment for NEMO_TOKEN or request an anonymous token if missing. There is no instruction to read unrelated files or other credentials.

Install Mechanism

This is an instruction-only skill with no install spec or code files — lowest-risk installation model. All network activity is to the documented nemovideo.ai endpoints.

Credentials

The only required credential is NEMO_TOKEN (declared as primaryEnv). The SKILL.md also explains how to obtain an anonymous token if none is present. This is proportionate to a cloud edit/export service. Minor note: the frontmatter includes a configPaths hint (~/.config/nemovideo/) which suggests the skill might look for or use a local config directory; the registry metadata did not list required config paths — clarify whether the skill will read/write that path.

Persistence & Privilege

always is false and the skill does not request system-wide privileges or modifications to other skills. It instructs the agent to maintain an ephemeral session_id for operations; nothing requires permanent presence or elevated agent privileges.

Assessment

This skill uploads your video files and metadata to an external service at mega-api-prod.nemovideo.ai and uses a NEMO_TOKEN for authorization (or will fetch an anonymous token for short-lived use). Before installing: (1) confirm you are comfortable uploading the content (don’t upload sensitive private data), (2) verify the nemovideo.ai domain and any privacy/billing terms, (3) note the skill may look for ~/.config/nemovideo/ (clarify whether it will read or write files there), and (4) if you allow the skill to obtain an anonymous token, be aware tokens expire and may grant rendering/credit usage — revoke or rotate tokens if needed. The metadata mismatch about config paths is a minor inconsistency worth asking the skill author to clarify but does not indicate malicious behavior.

Getting Started

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

Try saying:

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

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.

Editor for Beginners — Edit and Export Videos Easily

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

A quick example: upload a 2-minute smartphone recording of a birthday party, type "trim the shaky parts, add background music, and put text titles at the start", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: keep clips under 3 minutes for the fastest processing and simplest results.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

• X-Skill-Source: editor-for-beginners
• 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.

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the shaky parts, 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 phones, social media, and web.

Common Workflows

Quick edit: Upload → "trim the shaky parts, 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.