Instagram Video Editor Freelance

Skip the learning curve of professional editing software. Describe what you want — trim the footage, add text overlays, and format it for Instagram Reels — a...

Security Scan

The skill's behavior largely matches an online video-editing service, but small inconsistencies (metadata vs registry, unknown source, and instructions that encourage reading install/config paths) warrant caution before installing.

Purpose & Capability

The name/description match the instructions: it uploads video to a cloud rendering API and returns edited clips. Requesting a single service token (NEMO_TOKEN) is consistent with this purpose. Minor concern: the registry summary lists no required config paths, but the skill frontmatter declares a config path (~/.config/nemovideo/) — this mismatch should be clarified.

Instruction Scope

Runtime instructions are concrete (create session, upload, SSE, poll, export) and stay within the video-editing scope. However the skill instructs the agent to detect install path and include attribution headers (probing ~/.clawhub, ~/.cursor/skills), and to read its own YAML frontmatter at runtime. Probing install/config paths could cause the agent to read filesystem locations outside the minimal needs for editing; that behavior is not justified clearly in the description.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is downloaded or written by an installer, which minimizes risk.

Credentials

Only NEMO_TOKEN is required and is appropriate for a cloud API. The frontmatter's declared config path (~/.config/nemovideo/) and the suggestion to inspect install paths expand the scope of filesystem access beyond the single env var; that expansion isn't explained and looks disproportionate.

Persistence & Privilege

The skill is not forced always-on and uses default autonomous invocation. It does not request elevated or persistent platform privileges in the metadata provided.

What to consider before installing

This skill appears to call an external video-processing API and legitimately needs a NEMO_TOKEN. Before installing or using it: 1) Verify the service domain (mega-api-prod.nemovideo.ai) and the publisher—there's no homepage or source listed. 2) Prefer creating an anonymous/ephemeral token rather than exposing long-lived secrets. 3) Be aware that files you upload (raw video) will be sent to an external service; avoid uploading sensitive content. 4) Ask the publisher to clarify why the skill needs to probe install/config paths (~/.clawhub, ~/.cursor/skills, ~/.config/nemovideo/) and fix the metadata mismatch. If you can't confirm those points, treat the skill cautiously or run it with limited privileges and ephemeral credentials.

Getting Started

Share your raw video clips and I'll get started on AI video editing. Or just tell me what you're thinking.

Try saying:

• "edit my raw video clips"
• "export 1080p MP4"
• "trim the footage, add text overlays,"

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 Freelance — Edit and Export Instagram Videos

This tool takes your raw 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 product clip shot on iPhone and want to trim the footage, add text overlays, and format it for Instagram Reels — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: vertical 9:16 format works perfectly for Reels — crop before uploading for fastest results.

Matching Input to Actions

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

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

• X-Skill-Source: instagram-video-editor-freelance
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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 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)

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

Common Workflows

Quick edit: Upload → "trim the footage, add text overlays, and format it for Instagram Reels" → Download MP4. Takes 1-2 minutes 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 "trim the footage, add text overlays, and format it 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.