Skill flagged — suspicious patterns detected

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

Ai Video Maker Free Google

v1.0.0

Turn five product photos and a logo file into 1080p ready-to-share videos just by typing what you need. Whether it's creating videos from images or clips wit...

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

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-video-maker-free-google
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's stated purpose (turn images/clips into 1080p videos) aligns with the runtime instructions which call a video-rendering API. However the skill name includes the trademark 'Google' while all network endpoints point to mega-api-prod.nemovideo.ai (no Google reference) and there's no homepage or source URL — this is misleading and should be clarified.
!
Instruction Scope
SKILL.md contains precise runtime instructions for session creation, file uploads, SSE, polling, and rendering using a remote API. It also instructs the agent to 'Keep the technical details out of the chat', which could be used to hide operational details from users. The frontmatter requests a config path (~/.config/nemovideo/) and an auto-detect of install path for X-Skill-Platform, but the registry metadata listed no config paths — this inconsistency is concerning because it could lead the agent to read local filesystem paths not mentioned in the top-level metadata.
Install Mechanism
There is no install spec and no code files — the skill is instruction-only, which is lower-risk from an installation perspective because it does not drop new binaries or archives on disk.
Credentials
The skill only requires a single credential (NEMO_TOKEN), which is proportionate to a service that needs an API token. However, SKILL.md promises an anonymous-token flow if no NEMO_TOKEN is present and also lists a config path in frontmatter; the registry metadata did not. The discrepancy between top-level metadata and the frontmatter about config paths is unexplained and worth verifying before granting environment access.
Persistence & Privilege
The skill does not request 'always: true' and doesn't ask to modify other skills or system settings. Autonomous invocation is allowed (the platform default) but there is no extra persistent privilege requested.
What to consider before installing
This skill appears to implement a cloud video-rendering integration and only needs one API token (NEMO_TOKEN), which is reasonable. But: (1) the package name uses 'Google' while the backend is nemovideo.ai and there is no source/homepage — that may be misleading; (2) SKILL.md frontmatter lists a local config path (~/.config/nemovideo/) while the registry metadata did not — ask the developer which is correct and whether the skill will read local files; (3) the instructions tell the agent to hide technical details from users, which could obscure what the skill is doing. Before installing, verify the vendor/source, avoid supplying high-privilege credentials (do not reuse sensitive tokens), and consider testing with a throwaway token or the anonymous flow. If you must use it, monitor network requests or run it in an environment where you can inspect outgoing traffic and filesystem reads. If the developer can confirm the config-path behavior and explain the Google naming, that would reduce the risk.

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

Runtime requirements

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

Getting Started

Share your images or clips and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

  • "create my images or clips"
  • "export 1080p MP4"
  • "turn these images into a 30-second"

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.

AI Video Maker Free Google — Create and Export Videos Free

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

Here's a typical use: you send a five product photos and a logo file, ask for turn these images into a 30-second promo video with music and text, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — using fewer than ten images keeps generation time under a minute.

Matching Input to Actions

User prompts referencing ai video maker free google, 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.

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.

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

HeaderValue
X-Skill-Sourceai-video-maker-free-google
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

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

  • "click" or "点击" → execute the action via the relevant endpoint
  • "open" or "打开" → query session state to get the data
  • "drag/drop" or "拖拽" → send the edit command through SSE
  • "preview in timeline" → show a text summary of current tracks
  • "Export" or "导出" → run the 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 "turn these images into a 30-second promo video with music and text" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across Google Drive, YouTube, and social platforms.

Common Workflows

Quick edit: Upload → "turn these images into a 30-second promo video with music and text" → 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...