To Ai Video

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — convert my footage into a polished video with cuts, transitions, and capti...

0· 86·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/to-ai-video.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "To Ai Video" (mhogan2013-9/to-ai-video) from ClawHub.
Skill page: https://clawhub.ai/mhogan2013-9/to-ai-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 to-ai-video

ClawHub CLI

Package manager switcher

npx clawhub@latest install to-ai-video
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (AI video conversion) align with requirements and actions: it needs a NEMO_TOKEN, creates sessions, uploads video, and requests renders from the nemo video backend. Nothing requested appears unrelated to video editing.
Instruction Scope
Runtime instructions direct the agent to contact mega-api-prod.nemovideo.ai, create/refresh an anonymous token if NEMO_TOKEN is absent, create sessions, upload files, stream SSE responses, and poll renders. These are expected for a cloud video service. Minor scope note: the docs describe deriving an X-Skill-Platform header by inspecting install paths (e.g., ~/.clawhub/ or ~/.cursor/skills/), which implies checking local paths; the SKILL.md does not otherwise require broader filesystem reads — this is a small mismatch to be aware of.
Install Mechanism
No install step or remote downloads; the skill is instruction-only, so nothing is written to disk by an installer. This is the lowest-risk install model.
Credentials
Only NEMO_TOKEN is required (declared as primaryEnv). That aligns with needing authorization to a third‑party video-processing API. The metadata also lists a config path (~/.config/nemovideo/), which is plausible for storing local service config but is not otherwise used in the instructions — a small, explainable mismatch.
Persistence & Privilege
always is false and the skill is user-invocable with autonomous invocation allowed (platform default). The skill does not request persistent platform-level privileges beyond using the service token/session and local config path.
Assessment
This skill will upload your videos and metadata to a third‑party service (mega-api-prod.nemovideo.ai) for processing. Before installing, consider: 1) Do you trust the service to handle your footage and any sensitive content? 2) The skill will use NEMO_TOKEN if present or automatically obtain an anonymous token (100 free credits, 7‑day expiry) — store tokens securely if you provide one. 3) Metadata lists a local config path (~/.config/nemovideo/) and the instructions reference deriving a platform header from install paths; confirm you’re comfortable with the platform reading those paths or that the skill actually needs them. 4) Check the service terms/privacy policy if you need guarantees about retention or sharing of uploaded media. Functionally the skill appears coherent with its stated purpose, but the privacy and data‑sharing implications are the primary things to evaluate before use.

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

Runtime requirements

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

Getting Started

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

Try saying:

  • "convert my raw video footage"
  • "export 1080p MP4"
  • "convert my footage into a polished"

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.

To AI Video — Convert Footage Into Finished Videos

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

Say you have a 2-minute raw screen recording and want to convert my footage into a polished video with cuts, transitions, and captions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is to-ai-video, 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 → "convert my footage into a polished video with cuts, transitions, and captions" → 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 "convert my footage into a polished video with cuts, transitions, and captions" — 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.

Comments

Loading comments...