Instagram Video Editor Fiverr

Get polished Instagram videos ready to post, without touching a single slider. Upload your raw video clips (MP4, MOV, AVI, WebM, up to 500MB), say something...

Security Scan

The skill's requirements and runtime instructions are consistent with a remote AI video-editing service; nothing requested is disproportionate to that purpose, though a couple of minor metadata and UX choices are worth noting before install.

Purpose & Capability

The skill is an Instagram video editor and requires a NEMO_TOKEN (service API token), which matches the described backend (nemovideo). Minor inconsistency: the registry metadata lists no required config paths, but the skill frontmatter references ~/.config/nemovideo/ — this is likely harmless (caching/session storage) but should be clarified.

Instruction Scope

SKILL.md instructs the agent to create/obtain anonymous tokens, create sessions, upload user-provided video files (multipart or URLs), poll render status, and include attribution headers. These instructions stay within the stated editing/rendering scope. Two things to notice: (1) the skill tells the agent to auto-generate and use an anonymous token if NEMO_TOKEN is not provided, and to 'don't display raw API responses or token values to the user' (this hides the created token/response details from the user); (2) uploads use local file paths (files=@/path) so the agent will need access to user-supplied files—expected but worth confirming how your platform surfaces uploads.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest installation risk. No downloads or third-party packages are requested.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportionate for calling the nemovideo API. The skill also supports automatically obtaining a temporary anonymous token (100 credits, 7 days) if none is present. Be aware the token grants the skill/backend the ability to create and manage render jobs and query credit balance; treat it like any API token.

Persistence & Privilege

Does not request persistent 'always' presence or system-level changes. It instructs storing a session_id for job management (normal for remote service sessions).

Assessment

This skill appears to be what it says: a remote AI video editor that uses a NEMO_TOKEN to call nemovideo.ai. Before installing or using it, consider: (1) privacy — uploaded videos are sent to a third-party GPU backend; do not upload sensitive or private footage you wouldn't want processed remotely; (2) token handling — you can supply your own NEMO_TOKEN or allow the skill to create an anonymous 7-day token (the skill will hide token values from the user); if you need auditability, prefer providing and managing your own token; (3) billing/credits — the anonymous token supplies limited free credits; check the service's terms and any billing implications for extended use; (4) platform file access — the skill expects to upload files via paths or URLs, so confirm how your agent/platform exposes user file uploads. If these tradeoffs are acceptable, the skill's requirements are coherent with its stated purpose.

Getting Started

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

Try saying:

• "edit a 30-second Instagram reel clip shot on a phone into a 1080p MP4"
• "trim the clip, add captions, sync music, and format it for Instagram"
• "editing and formatting short videos for Instagram posts and Reels for Instagram creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Instagram Video Editor — Edit and Export Instagram Videos

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

A quick example: upload a 30-second Instagram reel clip shot on a phone, type "trim the clip, add captions, sync music, and format it for Instagram", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

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

Matching Input to Actions

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

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.

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

Common Workflows

Quick edit: Upload → "trim the clip, add captions, sync music, and format it for Instagram" → 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 clip, add captions, sync music, and format it for Instagram" — 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.