Editor Instagram

v1.0.0

Get Instagram-ready clips ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "cu...

0· 71·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for francemichaell-15/editor-instagram.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Editor Instagram" (francemichaell-15/editor-instagram) from ClawHub.
Skill page: https://clawhub.ai/francemichaell-15/editor-instagram
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install editor-instagram

ClawHub CLI

Package manager switcher

npx clawhub@latest install editor-instagram
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Instagram video editing) align with the runtime endpoints, upload/export/render flow, and the single required credential (NEMO_TOKEN). No unrelated services, binaries, or excessive permissions are requested.
Instruction Scope
SKILL.md confines actions to the remote nemovideo API (session creation, SSE, uploads, render polling). It instructs generating an anonymous token if NEMO_TOKEN is missing and saving session_id. Minor inconsistency: the frontmatter metadata lists a config path (~/.config/nemovideo/) and the headers require auto-detecting an install path for X-Skill-Platform — those imply reading agent/install metadata or config files, which is plausible for attribution but not strictly necessary for editing functionality and should be documented/justified.
Install Mechanism
No install spec or code files (instruction-only), so nothing is downloaded or written to disk during install.
Credentials
Only one credential is required (NEMO_TOKEN), which directly maps to the service's Bearer auth. The skill also supports creating a short-lived anonymous token if none is provided. No other secrets or unrelated env vars are requested.
Persistence & Privilege
always:false and normal autonomous invocation. The skill will save session_id and may persist the obtained anonymous token for subsequent calls — this is reasonable for a session-based remote service but the user should confirm how/where tokens are stored by the agent.
Assessment
This skill appears coherent for remote Instagram-style video editing. Before installing, consider: (1) the service receives full video uploads — avoid sending sensitive footage; (2) NEMO_TOKEN (or an anonymous token the skill will create) grants access to your account/credits — treat it like a password and confirm where the agent will persist it; (3) the SKILL.md mentions reading/install-path metadata for attribution headers and lists a config path in frontmatter — ask the developer why that config path is needed and what the agent reads from it; (4) verify the service's privacy/retention and billing policy (exports may be blocked on free tiers). If those points are acceptable, the skill itself is internally consistent with its stated purpose.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

📱 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk972ca367zp15hkm1a6xq6r5j5852nsk
71downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "edit a 60-second vertical phone recording into a 1080p MP4"
  • "cut this into a 30-second Instagram Reel with transitions and music sync"
  • "editing videos optimized for Instagram Reels and feed posts 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.

Instagram Video Editor — Edit and Export Instagram Videos

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

A quick example: upload a 60-second vertical phone recording, type "cut this into a 30-second Instagram Reel with transitions and music sync", and you'll get a 1080p MP4 back in roughly 30-60 seconds. 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 editor instagram, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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

EndpointMethodPurpose
/api/tasks/me/with-session/nemo_agentPOSTStart a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_ssePOSTSend 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>POSTUpload a file (multipart) or URL.
/api/credits/balance/simpleGETCheck remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latestGETFetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambdaPOSTStart 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.

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

HeaderValue
X-Skill-Sourceeditor-instagram
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Error Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut this into a 30-second Instagram Reel with transitions and music sync" — 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 → "cut this into a 30-second Instagram Reel with transitions and music sync" → 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.

Comments

Loading comments...