Video Editor With Ai Features

v1.0.0

Turn a 2-minute unedited screen recording into 1080p polished edited clips just by typing what you need. Whether it's automatically editing raw footage into...

0· 77·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 susan4731-wilfordf/video-editor-with-ai-features.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Video Editor With Ai Features" (susan4731-wilfordf/video-editor-with-ai-features) from ClawHub.
Skill page: https://clawhub.ai/susan4731-wilfordf/video-editor-with-ai-features
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 video-editor-with-ai-features

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-editor-with-ai-features
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill claims to run remote GPU-based video editing and only requests a single service token (NEMO_TOKEN) which aligns with calling a third-party API. Requiring an API token is proportionate to the stated purpose. Minor inconsistency: the registry metadata earlier said there are no required config paths, but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/). This should be clarified but does not by itself contradict the described purpose.
Instruction Scope
The SKILL.md explicitly instructs the agent to auto-create an anonymous token (POST to https://mega-api-prod.nemovideo.ai), create sessions, upload files (multipart file uploads or URLs), poll job status, and stream SSE results. Those actions are expected for a cloud render pipeline. The instructions also say to detect local install paths (~/.clawhub/, ~/.cursor/skills/) to set an attribution header and to include Authorization headers on every request. Those filesystem checks and automatic anonymous-token creation are functional for the service but touch user-local paths and make network requests automatically — worth informing users.
Install Mechanism
This is instruction-only with no install spec and no code files, so nothing will be downloaded or written by an installer. That limits supply-chain risks.
Credentials
The skill requests a single credential (NEMO_TOKEN) as primaryEnv, which fits a remote-service integration. However, the SKILL.md will generate an anonymous token itself if NEMO_TOKEN is not present, and the frontmatter references a config path (~/.config/nemovideo/) and reads install-path markers in the home directory — both are privacy-relevant. No unrelated cloud credentials are requested.
Persistence & Privilege
The skill is not marked always:true and does not request system-wide privileges. It instructs storing a session_id and using tokens for subsequent API calls; it does not explicitly instruct modifying other skills or global agent configuration. Autonomous invocation is allowed by default (platform normal) but not escalated here.
Assessment
This skill appears to be a straightforward client for a cloud video-editing backend, but review these points before installing: - Network/backend trust: The skill talks to https://mega-api-prod.nemovideo.ai and will upload your videos there. Only use it with footage you are comfortable sending to that service. Check the provider's privacy/retention policy if the content is sensitive. - Token behavior: If you do not provide NEMO_TOKEN, the skill will automatically obtain an anonymous token for you (100 free credits, 7-day validity). If you prefer control, provide your own token and confirm where tokens/sessions are stored. - Local-file and path access: The instructions expect to upload local files and also detect local install paths (~/.clawhub/, ~/.cursor/skills/) and reference ~/.config/nemovideo/. If you are uncomfortable with the skill reading these paths, do not install or ask the author to remove/limit that behavior. - Clarify metadata discrepancy: The registry metadata said no required config paths but SKILL.md frontmatter lists ~/.config/nemovideo/. Ask the publisher to confirm what local paths (if any) the skill will access and why. - Operational cues: The skill will make automatic network requests (session creation, SSE, polling). If you need to audit or restrict outbound traffic, plan for that. If you are okay with sending media to the provider and carrying the privacy tradeoffs above, this skill's footprint is proportionate to its purpose. If not, request changes or avoid installation.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97ajz63tg8ab1qx4vyf72101n84tgsy
77downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

Got raw video footage to work with? Send it over and tell me what you need — I'll take care of the AI-powered video editing.

Try saying:

  • "edit a 2-minute unedited screen recording into a 1080p MP4"
  • "cut the pauses, add background music, and generate captions"
  • "automatically editing raw footage into a clean, shareable video for content creators and marketers"

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.

Video Editor with AI Features — Edit and Export AI-Enhanced Videos

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

A quick example: upload a 2-minute unedited screen recording, type "cut the pauses, add background music, and generate captions", 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.

Matching Input to Actions

User prompts referencing video editor with ai features, 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 video-editor-with-ai-features, 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.

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.

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

Common Workflows

Quick edit: Upload → "cut the pauses, add background music, and generate 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 "cut the pauses, add background music, and generate 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...