Editor Ai With

edit raw video footage into edited MP4 videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and marketers use it for ed...

Security Scan

The skill's behavior mostly matches a cloud video-editing tool, but there are inconsistencies (unknown source, mixed metadata about local config access) and privacy risks from uploading video to an external API that you should understand before installing.

Purpose & Capability

The name/description (AI video editing) matches the runtime instructions (upload, render, export via nemovideo API). Requested credential (NEMO_TOKEN) is proportional. However the SKILL.md frontmatter declares access to a local config path (~/.config/nemovideo/) and instructions add an install-path-derived header, which are not documented elsewhere and are unexpected for a simple editing helper.

Instruction Scope

Instructions are concrete and confined to the external nemovideo API (session creation, SSE chat, upload, export). The skill instructs the agent to upload user-supplied video files to the third-party service and to create an anonymous token if no NEMO_TOKEN is present. It does not instruct reading arbitrary system files beyond the install-path/config-path detection noted above.

Install Mechanism

Instruction-only skill with no install spec or bundled code — lowest install risk. Nothing is downloaded or written by an installer step.

Credentials

Only one credential (NEMO_TOKEN) is declared which fits the API usage. But the frontmatter's configPaths (~/.config/nemovideo/) implies the skill may read local config files (potentially containing tokens) even though registry metadata listed no required config paths—this mismatch is unexplained and increases risk of local credential access.

Persistence & Privilege

always:false (not force-included) and no install-time persistence requested. The skill can be invoked autonomously by the agent (platform default), which increases blast radius if the skill is malicious, but this alone is not unusual and is not combined with other high privileges here.

What to consider before installing

This skill appears to be a straightforward cloud video editor, but take these precautions before installing or using it: - Verify the service and owner: there is no homepage and the publisher ID is opaque. Ask for the official service URL, privacy policy, and data-retention rules before uploading sensitive footage. - Token handling: the skill will use NEMO_TOKEN if present, otherwise it will call the API to mint an anonymous token. If you have a stored nemo token in ~/.config/nemovideo/, the skill may read it — either remove or inspect that file first if you don't want existing tokens used. Prefer using an ephemeral/anonymous token for sensitive content. - Data exposure: using the skill uploads your video to https://mega-api-prod.nemovideo.ai. Don't upload confidential material until you confirm how data is processed, stored, and deleted. - Headers/install-path detection: the skill adds headers based on install path (~/.clawhub/, ~/.cursor/skills/) which implies it may check filesystem paths — be cautious about local metadata leakage. - If you want extra safety: ask the publisher for source code or a privacy/security whitepaper; restrict the agent's ability to call external skills if your platform allows; and test with non-sensitive sample videos first. If you can obtain a verified homepage/source and an explicit statement about local config access, that would reduce the remaining concerns.

Getting Started

Got raw video footage 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 3-minute raw interview recording into a 1080p MP4"
• "trim the pauses, add transitions, and overlay background music"
• "editing videos with AI-powered tools and effects for content creators and marketers"

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.

Editor AI With — Edit Videos With AI Tools

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

Here's a typical use: you send a a 3-minute raw interview recording, ask for trim the pauses, add transitions, and overlay background music, 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 2 minutes process significantly faster.

Matching Input to Actions

User prompts referencing editor ai with, 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 calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is editor-ai-with, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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

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)

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

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.

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

Tips and Tricks

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

Common Workflows

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