Create Ai Video Free

v1.0.0

create images or clips into AI-generated videos with this create-ai-video-free skill. Works with MP4, MOV, JPG, PNG files up to 500MB. content creators and m...

0· 96·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 whitejohnk-26/create-ai-video-free.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Create Ai Video Free" (whitejohnk-26/create-ai-video-free) from ClawHub.
Skill page: https://clawhub.ai/whitejohnk-26/create-ai-video-free
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 create-ai-video-free

ClawHub CLI

Package manager switcher

npx clawhub@latest install create-ai-video-free
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (AI video generation) align with the endpoints, upload, render, credits, and session flow in SKILL.md. Requesting a single API token (NEMO_TOKEN) and a config path for nemo-related state is reasonable for a cloud render service.
Instruction Scope
Instructions tell the agent to upload user media to mega-api-prod.nemovideo.ai, create/refresh an anonymous token if NEMO_TOKEN is missing, manage a session_id, stream SSE responses, and poll status. These are expected for a remote rendering service, but they do mean user files and prompts will be transmitted off-device. Minor inconsistency: registry metadata lists NEMO_TOKEN as required, yet the runtime instructions also describe obtaining an anonymous token automatically if it's not present.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is downloaded or written by an installer. Risk from installation is low.
Credentials
Only one env var is declared (NEMO_TOKEN), which fits the described cloud API. Metadata also references a config path (~/.config/nemovideo/), implying local storage of tokens/session state — plausible but worth noting. The skill does not request unrelated credentials.
Persistence & Privilege
always is false and the skill does not ask to modify other skills or system-wide settings. It will operate autonomously by design (disable-model-invocation false), which is normal for skills, but increases runtime reach since it can be invoked by the agent.
Assessment
This skill appears to do what it says (remote AI video rendering) but it will upload any files and prompts you send to an external domain (mega-api-prod.nemovideo.ai) and will create/store an anonymous API token if you don't provide one. Before installing or using: (1) confirm you trust the service and its privacy policy for handling uploaded media, (2) avoid sending sensitive or private files, (3) consider providing your own scoped/ephemeral NEMO_TOKEN rather than relying on anonymous token creation, and (4) be aware the agent may call the skill autonomously — limit use to trusted contexts or test in a sandbox first. Note the small inconsistency between the registry requiring NEMO_TOKEN and the skill's runtime fallback to generate one automatically; this is likely intentional but worth understanding.

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

Runtime requirements

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

Getting Started

Send me your images or clips and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

  • "create five product photos and a logo file into a 1080p MP4"
  • "turn these photos into a 30-second promo video with background music"
  • "generating videos from images or text without manual editing for content creators and marketers"

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.

Create AI Video Free — Generate Videos from Images or Clips

Send me your images or 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 five product photos and a logo file, type "turn these photos into a 30-second promo video with background music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: using fewer images with clear subjects speeds up generation significantly.

Matching Input to Actions

User prompts referencing create ai video free, 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.

Base URL: https://mega-api-prod.nemovideo.ai

EndpointMethodPurpose
/api/tasks/me/with-session/nemo_agentPOSTStart a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_ssePOSTSend 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>POSTUpload a file (multipart) or URL.
/api/credits/balance/simpleGETCheck remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latestGETFetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambdaPOSTStart 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:

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

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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

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.

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

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 → "turn these photos into a 30-second promo video with background music" → 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 "turn these photos into a 30-second promo video with background music" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across social platforms.

Comments

Loading comments...