Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Video Editing With Music Free

v1.0.0

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

0· 68·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/video-editing-with-music-free.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-editing-with-music-free
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description match the runtime instructions: the SKILL.md describes a cloud video-editing API and upload/render flows which fit the stated purpose. The single required env var (NEMO_TOKEN) is consistent with a hosted API. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — this mismatch should be clarified.
!
Instruction Scope
Instructions tell the agent to POST user video files and session messages to external endpoints and to create/use tokens. They also instruct the agent to "keep the technical details out of the chat," which grants the agent explicit permission to hide network/auth activity from users — this reduces transparency and raises the risk of unnoticed data exfiltration. Otherwise the API calls and upload flow are within the expected scope for a cloud video-editing skill.
Install Mechanism
No install spec and no code files (instruction-only skill). This is lower risk because nothing is written to disk by an installer, but runtime network activity will still occur per the SKILL.md.
Credentials
Only one credential is declared (NEMO_TOKEN) which is appropriate for an external API. The skill explicitly supports generating an anonymous token if NEMO_TOKEN is absent (so it can operate without user-supplied secrets). The earlier registry metadata said 'no required config paths' while the skill frontmatter includes a config path — an inconsistency to resolve. Ensure NEMO_TOKEN does not contain unrelated or high-privilege secrets before supplying it.
Persistence & Privilege
always:false and no install-time persistence are appropriate. Autonomous invocation (default) is allowed but not, by itself, a red flag — combine this with the instruction to hide technical details if you want stricter controls.
What to consider before installing
This skill wires your uploads to an external service (mega-api-prod.nemovideo.ai). Before installing: (1) confirm you trust that external service and its privacy policy — your videos will be uploaded and processed remotely; (2) do not set NEMO_TOKEN to any credential used for other services (use a dedicated token); (3) ask the publisher to explain the metadata mismatch (SKILL.md references ~/.config/nemovideo/ but registry metadata said none); (4) be cautious because the instructions explicitly tell the agent to hide technical/network details from the chat — if you want transparency, avoid installing or ask for the skill to remove that instruction; (5) if you need stronger guarantees, test with non-sensitive sample videos first and verify where outputs and logs are stored and who can access them.

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

Runtime requirements

🎵 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk979aqfszf918jj2rrwq4fanwd85dk4v
68downloads
0stars
1versions
Updated 5d ago
v1.0.0
MIT-0

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

  • "edit a 2-minute travel video clip into a 1080p MP4"
  • "add background music to my video and sync it to the cuts"
  • "adding free background music to videos without paid software for content creators"

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.

Video Editing With Music Free — Edit Videos With Background Music

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

Here's a typical use: you send a a 2-minute travel video clip, ask for add background music to my video and sync it to the cuts, and about 30-60 seconds 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 sync music most accurately.

Matching Input to Actions

User prompts referencing video editing with music 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.

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

HeaderValue
X-Skill-Sourcevideo-editing-with-music-free
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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.

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

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add background music to my video and sync it to the cuts" — 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 social platforms.

Common Workflows

Quick edit: Upload → "add background music to my video and sync it to the cuts" → 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...