Editor Ai List

v1.0.0

Turn a 2-minute raw interview clip into 1080p edited video clips just by typing what you need. Whether it's browsing and applying AI editing tools from a cur...

0· 46·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 linmillsd7/editor-ai-list.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Editor Ai List" (linmillsd7/editor-ai-list) from ClawHub.
Skill page: https://clawhub.ai/linmillsd7/editor-ai-list
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-ai-list

ClawHub CLI

Package manager switcher

npx clawhub@latest install editor-ai-list
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The name/description (cloud AI video editing) match the actions in SKILL.md (upload, SSE-driven editing, render/export via https://mega-api-prod.nemovideo.ai). Required credential (NEMO_TOKEN) is appropriate. Minor mismatch: the registry metadata provided to you earlier listed no required config paths, but the SKILL.md frontmatter claims a config path (~/.config/nemovideo/) and uses install-path detection to set X-Skill-Platform — this could require checking directories on the user's machine and is not strictly required for the editing functionality.
Instruction Scope
Instructions stay largely within the stated purpose (authenticate, create session, upload video, request renders, poll state). They instruct the agent to obtain an anonymous token if NEMO_TOKEN is absent and to include custom headers. The SKILL.md also implies detecting an install path to set X-Skill-Platform (may involve probing ~/.clawhub/ or ~/.cursor/skills/), which is beyond simple API calls and could require reading the filesystem. Otherwise there are no instructions to read unrelated files or exfiltrate arbitrary data.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by the skill itself — lowest install risk.
Credentials
The skill only requires a single credential, NEMO_TOKEN, which matches the remote API usage. The only disproportionate item is the SKILL.md frontmatter's configPaths (~/.config/nemovideo/) which wasn't listed in the registry metadata; that suggests the skill may look for local config files beyond the declared environment variable.
Persistence & Privilege
The skill does not request always:true or elevated platform-wide privileges. It asks to store transient session_id/token for API calls (normal for a remote-service integration) and is user-invocable with normal autonomous invocation permitted.
Assessment
This skill appears to do what it says: it will call the nemovideo.ai API to upload clips and request server-side edits using a single token (NEMO_TOKEN). Before installing, consider: (1) You will upload potentially sensitive video files to an external service — verify you are comfortable sharing that content with nemovideo.ai and review their privacy/terms. (2) The skill will make network requests and may auto-generate an anonymous token if none is present; the token is valid for ~7 days per the instructions. (3) There is a minor metadata inconsistency: SKILL.md references a local config path (~/.config/nemovideo/) and install-path detection (~/.clawhub/, ~/.cursor/skills/) that could require checking your home directory; if you prefer not to allow filesystem probes, ask the skill author to remove or clarify that behavior. (4) Confirm the https://mega-api-prod.nemovideo.ai domain is the intended backend and acceptable to you. If any of these are unacceptable, do not install or only use the skill with explicit, temporary tokens and non-sensitive test footage.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk972a7htabhjn7p5cpmz66vhch85kgey
46downloads
0stars
1versions
Updated 1d ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "edit a 2-minute raw interview clip into a 1080p MP4"
  • "show me a list of AI editors that can auto-cut and add transitions"
  • "browsing and applying AI editing tools from a curated list for content 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.

Editor AI List — Browse and Apply AI Editors

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

A quick example: upload a 2-minute raw interview clip, type "show me a list of AI editors that can auto-cut and add transitions", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter clips let you test multiple editors from the list faster.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is editor-ai-list, 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).

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.

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

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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 saysYou 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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "show me a list of AI editors that can auto-cut and add transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "show me a list of AI editors that can auto-cut and add transitions" → Download MP4. Takes 20-40 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...