For Beginners Capcut Video Editor

edit raw video clips into edited video clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. beginner video creators use it for editing sh...

Security Scan

The skill broadly matches a remote AI video-editing service (it needs/uses a NEMO_TOKEN and uploads videos to a remote API), but there are inconsistencies in its declared metadata and a few privacy/networking behaviors you should be aware of before using it.

Purpose & Capability

The name and description describe a cloud-based video editor; requesting a NEMO_TOKEN to call a remote nemovideo.ai API is consistent with that purpose. However, the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained and could indicate sloppy metadata or that the skill expects to read local config files it didn't declare.

Instruction Scope

The instructions direct the agent to contact https://mega-api-prod.nemovideo.ai for auth, session creation, SSE editing, uploads, and exports, and to upload user-provided video files (up to 500MB). They also describe creating an anonymous token if NEMO_TOKEN is absent. These behaviours are coherent with remote editing but mean user files and session info will be sent to a third party; the skill also asks to include attribution headers and to 'auto-detect' platform from an install path (which could require reading local environment/install path). The SKILL.md explicitly tells the agent to avoid exposing technical details in chat — this is a behaviour note but not by itself malicious.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk (nothing is written to disk by an installer).

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportional for a hosted video editing API. Caveats: the frontmatter mentions a local config path (~/.config/nemovideo/), inconsistent with registry fields; the instructions also propose automatically obtaining an anonymous token via the network if NEMO_TOKEN is not present, which is reasonable but worth noting because it triggers network requests and use of returned tokens. Attribution headers and platform auto-detection may leak agent environment or install-path information.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and is invocation-limited. It uses session tokens for the remote service (normal for this kind of integration) but does not request persistent system-level privileges.

What to consider before installing

This skill will upload any video files you provide to a third-party service (mega-api-prod.nemovideo.ai) and will use either a NEMO_TOKEN you supply or obtain an anonymous token for you. Before using it: (1) Only upload non-sensitive videos you are comfortable sending to an external service. (2) Prefer setting your own NEMO_TOKEN if you trust an account provider; anonymous tokens are ephemeral but still send data off-device. (3) Note the SKILL.md mentions a local config path (~/.config/nemovideo/) even though the registry doesn't require it — expect the skill might try to read local config or infer install paths, which could expose environment info. (4) The skill has no published source/homepage and the owner is not identifiable from the manifest; verify the service’s privacy/security practices (nemovideo.ai) before proceeding. If you need stronger guarantees about where data goes, do not use this skill or ask for more information about the backend and privacy policy from the publisher.

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 60-second phone-recorded clip into a 1080p MP4"
• "trim the clip, add transitions, and overlay background music"
• "editing short videos with simple cuts, transitions, and music for beginner video creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

For Beginners CapCut Video Editor — Edit and Export Beginner Videos

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

A quick example: upload a 60-second phone-recorded clip, type "trim the clip, add transitions, and overlay background music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process faster and are easier to manage as a beginner.

Matching Input to Actions

User prompts referencing for beginners capcut 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.

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

Header	Value
X-Skill-Source	for-beginners-capcut-video-editor
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.

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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 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 clip, add transitions, and overlay 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 clip, add transitions, and overlay 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 phones, social media, and desktop.