Ai Video Editor Api

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — trim silences, add transitions, and export as a 60-second highlight reel —...

⭐ 0· 122·0 current·0 all-time

by@francemichaell-15

OpenClaw Prompt Flow

Install with OpenClaw

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

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Ai Video Editor Api" (francemichaell-15/ai-video-editor-api) from ClawHub.
Skill page: https://clawhub.ai/francemichaell-15/ai-video-editor-api
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 ai-video-editor-api

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-video-editor-api

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

ℹ

Purpose & Capability

The skill's name/description match its behavior (uploads video, starts sessions, renders on a remote GPU). One minor inconsistency: the registry metadata in the provided package lists no required config paths, but the SKILL.md frontmatter declares a config path (~/.config/nemovideo/). This is likely an authoring oversight but worth confirming.

✓

Instruction Scope

SKILL.md instructs only the network calls and session flow needed to upload footage, create sessions, stream events, and request exports. It does not ask the agent to read unrelated files or extra environment secrets. It does instruct generation/use of an anonymous token if NEMO_TOKEN is absent.

✓

Install Mechanism

Instruction-only — no install spec or code is written to disk, which keeps the installation surface small and consistent with the described cloud API usage.

ℹ

Credentials

Only NEMO_TOKEN is required (primary credential). The skill will also obtain an anonymous token from the remote API if NEMO_TOKEN is missing. That is proportionate for a third‑party cloud service, but means user media and a session token may be sent/stored on the remote provider — review their privacy and billing terms.

✓

Persistence & Privilege

always is false and the skill does not request elevated or persistent system privileges. Autonomous invocation is allowed (platform default), which is expected for an API‑driven skill.

Assessment

This skill appears to do what it says: it uploads your videos to a remote service and returns edited exports. Before installing, consider: (1) privacy — uploaded videos go to mega-api-prod.nemovideo.ai, so avoid sending sensitive footage unless you trust their policy; (2) billing/credits — anonymous tokens are time-limited and exports may be gated by credit/subscription rules; (3) token handling — the skill will read NEMO_TOKEN from the environment (or obtain an anonymous token if absent), so ensure you don’t store a long‑lived secret there unless intended; (4) confirm the minor metadata mismatch (SKILL.md lists a config path ~/.config/nemovideo/ while registry metadata did not) with the publisher if you need certainty about file‑system access. If you’re comfortable with these tradeoffs, the skill’s requirements are coherent with its purpose.

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

Runtime requirements

🎬 Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk976b28gphg59kypmszndm32ss8564dq

122downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

Getting Started

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

Try saying:

"edit a 2-minute product demo recording into a 1080p MP4"
"trim silences, add transitions, and export as a 60-second highlight reel"
"automating video editing workflows via API integration for developers and marketers"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

Generate a UUID as client identifier
POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

AI Video Editor API — Edit and Export Videos Programmatically

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

A quick example: upload a 2-minute product demo recording, type "trim silences, add transitions, and export as a 60-second highlight reel", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter input clips under 3 minutes return API responses significantly faster.

Matching Input to Actions

User prompts referencing ai video editor api, 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.

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

Header	Value
`X-Skill-Source`	`ai-video-editor-api`
`X-Skill-Version`	frontmatter `version`
`X-Skill-Platform`	auto-detect: `clawhub` / `cursor` / `unknown` from install path

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with `?bind=<id>` (get `<id>` from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate 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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim silences, add transitions, and export as a 60-second highlight reel" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

H.264 codec gives the best balance of quality and file size for API-delivered outputs.

Common Workflows

Quick edit: Upload → "trim silences, add transitions, and export as a 60-second highlight reel" → 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.

Comments

Loading comments...