Editor Ai Hd

v1.0.0

YouTubers and content creators edit raw video footage into HD edited videos using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, renders on cloud GPUs...

0· 100·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 susan4731-wilfordf/editor-ai-hd.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install editor-ai-hd
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill claims cloud GPU video editing and the SKILL.md instructs uploading videos and calling render endpoints using a single NEMO_TOKEN — this is coherent. Note: the YAML frontmatter lists a config path (~/.config/nemovideo/) that the registry metadata did not list; that discrepancy should be clarified.
Instruction Scope
Instructions stay within video-editing scope (session creation, SSE for edits, multipart upload, render polling). They do require the agent to read/detect an install path to derive X-Skill-Platform and to save a session_id; both are plausible but extend beyond purely 'upload this one file' behavior and may require filesystem access or local storage of session state.
Install Mechanism
No install spec or code files are present (instruction-only), so nothing will be written to disk by an installer. This is the lowest-risk install mechanism.
Credentials
Only one credential (NEMO_TOKEN) is required, which matches a cloud API. However the frontmatter mentions a config path (~/.config/nemovideo/) which would give the skill access to local configuration — that wasn't listed in the registry metadata and may be unnecessary. The skill also suggests generating and storing an anonymous token (100 credits, 7-day expiry); clarify whether tokens are stored persistently or only in-memory.
Persistence & Privilege
always:false (no forced global enable). The skill will store session_id and may write session state locally per instructions, which is reasonable for multi-step cloud jobs. Autonomous invocation is allowed (default) but not excessive by itself.
Assessment
This skill appears to do what it says: upload videos and call a cloud render API using a NEMO_TOKEN. Before installing, confirm: (1) the external domain (mega-api-prod.nemovideo.ai) is a service you trust to handle your media; (2) whether the skill will persist the anonymous token and session_id on disk (the frontmatter references ~/.config/nemovideo/); and (3) whether the agent will access other files when detecting install paths. If you need stronger privacy controls, avoid using anonymous token generation or uploading sensitive footage until you verify the service's terms and storage retention policies.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk9739sej597ea705m5a2r8p7x984kqpr
100downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "edit my raw video footage"
  • "export 1080p MP4"
  • "cut the slow parts, add transitions,"

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.

Editor AI HD — Edit and Export HD Videos

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI HD editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute 1080p camera recording, ask for cut the slow parts, add transitions, and export in HD quality, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 3 minutes process significantly faster and yield cleaner AI cuts.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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 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 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

Common Workflows

Quick edit: Upload → "cut the slow parts, add transitions, and export in HD quality" → 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 "cut the slow parts, add transitions, and export in HD quality" — 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 the best balance of HD quality and file size.

Comments

Loading comments...