Video Editor Generator

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — trim the pauses, add transitions, and generate a title card — and get edit...

⭐ 0· 83·0 current·0 all-time

by@mhogan2013-9

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mhogan2013-9/video-editor-generator.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Video Editor Generator" (mhogan2013-9/video-editor-generator) from ClawHub.
Skill page: https://clawhub.ai/mhogan2013-9/video-editor-generator
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-generator

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-editor-generator

Security Scan

VirusTotal

Pending

View report →

OpenClaw

Suspicious

medium confidence

ℹ

Purpose & Capability

The skill's stated purpose (remote AI video editing) matches the runtime instructions (upload video, create session, request render). However the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata above reported no required config paths — this mismatch in declared requirements is an inconsistency to verify. The external API domain (mega-api-prod.nemovideo.ai) has no homepage or owner info in the registry metadata, which reduces provenance.

✓

Instruction Scope

Runtime instructions are scoped to creating an anonymous or provided token, establishing a session, uploading user media, and polling for renders. The instructions do not direct the agent to read unrelated local files or arbitrary environment variables. They do require including specific attribution headers and handling SSE streams; these are coherent with a remote-rendering workflow.

✓

Install Mechanism

No install spec and no code files are present (instruction-only skill), so there is no installer writing code to disk. That lowers risk. All execution happens via network calls described in SKILL.md.

ℹ

Credentials

Only a single env var (NEMO_TOKEN) is required and is proportional to a hosted API. The SKILL.md also describes obtaining an anonymous token itself (POST to /api/auth/anonymous-token). The frontmatter's optional config path suggests local storage of session/token, but the registry did not declare that path — confirm whether the skill will create or read local config.

✓

Persistence & Privilege

always is false and the skill does not request elevated platform privileges. It will persist session tokens and job IDs as part of normal operation, which is expected for a remote-rendering service.

What to consider before installing

This skill is an instruction-only connector to a remote video-rendering API. Before installing: 1) Verify the service/domain (mega-api-prod.nemovideo.ai) and request a homepage/privacy policy from the author — the registry shows no source/homepage. 2) Expect that your video files (up to 500MB) will be uploaded to the remote endpoint; do not upload sensitive or private content until you trust the service. 3) The skill can mint anonymous short-lived tokens for you; consider using throwaway accounts or limiting scope if concerned. 4) Confirm whether the skill will create files under ~/.config/nemovideo/ (frontmatter mentions it) so you can audit any local token storage. 5) If you proceed, monitor network activity and avoid placing long‑lived credentials in NEMO_TOKEN unless you trust the provider. If you want higher assurance, ask the publisher for a homepage, documentation, or a public code repository before use.

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

Runtime requirements

🎬 Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk9717bn9d3w0jybcn0cka7wees858qe9

83downloads

0stars

1versions

Updated 6d 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 video editing.

Try saying:

"edit a 2-minute unedited screen recording into a 1080p MP4"
"trim the pauses, add transitions, and generate a title card"
"automatically editing raw footage into a finished video for 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 Generator — Edit and Export Finished Videos

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

A quick example: upload a 2-minute unedited screen recording, type "trim the pauses, add transitions, and generate a title card", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing video editor generator, 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`	`video-editor-generator`
`X-Skill-Version`	frontmatter `version`
`X-Skill-Platform`	auto-detect: `clawhub` / `cursor` / `unknown` from install path

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

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)

Common Workflows

Quick edit: Upload → "trim the pauses, add transitions, and generate a title card" → 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 pauses, add transitions, and generate a title card" — 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 across platforms and devices.

Comments

Loading comments...