Instagram Video Editor App

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's requests and runtime instructions are consistent with a cloud video-editing frontend that uses a single service token; nothing in the package indicates it is doing unrelated or hidden actions.

Purpose & Capability

Name and description match the runtime instructions: the SKILL.md describes uploading video, creating a session, sending SSE edit commands, and exporting rendered files from a nemo video API. The only minor mismatch is that the registry metadata listed no config paths while the SKILL.md frontmatter declares ~/.config/nemovideo/ (likely harmless metadata inconsistency).

Instruction Scope

Instructions are focused on creating sessions, uploading video, streaming SSE edits, polling render status, and returning download URLs — all consistent with an editing service. They instruct using NEMO_TOKEN or obtaining an anonymous token from the documented API. A small scope oddity: the skill asks the agent to auto-detect an install path to set X-Skill-Platform, which could cause the agent to read its install location or path metadata; otherwise there are no instructions to read unrelated files or secrets.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk or downloaded during installation. This is the lowest-risk install model.

Credentials

Only one credential is requested (NEMO_TOKEN), which is appropriate for a service API. The SKILL.md frontmatter also references a config path (~/.config/nemovideo/) that the registry metadata did not declare — a minor inconsistency. The skill's network calls use a single third-party domain (mega-api-prod.nemovideo.ai), which is expected but means uploaded videos and session data go to that external service.

Persistence & Privilege

always is false and the skill does not request system-wide changes or modify other skills. Autonomous invocation is enabled (platform default) but not combined with other elevation concerns.

Assessment

This skill appears coherent for a cloud-based video editor that needs one API token. Before installing: confirm you trust the domain mega-api-prod.nemovideo.ai and where NEMO_TOKEN comes from; understand that videos you upload will be sent to that external service; if you don’t want to provide a long-lived token, use the anonymous-token flow described (it issues a short starter token). Note the minor metadata mismatch (SKILL.md lists a config path ~/.config/nemovideo/ while the registry metadata did not) and that the skill asks the agent to identify its platform/install path for a header — if you’re uncomfortable exposing agent install or path metadata, ask for clarification or disallow that header. If you need stronger assurance, request the publisher/homepage or an official privacy/security policy for Nemovideo before using.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI video editing.

Try saying:

• "edit a 30-second vertical phone recording into a 1080p MP4"
• "trim the clip, add captions, and resize to 1080x1080 for Instagram feed"
• "editing and formatting videos for Instagram posts, 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.

Instagram Video Editor App — 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 vertical phone recording and want to trim the clip, add captions, and resize to 1080x1080 for Instagram feed — 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, 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
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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 JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the clip, add captions, and resize to 1080x1080 for Instagram feed" — 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.

Common Workflows

Quick edit: Upload → "trim the clip, add captions, and resize to 1080x1080 for Instagram feed" → 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.