Skill flagged — suspicious patterns detected

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

Ai Video Editor Baby Dance

v1.0.0

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

0· 35·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/ai-video-editor-baby-dance.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Ai Video Editor Baby Dance" (dsewell-583h0/ai-video-editor-baby-dance) from ClawHub.
Skill page: https://clawhub.ai/dsewell-583h0/ai-video-editor-baby-dance
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-baby-dance

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-video-editor-baby-dance
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name and description claim a cloud video editor and the SKILL.md contains API endpoints and upload/export flows that match that purpose. However, metadata declares a required env var (NEMO_TOKEN) and a config path (~/.config/nemovideo/) while the runtime instructions describe auto-provisioning a token if none is present and never instruct reading the declared config path — this mismatch is incoherent and should be clarified.
Instruction Scope
Instructions stay within the stated task (creating sessions, upload, SSE streaming, export polling) and explicitly instruct uploading user video files to a remote service. This is expected for a cloud video editor, but it is important to note the skill will send potentially sensitive user media off-device to an external API (mega-api-prod.nemovideo.ai). The SKILL.md also asks to auto-detect install platform from an install path (implies reading runtime/install path), which is a minor scope extension but not obviously malicious.
Install Mechanism
No install spec or code files are present (instruction-only). Nothing is written to disk by an installer in the bundle — lower install risk. Runtime network calls are required but are described in the instructions.
!
Credentials
Only one credential is declared (NEMO_TOKEN), which fits a cloud API. However, requires.env lists NEMO_TOKEN as required while the SKILL.md also instructs obtaining an anonymous token via the API if the env var is absent — inconsistent. Metadata additionally declares a config path (~/.config/nemovideo/) but instructions never reference reading it. These mismatches raise questions about what secrets/config the skill actually needs and whether it will read local config files.
Persistence & Privilege
No 'always' privilege; the skill is user-invocable and can run autonomously (platform default). There is no install-time code that claims to modify other skills or system-wide settings in the SKILL.md. The only persistence implied is use of a session token for API operations (normal for this purpose).
What to consider before installing
This skill appears to do what it says (upload your video to a cloud backend for editing), but there are a few red flags to consider before installing: - Data/privacy: Using the skill will upload your raw video clips to https://mega-api-prod.nemovideo.ai. Only proceed if you are comfortable sending those files to that service. Test with non-sensitive clips first. - Token inconsistency: The registry declares NEMO_TOKEN as required but the instructions also auto-generate an anonymous token if it is missing. Ask the publisher which behavior is intended and whether any obtained tokens are persisted on disk or in agent state. - Unused configPath: Metadata lists ~/.config/nemovideo/ but SKILL.md never reads it. Ask why that path is declared and whether the skill will read local configuration files. - Provenance: There is no homepage or known source for this skill. If possible, request publisher contact, privacy policy, or a public project repo to verify the backend is legitimate. If you still want to try it: run with a throwaway/non-sensitive video first, do not provide any private tokens you aren't willing to expose to the remote service, and ask the skill author to clarify the NEMO_TOKEN/configPath behavior and token storage/retention policy.

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

Runtime requirements

👶 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97acp2ebvt76kcmq109cep4n985kear
35downloads
0stars
1versions
Updated 1d ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "edit my raw video footage"
  • "export 1080p MP4"
  • "trim the best moments, add upbeat"

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 Baby Dance — Edit Baby Dance Videos Fast

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

Here's a typical use: you send a a 30-second phone clip of a baby dancing, ask for trim the best moments, add upbeat music, and sync cuts to the beat, 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 process faster and work best for social sharing.

Matching Input to Actions

User prompts referencing ai video editor baby dance, 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-Sourceai-video-editor-baby-dance
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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

Common Workflows

Quick edit: Upload → "trim the best moments, add upbeat music, and sync cuts to the beat" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the best moments, add upbeat music, and sync cuts to the beat" — 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 Instagram, TikTok, and YouTube.

Comments

Loading comments...