Movie Maker

v1.0.0

create video clips into finished movie files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for assembling raw cl...

0· 34·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 mhogan2013-9/movie-maker.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Movie Maker" (mhogan2013-9/movie-maker) from ClawHub.
Skill page: https://clawhub.ai/mhogan2013-9/movie-maker
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 movie-maker

ClawHub CLI

Package manager switcher

npx clawhub@latest install movie-maker
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (cloud GPU rendering of uploaded clips) match the runtime instructions which call a remote API to create sessions, upload files, and request renders. The single declared credential (NEMO_TOKEN) is appropriate for a remote service.
Instruction Scope
The SKILL.md explicitly instructs the agent to POST files and metadata to an external domain (mega-api-prod.nemovideo.ai), create anonymous tokens if no NEMO_TOKEN is present, and include attribution headers. This is consistent with a cloud render pipeline but does mean user media will be transmitted off-device. The instructions also reference deriving X-Skill-Platform from install paths and a config path (~/.config/nemovideo/) in the YAML frontmatter — minor scope expansion that may require reading the agent's install path or config files.
Install Mechanism
No install spec or code is provided (instruction-only), so nothing is written to disk by the skill itself. This is the lowest-risk install profile.
Credentials
Only NEMO_TOKEN is declared as required, which fits a third-party API. However, the instructions also describe generating an anonymous NEMO_TOKEN if none is present; the combination (declared primary credential but automatic anonymous issuance) is slightly inconsistent but explainable (use a provided account token when available, otherwise use a temporary anonymous token). No unrelated secrets are requested.
Persistence & Privilege
The skill is not always-enabled and uses normal autonomous invocation defaults. It does not request system-wide privileges or to modify other skills' configs. The skill will maintain session_id/tokens for its own operations (expected for a service client).
Assessment
This skill sends any uploaded video/audio to a third-party cloud service (mega-api-prod.nemovideo.ai) for rendering. That is expected behavior for a cloud render tool, but before installing: (1) verify you trust the service and its domain (there is no homepage listed), (2) do not upload sensitive or confidential footage unless you confirm the provider's privacy/TOS and encryption/retention policies, (3) consider supplying your own NEMO_TOKEN if you want operations tied to your account (the skill will otherwise obtain an anonymous token valid for 7 days), (4) note the minor metadata inconsistency: the SKILL.md frontmatter references a config path (~/.config/nemovideo/) and also reads install paths to set X-Skill-Platform — review what local paths the agent will access, and (5) if you need higher assurance, ask the author for a homepage, privacy policy, or source code before use.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk974qv2qpnnnyka9g2z3v5nwms85na4f
34downloads
0stars
1versions
Updated 13h ago
v1.0.0
MIT-0

Getting Started

Share your video clips and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

  • "create my video clips"
  • "export 1080p MP4"
  • "combine my clips, add background music,"

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.

Movie Maker — Create and Export Finished Videos

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

A quick example: upload three 30-second raw phone clips, type "combine my clips, add background music, and export as a finished short film", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: keeping individual clips under 2 minutes speeds up the final render noticeably.

Matching Input to Actions

User prompts referencing movie maker, 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.

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

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

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.

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

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

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.

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 → "combine my clips, add background music, and export as a finished short film" → 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 "combine my clips, add background music, and export as a finished short film" — 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...