Video Editing With 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 mostly behaves like a cloud video-processing front end (uploads user videos to nemovideo.ai and returns processed MP4s), but there are mismatches in the metadata and some privacy/clarity issues you should understand before installing.

Purpose & Capability

The name/description claim 'Instagram' formatted video editing and the runtime instructions consistently call a third-party rendering API (mega-api-prod.nemovideo.ai) to upload and process videos — that is coherent. However the skill name could be misleading: it does not integrate with Instagram's APIs (it only formats for Instagram), and the SKILL.md frontmatter references a config path (~/.config/nemovideo/) not declared in the registry requirements (registry shows no config paths). That metadata inconsistency is unexplained.

Instruction Scope

SKILL.md directs the agent to obtain (or use) a NEMO_TOKEN, create a session, upload user-supplied files, stream SSE edits, and poll render status. All actions are consistent with a cloud video-editing service. Important privacy-relevant behavior: user media and possibly metadata are uploaded to a third-party domain (mega-api-prod.nemovideo.ai). The instructions do not ask for unrelated environment variables or filesystem reads beyond the ambiguous install-path detection and the mentioned config path.

Install Mechanism

There is no install spec and no code files (instruction-only). That is lower risk because nothing is downloaded or written by an installer, but runtime will make network calls to the external API.

Credentials

The registry requires a single credential (NEMO_TOKEN) which matches the SKILL.md usage as the bearer token. However SKILL.md frontmatter mentions a config directory (~/.config/nemovideo/) and detection of install paths (to set X-Skill-Platform) which the registry earlier did not list — this mismatch should be clarified. Requesting only one token is proportionate, but the implied ability to read a config path (if implemented) would expand access and should be explained.

Persistence & Privilege

The skill does not request always: true and is user-invocable only. It does allow normal autonomous invocation (platform default). Nothing in the skill attempts to modify other skills or system-wide agent settings.

What to consider before installing

This skill uploads your videos to mega-api-prod.nemovideo.ai and requires a NEMO_TOKEN (it can generate a short-lived anonymous token). Before installing: 1) Confirm you trust the nemovideo.ai domain and review its privacy/terms because your media will be uploaded; 2) Verify the mismatch between registry metadata (no config paths) and SKILL.md (mentions ~/.config/nemovideo/) — ask the publisher whether the skill will read that folder; 3) Be aware the name references Instagram but it does not interact with Instagram APIs (it only formats for Instagram); 4) Test with non-sensitive sample clips first and avoid supplying videos containing private data; 5) If you need stronger assurance, ask the publisher for source/homepage and a clear privacy policy. If you want, I can draft questions to ask the publisher or check the nemovideo.ai domain for public documentation.

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 into a 1080p MP4"
• "crop to 9:16, add captions, and trim to under 60 seconds for Instagram Reels"
• "editing and formatting videos for Instagram Reels and Stories 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.

Video Editing with Instagram — Edit and Export Instagram Videos

This tool takes your video clips and runs Instagram-optimized 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 and want to crop to 9:16, add captions, and trim to under 60 seconds for Instagram Reels — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: vertical 9:16 video works best for Reels and Stories — crop landscape footage before uploading.

Matching Input to Actions

User prompts referencing video editing with 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-editing-with-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).

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

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

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.

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

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 → "crop to 9:16, add captions, and trim to under 60 seconds 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 "crop to 9:16, add captions, and trim to under 60 seconds 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's upload requirements.