Instagram Video Editor Free

Turn a 30-second vertical phone recording into 1080p Instagram-ready clips just by typing what you need. Whether it's editing and formatting videos for Insta...

Security Scan

The skill broadly matches its claimed purpose (cloud video editing) but contains inconsistencies about local config/paths and instructs the agent to send user videos and tokens to an external API with no homepage or provenance — proceed only after verifying the backend and token usage.

Purpose & Capability

Name/description match the instructions: the skill calls a cloud video-rendering API, uploads clips, and returns download URLs. Requesting a single API token (NEMO_TOKEN) is proportionate. However, the SKILL.md frontmatter declares a required config path (~/.config/nemovideo/) while the published registry metadata lists no config paths — this mismatch is unexplained and worth confirming with the author.

Instruction Scope

Runtime instructions direct the agent to obtain or use a NEMO_TOKEN, call multiple endpoints on https://mega-api-prod.nemovideo.ai, upload user video files (multipart or URL), and poll for render status. The doc also instructs the agent to detect install-paths (e.g., ~/.clawhub/ or ~/.cursor/skills/) to populate X-Skill-Platform and to derive headers from the YAML frontmatter. Detecting install paths / reading local config and constructing platform attribution headers requires filesystem/context inspection beyond simple API use and was not declared in the registry metadata — this increases privacy surface (local path discovery and potential config reading).

Install Mechanism

Instruction-only skill with no install spec and no code files, so nothing is written to disk by the skill package itself. This is the lowest install risk.

Credentials

Only NEMO_TOKEN is declared as required, which is reasonable for a cloud-rendering service. But SKILL.md instructs generating an anonymous token (POST to /api/auth/anonymous-token) and treating the returned token as NEMO_TOKEN (implying storage). The frontmatter's implicit claim that ~/.config/nemovideo/ is required (not present in registry) suggests possible local credential/config access that isn't justified by the description — ask why a local config path is needed.

Persistence & Privilege

Skill is not always-enabled and does not request elevated platform privileges. It does expect to save session_id and use short-lived render sessions, which is normal behavior for a remote-rendering skill.

What to consider before installing

This skill appears to do what it says — send videos to a cloud API for AI editing — but you should verify a few things before installing or using it with real data: 1) Confirm the backend domain (mega-api-prod.nemovideo.ai) and the skill author/source; there is no homepage or publisher information. 2) Understand that uploaded videos and generated tokens will be sent to that external service — do not upload sensitive or private videos until you trust the vendor. 3) Ask the author why the SKILL.md frontmatter requires ~/.config/nemovideo/ (the registry lists no config paths) and whether the agent will read any local files or credentials. 4) For testing, use a throwaway/anonymous token rather than any long-lived account credential. 5) If you need stronger assurance, request a canonical homepage, privacy/terms, or signed release (or run a network review to verify endpoints and TLS). If the author cannot explain the config-path discrepancy or provenance of the API, treat this as untrusted.

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 text overlays, and format it for Instagram Reels"
• "editing and formatting videos for Instagram posts and Reels for Instagram creators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Instagram Video Editor 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 text overlays, and format it for Instagram Reels, 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.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is instagram-video-editor-free, 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).

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.

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.

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.

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

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the clip, add text overlays, and format it for Instagram Reels" — 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 compatibility.

Common Workflows

Quick edit: Upload → "trim the clip, add text overlays, and format it for Instagram Reels" → 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.