Designer Video

v1.0.0

create raw video clips into polished designer videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. marketers and content creators use it...

0· 59·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/designer-video.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Designer Video" (linmillsd7/designer-video) from ClawHub.
Skill page: https://clawhub.ai/linmillsd7/designer-video
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 designer-video

ClawHub CLI

Package manager switcher

npx clawhub@latest install designer-video
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill's name/description (turn raw clips into branded videos) aligns with the network calls and flows in SKILL.md. Requesting a single service token (NEMO_TOKEN) and describing upload/render/export endpoints is appropriate. Minor inconsistency: the frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata showed no required config paths.
Instruction Scope
Instructions stay within the expected scope: authenticate (or obtain an anonymous token), create a session, upload files, run SSE-based editing, and export. They explicitly instruct uploading user media to an external API (mega-api-prod.nemovideo.ai) and saving session_id. There is no instruction to read unrelated system files or other credentials. The requirement to auto-detect an install path for the X-Skill-Platform header is vague for an instruction-only skill and may be ambiguous to implement.
Install Mechanism
This is an instruction-only skill with no install spec or code files, so nothing is written to disk by an installer — lowest install risk.
Credentials
Only one environment variable (NEMO_TOKEN) is declared as required and used for Bearer auth, which is proportionate for a third-party API. The skill also documents an anonymous-token flow when no env var is present. No unrelated secret or credential requests are present.
Persistence & Privilege
always is false and the skill does not request elevated platform privileges. It may store session identifiers (implied by the config path), but it does not request or modify other skills' configs or system-wide settings.
Assessment
This skill appears to do what it says: it uploads your videos to a cloud service that performs rendering and returns a downloadable MP4. Before installing/using: (1) Be aware your video files (and associated metadata) will be sent to https://mega-api-prod.nemovideo.ai — do not upload sensitive or private footage unless you trust the service and its privacy policy. (2) The skill will use NEMO_TOKEN if present; otherwise it will generate an anonymous token via the described API (tokens expire after 7 days). If you prefer control, set NEMO_TOKEN to a token you manage. (3) The frontmatter references storing data under ~/.config/nemovideo/ and requires attribution headers; confirm where session IDs or tokens will be stored and whether you are comfortable with that. (4) The skill's source/homepage is missing and owner identity is unknown — consider seeking documentation or an official homepage for the service before sending production content. (5) If you need tighter assurance, ask the publisher for a privacy policy, official SDK, or test with throwaway/non-sensitive data first.

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

Runtime requirements

🎨 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk975q467ffsjdqebr77dk22c65851rs9
59downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "create my raw video clips"
  • "export 1080p MP4"
  • "add branded motion graphics, clean up"

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.

Designer Video — Turn Clips Into Branded Videos

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

A quick example: upload a 60-second product walkthrough recording, type "add branded motion graphics, clean up the cuts, and apply a consistent color palette", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: keeping clips under 2 minutes gives the AI more precise control over design consistency.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

HeaderValue
X-Skill-Sourcedesigner-video
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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 → "add branded motion graphics, clean up the cuts, and apply a consistent color palette" → 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 "add branded motion graphics, clean up the cuts, and apply a consistent color palette" — 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 social platforms and presentations.

Comments

Loading comments...