Ai Video Generator Free Music

generate images or clips into music-backed videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. content creators and marketers use it for...

Security Scan

The skill's behavior mostly matches a video-upload/render service, but there are inconsistencies around required credentials and config paths and it instructs the agent to obtain and persist tokens/session state — these mismatches and persistence details deserve scrutiny before install.

Purpose & Capability

The skill claims to require NEMO_TOKEN (primary credential) but its runtime instructions explicitly describe how to obtain a free anonymous NEMO_TOKEN via the service API if the env var is not set. That mismatch between declared required env and the documented auto-provisioning is inconsistent. The SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) while the registry metadata said no config paths — another mismatch. Both raise questions about what the platform will actually require or persist.

Instruction Scope

The SKILL.md instructions stay within the stated purpose: creating sessions, uploading media, streaming SSE messages, polling render status, and exporting. It explicitly instructs uploading local files (multipart form uploads or URLs) and to store a session_id for later requests — reading local files and persisting a session is expected for a video upload skill. The doc also instructs not to display raw API responses or token values to the user; while reasonable for UX, it reduces transparency about what is being stored or sent.

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 lowers technical install risk.

Credentials

Only one credential (NEMO_TOKEN) is declared, which matches the service integration; however, the fact the skill will auto-create an anonymous token and wants to persist session_id (and frontmatter references a config path) means it will create or write credentials/state. The registry metadata and SKILL.md disagree about config paths, so it's unclear whether the skill expects to read/write ~/.config/nemovideo/. Persisting tokens or session IDs without clear storage rules is disproportionate if users expect no persistent credentials.

Persistence & Privilege

always:false (normal) and no install script. The skill instructs automatic first-time connection and to store a session token for later requests; that gives it ongoing ability to act on the remote service on behalf of the user until the token expires or is revoked. This is not inherently malicious, but combined with the config-path ambiguity and auto-provisioned tokens it increases the importance of knowing where/how the tokens/session are stored and how to revoke them.

What to consider before installing

Key points to consider before installing: - The skill will upload your files to https://mega-api-prod.nemovideo.ai and may persist a session_id and/or token. If you plan to upload sensitive media, confirm you trust that endpoint and its privacy/retention policy. - The registry metadata and SKILL.md disagree: NEMO_TOKEN is listed as required but the skill also describes automatically obtaining an anonymous token if none is present; the SKILL.md mentions a config path (~/.config/nemovideo/) while registry metadata did not. Ask the author which is authoritative and where tokens/session state are stored and how to revoke/delete them. - If you prefer control, set your own NEMO_TOKEN (if supported) or avoid persistent storage by clearing session info after use. - Because this skill can automatically connect and persist state, limit use on agents that have access to sensitive local files or system-wide credentials until you verify behavior. - If you need higher assurance, request clarification or source code (install script, storage handling) before enabling the skill.

Getting Started

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

Try saying:

• "generate five product photos and a script into a 1080p MP4"
• "create a 30-second video with free background music"
• "generating videos with free background music from images or clips for content creators and marketers"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

AI Video Generator Free Music — Generate Videos with Free Music

This tool takes your images or clips and runs AI video creation with music through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have five product photos and a script and want to create a 30-second video with free background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter videos under 60 seconds pair best with a single music track for clean output.

Matching Input to Actions

User prompts referencing ai video generator free music, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...	Action	Skip 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:

Header	Value
X-Skill-Source	ai-video-generator-free-music
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process 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 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 Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Common Workflows

Quick edit: Upload → "create a 30-second video with free 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 30-second video with free background music" — 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 social platforms.