Free Editor Generation

v1.0.0

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

0· 38·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 dsewell-583h0/free-editor-generation.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Free Editor Generation" (dsewell-583h0/free-editor-generation) from ClawHub.
Skill page: https://clawhub.ai/dsewell-583h0/free-editor-generation
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-editor-generation

ClawHub CLI

Package manager switcher

npx clawhub@latest install free-editor-generation
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (auto video editing) match the declared requirement (NEMO_TOKEN) and the SKILL.md's network calls (session creation, upload, render, export). The required credential is directly tied to the backend API the skill documents.
Instruction Scope
Instructions are focused on session creation, SSE messaging, uploads, export polling, and credit/state checks — all expected for a cloud render/edit service. The SKILL.md also asks to derive attribution headers and detect an install path (~/.clawhub/ or ~/.cursor/skills/) to set X-Skill-Platform; that file-system/installation-path detection is unnecessary for core functionality and slightly broadens what the agent is asked to read, though it is not obviously malicious.
Install Mechanism
No install spec or code files — instruction-only skill. No downloads or archives, so there is no install-time code execution risk.
Credentials
Only a single environment variable (NEMO_TOKEN) is required and documented as the primary credential for the nemo API. The instructions also describe generating an anonymous token if NEMO_TOKEN is absent, which is coherent. No unrelated secrets or high-privilege env vars are requested.
Persistence & Privilege
always is false and the skill does not request persistent system changes or to modify other skills/configurations. It does not request elevated privileges beyond network access and reading the install path (for header attribution).
Assessment
This skill appears to do what it says: it uploads your videos to nemo's cloud API, requests a session, runs remote edits, and returns a download URL. Before installing/use, consider: (1) Privacy — your raw video files and any metadata will be sent to https://mega-api-prod.nemovideo.ai; confirm you are comfortable uploading the content and check the service's data-retention/privacy policy. (2) Tokens — the skill uses NEMO_TOKEN if present, otherwise it will create an anonymous token by POSTing a generated UUID; anonymous tokens are short-lived. Don’t provide unrelated credentials. (3) Filesystem access — the skill asks the agent to detect an install path for an attribution header; this is not required for editing and you can restrict filesystem reads if you prefer. (4) Verify the backend domain and service provenance before sending sensitive footage. If you need offline-only editing or stricter privacy guarantees, do not use a cloud-based skill like this.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk977f0g8xqn1ayqhbsjbxpyyfd85n7qf
38downloads
0stars
1versions
Updated 17h ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "generate my raw video footage"
  • "export 1080p MP4"
  • "trim silences, add cuts, and export"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

  • Generate a UUID as client identifier
  • POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
  • The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Free Editor Generation — Generate Edited Videos Automatically

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

A quick example: upload a 2-minute unedited screen recording, type "trim silences, add cuts, and export a clean final video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster and yield cleaner results.

Matching Input to Actions

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

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

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.

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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

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)

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 silences, add cuts, and export a clean final video" — 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 silences, add cuts, and export a clean final video" → 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.

Comments

Loading comments...