Instagram Video Editor App Download

Turn a 30-second phone-recorded clip for an Instagram post into 1080p Instagram-ready clips just by typing what you need. Whether it's editing and formatting...

Security Scan

The skill's network calls and single required credential (NEMO_TOKEN) match its stated video-editing purpose, but there are inconsistencies in declared config-path requirements and some vague instructions about where tokens/session IDs are stored that merit caution.

Purpose & Capability

The skill is a cloud-based video editor and legitimately needs a service token and endpoints for uploading, SSE, and rendering; however the frontmatter in SKILL.md lists a config path (~/.config/nemovideo/) while the registry metadata shows no required config paths — this mismatch is unexplained and may indicate the skill expects to read or write files it didn't declare.

Instruction Scope

Runtime instructions are narrowly scoped to creating sessions, uploading video files, streaming edits via SSE, polling render status, and returning download URLs — all consistent with an edit/export workflow. Minor scope questions: it asks to 'save session_id' but doesn't specify where (implies persistent storage), and it requires auto-detecting an install path to populate an attribution header, which could require reading environment/paths outside the immediate task.

Install Mechanism

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

Credentials

Only NEMO_TOKEN is declared (appropriate for a cloud API), but the SKILL.md frontmatter also references a config directory (~/.config/nemovideo/) which was not declared in the registry. That suggests the skill may read/write files in the user's home directory or expect to persist credentials/session state there — this access was not explicitly listed and is disproportionate unless justified.

Persistence & Privilege

The skill is not forced-always, and autonomous invocation is allowed (the platform default). Autonomy plus network access is expected for this type of skill but increases blast radius; combined with the unexplained config-path behavior, this is worth confirming.

What to consider before installing

This skill broadly appears to do what it describes (upload your clips to a cloud service, run edits, return a download). Before installing: 1) Confirm where session tokens and the anonymous NEMO_TOKEN will be stored (the SKILL.md implies saving session_id and references ~/.config/nemovideo/, but the registry didn't declare that). 2) Be comfortable that uploading your videos to mega-api-prod.nemovideo.ai is acceptable (check privacy/TOS and avoid uploading sensitive footage). 3) If you prefer not to expose persistent credentials, avoid setting a long-lived NEMO_TOKEN in your environment and prefer anonymous tokens with limited scope. 4) Ask the publisher to clarify the config-path usage and whether the skill will read/write files under your home directory. If those answers are satisfactory, the skill's network actions are consistent with its stated purpose.

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"
• "trim the clip, add text overlays,"

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 App Download — Edit and Export Instagram Videos

This tool takes your video clips and runs AI video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 30-second phone-recorded clip for an Instagram post and want to trim the clip, add text overlays, and export in vertical 9:16 format for Instagram Reels — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: vertical 9:16 video works perfectly for Reels and Stories without any cropping needed.

Matching Input to Actions

User prompts referencing instagram video editor app download, 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-app-download
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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.

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.

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

Common Workflows

Quick edit: Upload → "trim the clip, add text overlays, and export in vertical 9:16 format 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.

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 export in vertical 9:16 format 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 compatibility with Instagram uploads.