Skill flagged — suspicious patterns detected

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

Video Clip Maker Ai Free

v1.0.0

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

0· 52·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/video-clip-maker-ai-free.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-clip-maker-ai-free
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description (cloud video clip creation) aligns with the APIs and flows described (upload, SSE, render/export). However SKILL.md frontmatter advertises a required config path (~/.config/nemovideo/) while registry metadata lists no required config paths — this mismatch is unexplained and worth asking the publisher about. The required env (NEMO_TOKEN) is coherent for a cloud API.
Instruction Scope
Instructions stay within the editing/exporting domain: create session, upload video, run SSE, poll render status, return download URL. They explicitly instruct the agent to look for NEMO_TOKEN in env and, if missing, to request an anonymous token from the external endpoint. The skill will send user-supplied files to mega-api-prod.nemovideo.ai — expected for the purpose, but a clear privacy/exfiltration action the user should be aware of.
Install Mechanism
No install spec and no code files — lowest disk risk. All runtime behavior is instruction-only and performs network calls; nothing is written by an installer.
!
Credentials
The only declared credential is NEMO_TOKEN (primaryEnv), which makes sense. But SKILL.md metadata mentions a config path (~/.config/nemovideo/), which the registry listing did not show — inconsistent declarations. The skill will also read environment variables and may use any existing NEMO_TOKEN it finds; if one exists in your environment it will be used to authorize uploads and renders (i.e., the skill can use/expose that token to the external service).
Persistence & Privilege
always is false and there is no install-time persistence. The skill does request an ephemeral anonymous token if none exists, but it doesn't ask to be force-enabled or to alter other skills' config.
Scan Findings in Context
[no-code-files-found] expected: The scanner found no code files (instruction-only skill). This is expected, but means static regex findings are not available — review the SKILL.md carefully for behavior (network calls, token handling).
What to consider before installing
This skill will upload any video files you provide to an external service (mega-api-prod.nemovideo.ai) and uses a NEMO_TOKEN (it will create an anonymous one if none exists). Before installing/using it: 1) Confirm you trust nemovideo.ai (privacy, retention, and terms) because your video content is sent off-device. 2) Check whether you already have a NEMO_TOKEN in your environment — the skill will use it if present. 3) Ask the publisher about the mismatched config-path declaration (~/.config/nemovideo/) in the SKILL.md frontmatter vs the registry metadata. 4) If you handle sensitive content, do not upload until you verify storage/retention policies. If you want help drafting questions to the publisher or vetting the domain/terms, I can help.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97agrrzkgkzyn401f56arr7mx85k75k
52downloads
0stars
1versions
Updated 2d ago
v1.0.0
MIT-0

Getting Started

Send me your raw footage and I'll handle the AI clip creation. Or just describe what you're after.

Try saying:

  • "create a 3-minute phone recording from a birthday party into a 1080p MP4"
  • "cut this into a 30-second highlight clip with music and transitions"
  • "generating short shareable clips from longer video recordings for TikTok creators"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

  • Generate a UUID as client identifier
  • POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
  • Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Video Clip Maker AI Free — Create and Export Short Clips

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

Here's a typical use: you send a a 3-minute phone recording from a birthday party, ask for cut this into a 30-second highlight clip with music and transitions, 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 — clips under 60 seconds process significantly faster than longer footage.

Matching Input to Actions

User prompts referencing video clip maker ai 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.

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

HeaderValue
X-Skill-Sourcevideo-clip-maker-ai-free
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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

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 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)

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 "cut this into a 30-second highlight clip with music and transitions" — 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 → "cut this into a 30-second highlight clip with music and transitions" → 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...