Instagram Video Editor Desktop

Skip the learning curve of professional editing software. Describe what you want — crop to square format, add trending music, and overlay captions — and get...

Security Scan

The skill is internally consistent with a cloud-based Instagram video editor (it just routes uploads and editing jobs to nemovideo.ai using a single NEMO_TOKEN), but there are minor metadata inconsistencies and no public source/homepage, so verify the external service before sending sensitive files.

Purpose & Capability

The instructions and required NEMO_TOKEN match the declared purpose (cloud video editing). However the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata indicated no required config paths — a minor inconsistency in declared requirements. Overall the requested credential (NEMO_TOKEN) is proportionate to the described cloud API usage.

Instruction Scope

SKILL.md gives concrete runtime steps (obtain anonymous token, create session, upload, render, poll for job status). These steps are within scope for a cloud video editor. It does instruct the agent to read the skill's YAML frontmatter and to 'detect from install path' (e.g., ~/.clawhub/ or ~/.cursor/skills/) which implies inspecting the agent's environment/filesystem; that is plausible for attribution but worth noting.

Install Mechanism

This is an instruction-only skill with no install spec or code to write to disk, so there is no install-related risk from downloads or executing third-party packages.

Credentials

The skill only declares a single credential (NEMO_TOKEN) as primaryEnv, which is appropriate for a cloud API-backed editor. There are no unrelated credentials requested.

Persistence & Privilege

The skill directs the agent to 'save session_id' and reuse tokens for subsequent requests; persisting session state or tokens is reasonable for session continuity but be aware tokens are bearer credentials and should be stored securely. always:false and normal model invocation are set.

Assessment

This skill sends your uploaded videos and metadata to https://mega-api-prod.nemovideo.ai and expects a NEMO_TOKEN (which can be generated anonymously). Before installing: 1) Confirm you trust nemovideo.ai (no homepage/source listed here). 2) Understand any videos you upload will go to their servers — avoid sending sensitive or private content. 3) Anonymous tokens expire in 7 days and carry credits; treat them like bearer credentials and don't paste them into public logs. 4) The skill will persist session_id/token state for convenience — ensure your agent stores these securely or use a throwaway account/token for testing. 5) If you need higher assurance, ask the publisher for source code, privacy policy, and a canonical homepage before use.

Getting Started

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

Try saying:

• "edit a 60-second phone-recorded clip for Instagram into a 1080p MP4"
• "crop to square format, add trending music, and overlay captions"
• "editing and formatting videos for Instagram posts and Reels on desktop 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 Desktop — 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 60-second phone-recorded clip for Instagram and want to crop to square format, add trending music, and overlay captions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: square (1:1) and vertical (9:16) aspect ratios both work — pick based on feed vs Reels.

Matching Input to Actions

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

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

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

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "crop to square format, add trending music, and overlay captions" — 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 → "crop to square format, add trending music, and overlay captions" → 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.