Editor Ai Instagram

Instagram creators edit video clips into Instagram-ready clips using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, renders on cloud GPUs at 1080p, and...

Security Scan

The skill largely matches a cloud-video-editing purpose (needs a single API token and makes API calls), but there are mismatches and vague instructions (undocumented headers, an unexpected config path, and filesystem-detection behavior) that are unexplained and warrant caution before installing.

Purpose & Capability

Name/description (cloud GPU video editing) aligns with needing an API token (NEMO_TOKEN) and making upload/render API calls. However the SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) and uses install-path detection to set an attribution header — these filesystem accesses are not declared in the registry metadata and are not strictly necessary to provide basic editing capability.

Instruction Scope

Instructions tell the agent to create sessions, upload files, run SSE, and poll render status — all consistent with the stated purpose. Concerns: (1) If NEMO_TOKEN is absent the skill instructs the agent to generate an anonymous token via POST to an external endpoint (fine functionally but requires network access). (2) It requires deriving three attribution headers from YAML frontmatter and detecting install paths (e.g., ~/.clawhub/, ~/.cursor/) — this implies reading the filesystem to detect install location or config files, which is scope creep relative to simple upload/render. (3) The names/values of the 'three attribution headers' are ambiguous in the doc, which could lead to incorrect or surprising behavior.

Install Mechanism

This is instruction-only with no install spec and no code files, so nothing will be written to disk by an installer. That lowers risk compared to remote-download installs.

Credentials

Only one required env var (NEMO_TOKEN) is declared, which is proportionate for an API-backed editing service. However the frontmatter also lists a config path (~/.config/nemovideo/) that was not declared elsewhere — reading that directory could expose other local config or credentials. The skill also instructs deriving headers based on install paths, which could cause additional filesystem reads.

Persistence & Privilege

always:false and no install hooks are declared. The skill does not request elevated or permanent presence in the agent beyond normal autonomous invocation (default), and it does not claim to modify other skills or global agent settings.

What to consider before installing

This skill appears to implement a cloud video-editing service and legitimately needs an API token and network access. Before installing: (1) Verify the backend domain (mega-api-prod.nemovideo.ai) and the service's privacy/retention policy — the skill will upload your videos to that service. (2) Prefer using an anonymous/starter token (as described) rather than placing a long-lived credential in your environment. (3) Ask the author to clarify the 'three attribution headers' and why install-path detection or ~/.config/nemovideo/ access is needed; these require the agent to read local filesystem paths and may expose unexpected data. (4) If you have sensitive data in home config dirs, avoid granting the skill filesystem access or do not install it until provenance/homepage is confirmed. The lack of a homepage and the registry-frontmatter mismatch are reasons to be cautious.

Getting Started

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

Try saying:

• "edit a 60-second vertical phone recording into a 1080p MP4"
• "cut this into a 30-second Instagram Reel with transitions and captions"
• "editing videos for Instagram Reels and Stories for Instagram creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

AI Editor for Instagram — Edit and Export Instagram Videos

Send me your video clips and describe the result you want. The AI Instagram editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 60-second vertical phone recording, type "cut this into a 30-second Instagram Reel with transitions and captions", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: vertical 9:16 video works best for Reels and Stories output.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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

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

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 → "cut this into a 30-second Instagram Reel with transitions and 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut this into a 30-second Instagram Reel with transitions and 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 direct Instagram upload compatibility.