Free Video Fast

v1.0.0

Get edited MP4 videos ready to post, without touching a single slider. Upload your raw video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "tr...

0· 76·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 vcarolxhberger/free-video-fast.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install free-video-fast
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (cloud video editing) match the declared env var (NEMO_TOKEN), declared config path (~/.config/nemovideo/), and the SKILL.md's API endpoints. The requested credential and endpoints are consistent with a third‑party video processing backend.
Instruction Scope
Instructions direct the agent to upload user-supplied media, create or use an auth token, create sessions, stream SSE, poll render status, and return download URLs — all expected for this service. Note: the skill will auto-generate an anonymous token and call the external API if NEMO_TOKEN is not set, and it instructs storing a session_id for later requests. It also specifies not to display raw API responses or token values to the user.
Install Mechanism
No install spec or code files — instruction-only skill. Nothing is downloaded or written by default by an installer. Lowest install risk.
Credentials
Only a single credential (NEMO_TOKEN) is declared, which is appropriate for a service API. However, the skill will obtain an anonymous token from the external API automatically if NEMO_TOKEN is unset, so the skill can operate (and transmit media) without the user explicitly providing credentials.
Persistence & Privilege
always is false and autonomous invocation is default. The skill asks to store a session_id and references a config path for nemovideo; that is reasonable for session persistence and does not request system-wide or other-skills' config changes.
Assessment
This skill will upload any video/audio files you give it to https://mega-api-prod.nemovideo.ai and may create an anonymous API token if you don't provide NEMO_TOKEN. That behavior is consistent with its stated purpose but has privacy implications: don't send sensitive footage unless you trust the service; check nemovideo.ai's privacy/retention policy if available. Be aware the skill may persist a session_id under ~/.config/nemovideo/ (or in runtime storage) and will include headers that may reveal platform/install-path info. If you prefer control, set your own NEMO_TOKEN (and review token storage practices) or avoid sending private media.

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

Runtime requirements

Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk970qjaykdrfzddt5xmrd1n8b585bq86
76downloads
0stars
1versions
Updated 6d ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "create my raw video clips"
  • "export 1080p MP4"
  • "trim, add transitions, and export a"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

  1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
  2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Free Video Fast — Edit and Export Videos Free

Drop your raw video clips in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute phone recording, ask for trim, add transitions, and export a clean video for free, and about under a minute later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 60 seconds process the fastest.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

  1. SessionPOST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
  2. Chat (SSE)POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
  3. UploadPOST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
  4. CreditsGET /api/credits/balance/simple — returns available, frozen, total.
  5. StateGET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
  6. ExportPOST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim, add transitions, and export a clean video for free" — 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.

Common Workflows

Quick edit: Upload → "trim, add transitions, and export a clean video for free" → Download MP4. Takes under a minute 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.

Comments

Loading comments...