Skill flagged — suspicious patterns detected

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

Ai Video Editor B Roll

v1.0.0

Get b-roll enhanced video ready to post, without touching a single slider. Upload your raw footage (MP4, MOV, AVI, WebM, up to 500MB), say something like "au...

0· 54·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 tk8544-b/ai-video-editor-b-roll.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Ai Video Editor B Roll" (tk8544-b/ai-video-editor-b-roll) from ClawHub.
Skill page: https://clawhub.ai/tk8544-b/ai-video-editor-b-roll
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 ai-video-editor-b-roll

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-video-editor-b-roll
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The name/description (cloud-based AI b-roll insertion) aligns with the instructions to upload video files and call a remote rendering API. However the SKILL.md frontmatter declares a required config path (~/.config/nemovideo/) that is not reflected in the registry's top-level metadata, and there is no homepage or clear vendor provenance. The need for NEMO_TOKEN is expected, but the undocumented config path and missing source information are inconsistent with a well-described skill.
!
Instruction Scope
Runtime instructions direct the agent to upload user video files (multipart POST) and to POST for anonymous tokens if NEMO_TOKEN is absent, poll SSE endpoints, and include install-path-derived headers. Uploading user files and creating/using tokens is within the stated feature set, but the doc implies reading install/config paths and possibly persisting or deriving platform info from the filesystem—these actions extend scope beyond simple API calls and are not fully documented or justified.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That minimizes install-time risk.
Credentials
The skill only declares a single primary credential (NEMO_TOKEN), which is appropriate for a cloud video service. It also instructs the agent to generate an anonymous token via an external endpoint if NEMO_TOKEN is absent. The frontmatter's additional config path requirement (~/.config/nemovideo/) is not reflected in registry metadata and is not explained, which raises questions about where tokens or credentials will be stored.
Persistence & Privilege
always:false and no install script are good. However the skill implies creating a session token and may expect to persist state (session_id, possibly token) and to read install/config paths to set headers — it's unclear whether/where tokens are stored. Autonomous invocation is allowed (default) but not by itself a reason for concern.
What to consider before installing
This skill will upload your video files and interact with https://mega-api-prod.nemovideo.ai, using a NEMO_TOKEN credential (it can also request an anonymous token from that endpoint). Before installing or using it: 1) Confirm you trust the unknown service (there is no homepage or vendor info). 2) Decide whether you are comfortable uploading potentially sensitive video content to an external cloud. 3) Ask the publisher how/where the NEMO_TOKEN and session IDs are stored (the SKILL.md references ~/.config/nemovideo/ but the registry metadata doesn't). 4) Prefer providing an explicit NEMO_TOKEN only if you trust the service; otherwise decline and avoid automatic anonymous token creation. If you need higher assurance, request the skill's source or a vendor privacy/security policy; absent that, treat the skill as unproven and proceed cautiously.

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

Runtime requirements

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

Getting Started

Share your raw footage and I'll get started on AI b-roll insertion. Or just tell me what you're thinking.

Try saying:

  • "add my raw footage"
  • "export 1080p MP4"
  • "automatically find and insert relevant b-roll"

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.

AI Video Editor B-Roll — Auto-insert B-Roll into Videos

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

A quick example: upload a 2-minute talking head interview clip, type "automatically find and insert relevant b-roll footage to cover cuts and pauses", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: clearly scripted or narrated videos get more accurate b-roll matches from the AI.

Matching Input to Actions

User prompts referencing ai video editor b roll, 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 ai-video-editor-b-roll, 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).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 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 "automatically find and insert relevant b-roll footage to cover cuts and pauses" — 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 YouTube, Instagram, and Vimeo.

Common Workflows

Quick edit: Upload → "automatically find and insert relevant b-roll footage to cover cuts and pauses" → 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...