Instagram Video Editor Ai Free

edit video clips into Instagram-ready clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. Instagram creators use it for editing vertical...

Security Scan

The skill's requirements and runtime instructions are largely coherent with an AI video-rendering frontend that talks to a cloud backend, but there are small metadata inconsistencies and privacy considerations you should review before use.

Purpose & Capability

The skill claims to perform cloud video editing and only requests a single service token (NEMO_TOKEN) and API calls to a video-render backend (mega-api-prod.nemovideo.ai), which is proportionate to its stated purpose.

Instruction Scope

Runtime instructions stay within the editing/export domain: create/keep a session, upload files, use SSE for edits, poll render status, and return download URLs. They explicitly upload user video files to the remote backend, so the agent will transmit user media off-device — expected for a cloud editor but important to note. The SKILL.md also instructs auto-provisioning of an anonymous token if no NEMO_TOKEN is present, which is reasonable but broadens where credentials may originate.

Install Mechanism

Instruction-only skill with no install spec or code files; nothing will be written to disk by an installer. This is the lowest-risk install pattern.

Credentials

Only one credential is required (NEMO_TOKEN), which matches the backend calls in the instructions. However, the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata summary provided earlier said no required config paths — this mismatch is an inconsistency to clarify. The skill will also generate or fetch an anonymous token if NEMO_TOKEN is not provided, which is expected but means the agent may call the auth endpoint to obtain credentials automatically.

Persistence & Privilege

always is false and the skill does not request persistent agent-wide privileges. It instructs maintaining a session_id in memory for operations, which is normal for a session-based service.

Assessment

This skill is coherent with a cloud-based video editor, but before installing consider: (1) Uploaded videos will be sent to mega-api-prod.nemovideo.ai — do not upload sensitive or private footage unless you trust the service and its privacy terms. (2) You can provide your own NEMO_TOKEN or the skill can obtain an anonymous token automatically; providing your own token gives you more control. (3) There is a metadata mismatch: SKILL.md mentions ~/.config/nemovideo/ while the registry metadata did not list required config paths — ask the publisher which is correct. (4) The skill's source and homepage are unknown; verify the backend domain and operator reputation if possible. If you need stronger guarantees about data handling or provenance, prefer a skill with a documented homepage and known publisher before use.

Getting Started

Send me your video clips and I'll handle the AI video editing. Or just describe what you're after.

Try saying:

• "edit a 30-second vertical phone recording into a 1080p MP4"
• "trim the clip, add captions, and fit it to Instagram's 9:16 format"
• "editing vertical videos for Instagram Reels and Stories for Instagram creators"

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 AI Free — 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 recording, ask for trim the clip, add captions, and fit it to Instagram's 9:16 format, 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 Stories without cropping.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	instagram-video-editor-ai-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

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 clip, add captions, and fit it to Instagram's 9:16 format" — 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 Instagram upload compatibility.

Common Workflows

Quick edit: Upload → "trim the clip, add captions, and fit it to Instagram's 9:16 format" → 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.