Video Editor Software 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's functionality (cloud-based AI video editing) matches its requests in broad strokes, but there are several inconsistencies and minor risks (metadata mismatches, unclear platform attribution, and token handling) you should review before installing.

Purpose & Capability

The stated purpose (AI-assisted cloud video editing) aligns with the API endpoints and upload/export flow described in SKILL.md and with requiring a NEMO_TOKEN. That token is a reasonable credential for a cloud editing backend. However, the skill's frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata earlier listed no required config paths — a mismatch in declared resource access.

Instruction Scope

SKILL.md instructs the agent to read NEMO_TOKEN from the environment and, if absent, call an anonymous-token endpoint to obtain one. It also describes uploading files (multipart -F "files=@/path") and storing session_id for subsequent operations. The instructions don't explicitly limit file reads to user-provided uploads vs arbitrary local filesystem paths — the multipart example implies reading local paths. The skill also requires per-request attribution headers including an install-path-derived `X-Skill-Platform`, but there is no install spec to determine an install path, creating ambiguity about how to populate that header.

Install Mechanism

There is no install spec and no files to be written to disk (instruction-only skill). This is the lowest-risk install mechanism. Nothing in the package attempts to download or install external binaries.

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportionate for a cloud API. The skill also documents an anonymous-token fallback and instructs generation of a UUID client id. That's reasonable, but users should be aware that providing a personal NEMO_TOKEN likely grants the skill access to their account (credits, uploads, renders). The frontmatter also mentions a config path (~/.config/nemovideo/) which was not declared in the registry metadata — a small inconsistency worth clarifying.

Persistence & Privilege

always:false and no install-time persistence are appropriate. The instructions say to retain session_id during a session (ephemeral), which is expected for a cloud job workflow. The skill does not request permanent presence or modify other skills' configs.

What to consider before installing

This skill is an instruction-only connector to a third-party cloud video editing service and mostly behaves as described, but check these before installing: - Verify the endpoint domain (mega-api-prod.nemovideo.ai) is a service you trust. Uploaded videos and derived assets will be sent off-platform. - Prefer using the anonymous-token flow instead of supplying a personal NEMO_TOKEN unless you trust the service and understand what account-level access the token grants (credits, stored media, billing). - Ask the publisher to clarify the config path mention (~/.config/nemovideo/) and how the X-Skill-Platform header should be determined when there's no install path — ambiguous behavior could lead to unexpected headers or dropped requests. - Confirm how long uploads and rendered outputs are retained and how to delete them (privacy/retention). Avoid uploading sensitive content until retention and access controls are clear. - Because SKILL.md shows examples of reading local file paths for uploads, ensure the platform only allows the skill to access files you explicitly supply, not arbitrary filesystem paths. If you need higher assurance, request the API docs or the service's privacy/security policy and ask the publisher to fix the metadata inconsistencies before installing.

Getting Started

Got raw video clips to work with? Send it over and tell me what you need — I'll take care of the AI-assisted video editing.

Try saying:

• "edit a 2-minute smartphone recording of a birthday party into a 1080p MP4"
• "trim the shaky parts, add transitions, and put text titles at the start"
• "turning raw footage into a clean, shareable video without prior editing experience for first-time video creators and casual content makers"

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 Editor Software for Beginners — Edit and Export Videos Easily

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

Say you have a 2-minute smartphone recording of a birthday party and want to trim the shaky parts, add transitions, and put text titles at the start — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: keep clips under 3 minutes for the fastest processing and smoothest AI suggestions.

Matching Input to Actions

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

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.

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

Header	Value
X-Skill-Source	video-editor-software-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 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)

Tips and Tricks

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