Video Editing With Effects Free

edit video clips into effects-enhanced clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for adding visual eff...

Security Scan

The skill's networking and credential use match a video-editing service, but there are inconsistencies about filesystem/config access and the SKILL.md instructs the agent to read/write local config and detect install paths — things not declared in the registry metadata.

Purpose & Capability

The skill's declared purpose (cloud video editing) aligns with the single requested credential (NEMO_TOKEN) and the API endpoints in the SKILL.md. However, the frontmatter metadata in SKILL.md requests a config path (~/.config/nemovideo/) and instructs detection of install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) for X-Skill-Platform attribution — filesystem access beyond just handling uploaded videos is implied. The registry entry earlier listed no required config paths, creating an internal inconsistency.

Instruction Scope

The instructions require contacting an external API (mega-api-prod.nemovideo.ai) for anonymous tokens and session creation and instruct saving session_id and token. They also instruct reading this SKILL.md frontmatter and detecting local install paths to generate X-Skill-Platform header — which implies reading the user's filesystem. While these actions can be legitimate for a cloud editing skill, they expand scope from purely handling uploaded media to reading/writing local config and determining install locations. The SKILL.md explicitly instructs not to print tokens/JSON, but it does not describe where or how long the token/session will be persisted.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only. That minimizes installation risk because nothing is downloaded or executed on disk by the skill itself.

Credentials

Only one environment variable (NEMO_TOKEN) is required, which is proportionate for an API-backed service. However, SKILL.md describes generating an anonymous token and implies storing it (100 credits, 7-day expiry) and also references a local config path in its metadata. The registry listing omitted this config path, so it's unclear whether/where tokens or session state will be written.

Persistence & Privilege

The skill does not request always:true and allows normal model invocation. It does instruct the agent to persist a session_id and use a token (possibly saved under ~/.config/nemovideo/ per SKILL.md frontmatter). Persisting tokens/sessions and probing install directories is privilege-bearing (filesystem read/write) but not inherently malicious; the mismatch with the registry's claimed lack of config paths is the main concern.

What to consider before installing

This skill mostly behaves like a cloud video-editing integration and only asks for one credential (NEMO_TOKEN), which is expected. Before installing or using it, confirm: 1) whether you want the agent to be able to read/write ~/.config/nemovideo/ (the SKILL.md mentions this) and to probe install paths (it uses that to set X-Skill-Platform); 2) where the token/session will be stored and how to revoke or delete it (SKILL.md suggests the anonymous token expires in 7 days but also asks you to save it); 3) that the external domain (mega-api-prod.nemovideo.ai) is acceptable for your data — uploaded videos will be sent there. If you are unsure, prefer using an anonymous token (short-lived) or keep NEMO_TOKEN unset and monitor what gets written to your home config directory. The inconsistency between the registry metadata (no config paths) and the SKILL.md (includes ~/.config/nemovideo/) is the primary red flag — ask the publisher to clarify storage behavior before granting persistent credentials or allowing filesystem writes.

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

• "edit a 2-minute vlog clip recorded on a smartphone into a 1080p MP4"
• "add transitions, color grading, and motion effects between scenes"
• "adding visual effects and transitions to raw video clips for content creators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Editing With Effects Free — Edit Videos With Visual Effects

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

Here's a typical use: you send a a 2-minute vlog clip recorded on a smartphone, ask for add transitions, color grading, and motion effects between scenes, 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 — shorter clips under 60 seconds process faster and give you more control over effect placement.

Matching Input to Actions

User prompts referencing video editing with effects free, 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.

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

• X-Skill-Source: video-editing-with-effects-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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 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)

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 → "add transitions, color grading, and motion effects between scenes" → 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 "add transitions, color grading, and motion effects between scenes" — 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 platforms like YouTube, TikTok, and Instagram.