Video Editor Ai Hd

v1.0.0

Get HD edited videos ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something like "t...

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 tk8544-b/video-editor-ai-hd.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-editor-ai-hd
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match requested resources: the skill accesses a NEMO_TOKEN and a nemovideo config path which are appropriate for a cloud video-processing integration. No unrelated credentials or binaries are requested.
Instruction Scope
SKILL.md instructs the agent to create/use a NEMO_TOKEN, open a session, upload files, stream SSE edits, poll render status, and return download URLs — all consistent with a remote video-rendering service. It does not ask the agent to read unrelated system files or exfiltrate data to other endpoints.
Install Mechanism
Instruction-only skill with no install spec and no code files — minimal disk/write risk. The runtime only describes HTTP API interactions with mega-api-prod.nemovideo.ai.
Credentials
Only NEMO_TOKEN (primary credential) and an optional nemovideo config path are declared. That is proportionate for a cloud editing service that authenticates requests. No broad or unrelated secrets are requested.
Persistence & Privilege
Skill is not always-enabled and does not request special platform privileges. It asks the agent to store a session_id for job tracking, which is normal for an upload/render workflow.
Assessment
This skill appears coherent for a cloud-based video editor, but consider these points before installing: - It uploads your raw video files to mega-api-prod.nemovideo.ai for processing — do not use it for sensitive or confidential footage unless you trust the service and its privacy policy. - The skill needs a NEMO_TOKEN to authenticate API calls. Prefer a scoped or disposable token and do not share your global credentials. The skill can also obtain an anonymous token (100 credits, 7-day expiry) if no token is set. - Because files are sent to an external server, check copyright and privacy implications (people in video, proprietary content, etc.). - The package is instruction-only (no install or binaries), so installation risk is low, but the agent will perform network operations on your behalf — monitor network activity if you’re concerned. - If you want extra safety, create a dedicated account/token for this service, limit token lifetime/permissions if possible, and review the service domain (nemovideo.ai) and its terms before use.

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

Runtime requirements

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

Getting Started

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

Try saying:

  • "edit a 2-minute 1080p phone recording into a 1080p MP4"
  • "trim the shaky parts, enhance the resolution to HD, and add smooth transitions"
  • "editing and upscaling videos to HD quality using AI for YouTubers and content 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.

Video Editor AI HD — Edit and Export HD Videos

This tool takes your raw video footage and runs AI HD editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute 1080p phone recording and want to trim the shaky parts, enhance the resolution to HD, and add smooth transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster and yield sharper AI upscaling results.

Matching Input to Actions

User prompts referencing video 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

  1. SessionPOST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
  2. Chat (SSE)POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
  3. UploadPOST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
  4. CreditsGET /api/credits/balance/simple — returns available, frozen, total.
  5. StateGET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
  6. ExportPOST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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

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.

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 → "trim the shaky parts, enhance the resolution to HD, and add smooth transitions" → 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 shaky parts, enhance the resolution to HD, and add smooth transitions" — 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...