Video Editor Instagram Ai

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 and refo...

Security Scan

The skill largely matches its stated purpose (cloud video editing) but contains a few inconsistencies and data-access expectations you should understand before installing.

Purpose & Capability

Name/description match the instructions: the skill talks to a remote video-processing backend (nemovideo.ai) and uploads video files for editing. Requesting a NEMO_TOKEN as the primary credential is consistent with a cloud API integration. However, the SKILL.md also documents an anonymous-token flow that obtains a NEMO_TOKEN automatically if none is present — this conflicts with the registry metadata that declares NEMO_TOKEN required (primaryEnv). Also the frontmatter metadata mentions a config path (~/.config/nemovideo/) that the registry listing did not mark as a required config path.

Instruction Scope

Runtime instructions tell the agent to: look for NEMO_TOKEN, if absent POST to https://mega-api-prod.nemovideo.ai to create an anonymous token, create sessions, upload user files (multipart or by URL), stream SSE requests, poll render endpoints, and return download URLs. These are coherent for a cloud editor, but the skill also requires adding attribution headers that include an auto-detected X-Skill-Platform value derived from the install path — that implies the agent may need to read install/agent path info (filesystem or environment). The SKILL.md references a config directory in its metadata; it's not explicit whether the agent must read that path, but the combination suggests potential filesystem reads beyond just handling user-uploaded video files. The instructions also instruct not to expose tokens, but they do create and store tokens/session IDs which are sensitive.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. All network calls happen at runtime to the documented nemovideo.ai endpoints; nothing is downloaded or written by an installer step.

Credentials

Only one credential (NEMO_TOKEN) is declared as required, which is proportionate for a cloud video API. But the SKILL.md documents an anonymous-token acquisition flow (POST to /api/auth/anonymous-token) so a preexisting token may not actually be necessary. The frontmatter's configPaths (~/.config/nemovideo/) suggests potential access to a user config directory that is not otherwise explained — this should be clarified. No other unrelated secrets are requested.

Persistence & Privilege

always:false and the skill is user-invocable; it does not request permanent platform-wide privileges. The skill will create and use session tokens at runtime, but there is no install-time persistence or modification of other skills/configs described.

Scan Findings in Context

[NO_CODE_FILES] expected: The skill is instruction-only and the regex scanner had no code files to analyze. This is expected for a pure-instructions skill, but it means the security surface is the SKILL.md text (network calls, token handling, file uploads).

What to consider before installing

This skill appears to do what it says — upload your video and call a cloud API for editing — but review a few things before installing: 1) Confirm you trust the endpoint host (mega-api-prod.nemovideo.ai) and its privacy/billing policies because user videos will be uploaded to that third party. 2) Clarify the NEMO_TOKEN requirement: the skill claims NEMO_TOKEN is required but also documents an anonymous-token flow that will mint a token for you; ask the author which behavior applies and whether the created token is stored or logged. 3) Ask why the frontmatter mentions ~/.config/nemovideo/ and whether the skill will read files from your home directory or agent install path (used to set X-Skill-Platform). If you are uncomfortable with filesystem access, request the author to remove or document that requirement. 4) The skill will make outbound network calls and upload files; do not provide sensitive or private video content until you verify the service terms. If you need higher assurance, request source code or a trustworthy homepage and a clear privacy/retention policy from the publisher.

Getting Started

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

Try saying:

• "edit a 60-second vertical phone recording into a 1080p MP4"
• "reformat to 9:16, add trending captions, and trim pauses for Instagram Reels"
• "editing and reformatting videos for Instagram Reels 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.

Video Editor Instagram AI — Edit Videos for Instagram Reels

Drop your video clips in the chat and tell me what you need. I'll handle the AI Instagram editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 60-second vertical phone recording, ask for reformat to 9:16, add trending captions, and trim pauses 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 best for Reels and Stories output.

Matching Input to Actions

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

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

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

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "reformat to 9:16, add trending captions, and trim pauses 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 upload compatibility.

Common Workflows

Quick edit: Upload → "reformat to 9:16, add trending captions, and trim pauses 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.