For Beginners Editor Online

Skip the learning curve of professional editing software. Describe what you want — trim the video, add transitions, and put text titles at the start — and ge...

Security Scan

The skill's runtime instructions mostly match a cloud video-editing service, but small mismatches (undeclared config path in the skill frontmatter, vague 'install path' detection, and automatic token creation) leave open questions that should be clarified before trusting it with files or tokens.

Purpose & Capability

The name/description and runtime instructions are coherent for a cloud AI video editor: it requires a service token, creates sessions, uploads video, and requests rendering. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this discrepancy is unexplained.

Instruction Scope

Instructions direct the agent to call the service APIs, upload user-provided files, stream SSE responses, and poll session state — all expected for this use case. They do not (explicitly) instruct reading unrelated system files, but they do ask to auto-detect an 'install path' for X-Skill-Platform which is vague in an instruction-only skill and could cause unexpected behavior if implemented broadly.

Install Mechanism

No install spec and no code files are present, so there's nothing extra being downloaded or written by an installer — lowest-risk install profile.

Credentials

Only a single credential (NEMO_TOKEN) is declared, which is appropriate for a cloud API. But SKILL.md includes a flow to POST for an anonymous token and the frontmatter references a config path for potential persistence (~/.config/nemovideo/). The registry listing did not declare that config path. It's unclear whether the skill will persist tokens locally or where it expects the token to live.

Persistence & Privilege

always:false (default) and no special privileges are requested. The skill's autonomous invocation is the platform default and does not by itself raise extra concerns.

What to consider before installing

This appears to be a legitimate cloud video-editing workflow, but there are a few things to check before using it with your files or tokens: - Confirm where and whether the skill will persist the anonymous token (SKILL.md mentions ~/.config/nemovideo/ in its frontmatter but the registry did not list any config paths). If the skill writes tokens or other data to disk, ask where and with what permissions. - Understand that the skill will call a remote API (mega-api-prod.nemovideo.ai) and upload your video files. Only provide files you are comfortable sending to an unknown backend and review any privacy/retention policy from the service owner. - The skill will generate an anonymous token if none is supplied; verify token scope, expiry, and whether it can be revoked. Do not provide broader credentials (AWS, GitHub, etc.) — they are not needed here. - Ask the publisher for a homepage or documentation and for clarification about the X-Skill-Platform 'install path' auto-detection to avoid accidental exposure of environment details. If you cannot get satisfactory answers, consider running this skill only in an isolated environment or avoid sharing sensitive footage or account credentials.

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 video, add transitions, and"

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.

For Beginners Editor Online — Edit and Export Videos Online

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 and want to trim the video, 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 faster processing as a beginner.

Matching Input to Actions

User prompts referencing for beginners editor online, 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.

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

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

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.

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.

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.

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

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)

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

Common Workflows

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

Tips and Tricks

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