Free Video Free

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — trim, add music, and export this video for free — and get edited MP4 video...

0· 91·0 current·0 all-time
bypeandrover adam@peand-rover

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for peand-rover/free-video-free.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install free-video-free
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill's name and description match its runtime instructions: it uploads user-provided video files and drives a cloud render pipeline at mega-api-prod.nemovideo.ai using a NEMO_TOKEN. Required headers, endpoints, and workflows all align with a remote video-editing service.
Instruction Scope
SKILL.md confines actions to the nemovideo API (auth, session creation, SSE chat, upload, export, state). It does not instruct reading unrelated system files or other environment variables. A minor ambiguity: it instructs the agent to 'auto-detect' an install-platform value for the X-Skill-Platform header, which may require inspecting the runtime/install path (this is vague but not obviously malicious).
Install Mechanism
This is an instruction-only skill with no install spec or bundled code, so nothing is downloaded or written by the skill itself — lowest-risk installation profile.
Credentials
Only a single credential (NEMO_TOKEN) is declared as required and is directly used for Bearer auth with the service, which is proportionate. Minor inconsistency: the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — if the skill actually reads that directory it would broaden access and should be clarified.
Persistence & Privilege
The skill does not request always:true and does not ask to modify other skills or system-wide settings. It instructs the agent to persist session_id (normal for interacting with a remote service), which is proportionate for its purpose.
Assessment
This skill appears to do what it says: it uploads videos to nemovideo.ai and returns edited exports using a NEMO_TOKEN. Before installing or using it, consider: (1) Do not upload sensitive or private videos unless you trust the nemovideo service and its retention/privacy policy. (2) The skill can auto-generate an anonymous token by calling https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token — that will create a short-lived token; treat it like any credential. (3) Clarify the config-path discrepancy: SKILL.md mentions ~/.config/nemovideo/ even though the registry didn’t declare required config paths — ask the publisher whether the agent will read that directory. (4) Because the skill is instruction-only and can be invoked by the agent, avoid granting it or sending content you wouldn’t want uploaded automatically; test with non-sensitive sample videos first. (5) If you need stricter control, set NEMO_TOKEN yourself (so the skill won’t request anonymous auth) and review network activity or privacy policy for the backend service.

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

Runtime requirements

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

Getting Started

Send me your video clips and I'll handle the free video editing. Or just describe what you're after.

Try saying:

  • "edit a 2-minute MP4 recorded on a smartphone into a 1080p MP4"
  • "trim, add music, and export this video for free"
  • "editing and exporting videos at no cost for casual creators"

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.

Free Video Free — Edit and Export Videos Free

This tool takes your video clips and runs free video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute MP4 recorded on a smartphone and want to trim, add music, and export this video for free — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process and export the fastest.

Matching Input to Actions

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

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.

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

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

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 music, and export this 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 across platforms and devices.

Common Workflows

Quick edit: Upload → "trim, add music, and export this video for free" → Download MP4. Takes 30-60 seconds 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...