Ai Video Editor Inshot

Turn a 60-second smartphone video clip into 1080p edited video clips just by typing what you need. Whether it's editing short mobile-style videos with transi...

Security Scan

The skill's declared purpose (cloud video editing) matches its runtime instructions and the single required secret (NEMO_TOKEN), but the SKILL.md contains small inconsistencies and asks the agent to infer or read local install/config paths that were not declared—this is unexpected and worth verifying before use.

Purpose & Capability

Name/description describe a cloud video editing service and the skill only requires a single service token (NEMO_TOKEN), which is proportionate and expected for an API-backed editor. The SKILL.md endpoints (mega-api-prod.nemovideo.ai) and workflows align with the stated purpose.

Instruction Scope

Instructions send uploaded videos and commands to an external API (expected), but the frontmatter asks the agent to use a config path (~/.config/nemovideo/) and to detect install path (~/.clawhub/, ~/.cursor/skills/) to set headers. Those filesystem/installation probes are not declared in the registry metadata and broaden the skill's scope (the agent may read local paths it didn't advertise). Also the skill instructs the agent to include attribution headers derived from local paths—this implies inspecting the runtime environment.

Install Mechanism

No install spec and no code files (instruction-only). This minimizes on-disk code execution risk; nothing is downloaded or written by the skill itself.

Credentials

Only NEMO_TOKEN is declared as required, which fits a cloud API service. However, SKILL.md metadata references a configPath (~/.config/nemovideo/) not declared in the registry manifest, suggesting the skill may also read local config files or tokens that were not listed. That mismatch is unexpected and should be clarified.

Persistence & Privilege

The skill is not always-enabled and does not request persistent system-wide privileges. It doesn't instruct modifying other skills or global agent settings.

What to consider before installing

This skill appears to do what it says (cloud video editing) and legitimately needs a NEMO_TOKEN to operate, but before installing or using it you should: 1) Confirm you trust the backend domain (https://mega-api-prod.nemovideo.ai) and understand the service's privacy/retention for uploaded videos. 2) Verify where NEMO_TOKEN comes from and avoid supplying a high-privilege or unrelated token (use a service-specific token). 3) Ask the author or maintainer why SKILL.md mentions ~/.config/nemovideo/ and install-path detection when the registry metadata lists no config paths—this mismatch means the agent may read local files/paths not advertised. 4) Avoid uploading sensitive or private videos until you’ve confirmed data handling practices; test first with non-sensitive sample clips. 5) If you need higher assurance, request an explicit statement from the publisher about what local files (if any) the skill will read and whether any logs or copies of uploads are retained.

Getting Started

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

Try saying:

• "edit a 60-second smartphone video clip into a 1080p MP4"
• "trim the clip, add music, and apply smooth transitions like InShot style"
• "editing short mobile-style videos with transitions and music for TikTok and Instagram 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.

AI Video Editor InShot — Edit and Export Mobile Videos

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

Here's a typical use: you send a a 60-second smartphone video clip, ask for trim the clip, add music, and apply smooth transitions like InShot style, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — vertical 9:16 video works perfectly for Reels and TikTok exports.

Matching Input to Actions

User prompts referencing ai video editor inshot, 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 ai-video-editor-inshot, 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 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)

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

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.

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 clip, add music, and apply smooth transitions like InShot style" → Download MP4. Takes 30-60 seconds 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 music, and apply smooth transitions like InShot style" — 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 social platforms.