Ai Video Generator Free Beat

generate audio beat files into beat-synced videos with this skill. Works with MP3, WAV, MP4, MOV files up to 200MB. music producers use it for generating fre...

Security Scan

The skill's requirements and runtime instructions align with its stated purpose (generating beat‑synced videos via a cloud API); nothing requests unrelated system credentials or installs arbitrary code, though it will call an external service and can auto-provision anonymous tokens.

Purpose & Capability

Name/description (beat-synced video generation) matches the declared primary credential (NEMO_TOKEN) and the SKILL.md endpoints for a nemo video backend. The declared primaryEnv is appropriate for a cloud render API. Minor metadata discrepancy: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) even though the registry summary earlier showed no required config paths.

Instruction Scope

Instructions stay within the video-generation scope: session creation, SSE streaming, uploads, render requests and polling. They instruct the agent to auto-obtain an anonymous token when NEMO_TOKEN is absent and to store session_id for subsequent calls — behavior expected for this integration but notable because it causes network calls and automatic credential issuance without explicit user-supplied API keys.

Install Mechanism

Instruction-only skill with no install steps or code files; nothing is downloaded or written by an installer spec. Low install-time risk.

Credentials

Only one credential (NEMO_TOKEN) is required and is justified by the backend API. The frontmatter also references a config path (~/.config/nemovideo/), which could imply reading or writing local config — the registry metadata earlier omitted this; the discrepancy should be clarified. No unrelated secrets or multiple unrelated env vars are requested.

Persistence & Privilege

always:false and no request to modify other skills or system-wide settings. The skill will hold a session_id and may persist or reuse an anonymous token for up to 7 days per the backend, which is consistent with its function.

Assessment

This skill appears internally consistent for generating videos via a nemo video backend, but it will upload your audio/video to an external service (mega-api-prod.nemovideo.ai) and can automatically request an anonymous token if you don't provide NEMO_TOKEN. Before installing: 1) Confirm you trust the external domain and the privacy policy for uploaded media. 2) If you prefer control, set your own NEMO_TOKEN instead of allowing anonymous token issuance. 3) Ask the publisher to clarify whether the skill reads/writes ~/.config/nemovideo/ (the SKILL.md frontmatter mentions it but registry metadata did not). 4) Avoid uploading sensitive or confidential audio/video unless you accept that it will be sent to the external service.

Getting Started

Ready when you are. Drop your audio beat files here or describe what you want to make.

Try saying:

• "generate a 3-minute MP3 beat track into a 1080p MP4"
• "generate a music video with visuals synced to this beat for free"
• "generating free videos synced to music beats for music producers"

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 Beat — Generate Videos From Beat Tracks

This tool takes your audio beat files and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute MP3 beat track and want to generate a music video with visuals synced to this beat for free — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter beat loops under 60 seconds render significantly faster.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: ai-video-generator-free-beat
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a music video with visuals synced to this beat for free" — concrete instructions get better results.

Max file size is 200MB. Stick to MP3, WAV, MP4, MOV for the smoothest experience.

Export as MP4 for widest compatibility across YouTube and SoundCloud.

Common Workflows

Quick edit: Upload → "generate a music video with visuals synced to this beat for free" → 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.