Video Editor Modi

edit raw video footage into style-edited videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and social media editors...

Security Scan

The skill's behaviour generally matches a cloud video-editing integration, but there are small mismatches and privacy/operational choices (automatic backend connection, token generation/storage, and a config-path discrepancy) that merit caution before installing.

Purpose & Capability

The skill name/description align with the runtime instructions (upload video, request edits, download processed MP4). Requesting a single service token (NEMO_TOKEN) is consistent with a backend API integration. However, SKILL.md declares a config path (~/.config/nemovideo/) in its frontmatter while the registry metadata reported no required config paths — this mismatch should be clarified.

Instruction Scope

Instructions direct the agent to automatically connect to the remote API the first time the skill is opened (network calls to https://mega-api-prod.nemovideo.ai), generate anonymous tokens if NEMO_TOKEN isn't present, create and store sessions, and include attribution headers by detecting install paths on disk. Automatic network activity and filesystem detection (to infer install path) expand the skill's scope beyond simple user-triggered uploads and deserve explicit user consent/visibility.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing will be written to disk by an installer. That's the lowest-risk install mechanism.

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportionate to a cloud API. That said: SKILL.md both expects NEMO_TOKEN and also instructs the agent to generate and use an anonymous token when none is set — this inconsistency should be resolved. The skill also instructs 'don't display raw API responses or token values to the user', which reduces transparency about credential handling.

Persistence & Privilege

The skill instructs storing the returned session_id/token for subsequent requests and references a config directory (~/.config/nemovideo/) in its frontmatter. While storing session state is reasonable for a remote service, the combination of automatic token/session creation, implied persistence on disk, and filesystem detection raises modest privilege/persistence concerns that should be explained (where/how tokens/session IDs are stored, retention, and deletion behavior).

What to consider before installing

This skill appears to be a normal cloud-based video editor, but before installing consider: 1) It will contact a third-party API (mega-api-prod.nemovideo.ai) automatically the first time it runs and may generate and store an anonymous token/session—confirm you are comfortable with that network activity and with where session data will be saved. 2) Clarify the config-path discrepancy (SKILL.md references ~/.config/nemovideo/ but registry metadata lists none). 3) If you prefer control, set your own NEMO_TOKEN (if available) rather than relying on auto-created anonymous tokens, and ask the publisher where tokens and session IDs are stored and how to revoke them. 4) Avoid uploading sensitive footage until you confirm the vendor’s privacy/security posture and that their domain/service is legitimate. If you need higher assurance, request the skill’s source/homepage or ask the publisher to explain the token/session lifecycle and file/storage locations.

Getting Started

Send me your raw video footage and I'll handle the AI style-based editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute unedited talking-head recording into a 1080p MP4"
• "edit this video in Modi style with cuts, pacing, and transitions"
• "applying a specific editing style or mood to raw video footage for content creators and social media editors"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Editor Modi — Edit Videos in Modi Style

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

Say you have a 2-minute unedited talking-head recording and want to edit this video in Modi style with cuts, pacing, and transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 90 seconds produce the most consistent style results.

Matching Input to Actions

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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

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

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 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 "edit this video in Modi style with cuts, pacing, and transitions" — 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 and devices.

Common Workflows

Quick edit: Upload → "edit this video in Modi style with cuts, pacing, and transitions" → 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.