Instagram Video Editor Web

Skip the learning curve of professional editing software. Describe what you want — crop to 9:16, add captions, and trim the intro silence — and get Instagram...

Security Scan

This instruction-only skill is coherent with its stated purpose: it uploads user video files to a named cloud rendering API and uses a single service token (NEMO_TOKEN) to operate.

Purpose & Capability

Name/description (AI cloud video editing) matches the declared requirement (NEMO_TOKEN) and the runtime instructions (create session, upload video, render/export). The declared config path (~/.config/nemovideo/) and primaryEnv (NEMO_TOKEN) are consistent with a service-backed editor.

Instruction Scope

SKILL.md directs the agent to upload user video files, call the nemo backend (mega-api-prod.nemovideo.ai) for anonymous-token creation, session creation, SSE message streams, uploads and polling exports. It also reads this file's frontmatter and may probe install paths to set X-Skill-Platform. These actions are within the skill's stated purpose but are privacy-sensitive (user videos and tokens are transmitted to a third-party API).

Install Mechanism

Instruction-only skill with no install steps or downloaded code — lowest install risk. No external binaries or archives are pulled.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv). The skill can generate an anonymous token if none is present; no unrelated credentials or broad environment access are requested.

Persistence & Privilege

always is false and the skill does not request system-wide changes. It will maintain session_id/client-id for operations (normal for a cloud-backed skill). Autonomous invocation is enabled by default (expected) but not combined with other concerning privileges.

Assessment

This skill will upload your video files and use a NEMO_TOKEN (or obtain an anonymous one) to call a third‑party API at mega-api-prod.nemovideo.ai. Before installing: 1) Confirm you are comfortable with uploading potentially sensitive video/audio to that service and review its privacy/terms; 2) Prefer providing a scoped service token or let the skill use the anonymous token flow if you do not want to supply credentials; 3) Understand exported files, tokens, and session IDs are sent over the network—treat NEMO_TOKEN like an account credential; 4) Note tokens expire (7 days) and there are rate/credit rules; 5) If you need greater assurance, verify the service domain and policy, or run editing locally with tools you control. Overall the skill appears consistent with its stated purpose, but it will transmit data off‑device so consider privacy and billing implications.

Getting Started

Share your video clips and I'll get started on AI video editing. Or just tell me what you're thinking.

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "crop to 9:16, add captions, and"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Instagram Video Editor Web — Edit and Export Instagram Videos

Drop your 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 30-second vertical phone video, ask for crop to 9:16, add captions, and trim the intro silence, 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 natively so no manual cropping is needed for Reels.

Matching Input to Actions

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

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

• X-Skill-Source: instagram-video-editor-web
• 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

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.

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)

Common Workflows

Quick edit: Upload → "crop to 9:16, add captions, and trim the intro silence" → 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 "crop to 9:16, add captions, and trim the intro silence" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 with H.264 codec for best compatibility with Instagram uploads.