Skill flagged — suspicious patterns detected

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

Video Cv Maker Free

v1.0.0

Turn a headshot photo and resume text into 1080p professional video CV just by typing what you need. Whether it's creating a video resume to send to employer...

0· 92·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 linmillsd7/video-cv-maker-free.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-cv-maker-free
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The declared purpose (create video CVs) matches the runtime instructions (calls to a nemovideo cloud render API, upload endpoints, render/export flows). However the SKILL.md metadata requests a config path (~/.config/nemovideo/) while the registry metadata listed none, and the skill declares NEMO_TOKEN as required but provides an anonymous-token fallback — this mismatch between declared 'required' assets and the runtime fallback is inconsistent.
Instruction Scope
Instructions tell the agent to: use NEMO_TOKEN if present, otherwise POST for an anonymous token; create sessions; upload files via multipart (files=@/path) or URLs; poll SSE and state endpoints; and include attribution headers derived from local install paths. These actions are within the skill's stated purpose but require reading user-supplied files (or file paths) and detecting install/config paths in the user's home directory — both privacy-sensitive and not fully reflected in the registry metadata.
Install Mechanism
Instruction-only skill with no install spec and no code files. Nothing is downloaded or written to disk by an install step as part of the skill bundle itself.
!
Credentials
Only NEMO_TOKEN is declared as the primary credential, which is appropriate for a cloud service. But SKILL.md also references a config path (~/.config/nemovideo/) and instructs deriving X-Skill-Platform from install paths (~/.clawhub/, ~/.cursor/skills/) — these imply the agent will inspect the filesystem for paths not declared in the registry metadata. The combination of needing a token and the skill reading home-directory paths is a privacy concern and is disproportionate to a minimal 'upload and render' description unless the token/config are truly required.
Persistence & Privilege
always:false and no install-time persistence requested. The skill requires creating ephemeral sessions with the backend, but it does not request forced always-on presence or modify other skills or system-wide settings.
What to consider before installing
This skill calls an external API (mega-api-prod.nemovideo.ai) to create and render videos and will upload photos and resume text you supply. Before installing: 1) Be aware your resume and headshot will be sent to that external service — don't send sensitive personal data you don't want uploaded. 2) The SKILL.md asks the agent to look for local config/install paths (~/.config/nemovideo/, ~/.clawhub/, ~/.cursor/skills/) to populate headers; decide whether you’re comfortable with the skill inspecting your home directory. 3) The skill declares NEMO_TOKEN but can also request an anonymous token from the API — anonymous tokens grant temporary credits, so the skill can operate without your token but will still contact the remote service. 4) Confirm the backend domain is legitimate and acceptable to you; if you need stronger guarantees, prefer an official publisher or an open-source skill you can audit. If you proceed, avoid including highly sensitive info in uploads and consider using a throwaway/limited token or reviewing network logs for unexpected activity.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk976yq12mvbjza4p6ampr3mnk1859scw
92downloads
0stars
1versions
Updated 6d ago
v1.0.0
MIT-0

Getting Started

Got text or photos to work with? Send it over and tell me what you need — I'll take care of the AI CV video creation.

Try saying:

  • "create a headshot photo and resume text into a 1080p MP4"
  • "create a 60-second video CV from my resume and photo with professional background music"
  • "creating a video resume to send to employers for job seekers"

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 CV Maker Free — Create and Export Video Resumes

This tool takes your text or photos and runs AI CV video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a headshot photo and resume text and want to create a 60-second video CV from my resume and photo with professional background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: keep your script under 90 seconds — recruiters rarely watch longer video CVs.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-cv-maker-free, 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.

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.

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

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)

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 → "create a 60-second video CV from my resume and photo with professional background music" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a 60-second video CV from my resume and photo with professional background music" — concrete instructions get better results.

Max file size is 200MB. Stick to JPG, PNG, PDF, DOCX for the smoothest experience.

Export as MP4 for widest compatibility across job portals and email attachments.

Comments

Loading comments...