Brainrot Video Maker Free

Turn a 30-second gameplay or meme clip into 1080p brainrot-style videos just by typing what you need. Whether it's generating split-screen brainrot videos wi...

Security Scan

The skill is internally consistent with a cloud video-rendering integration: it only asks for a single service token (NEMO_TOKEN), describes API usage to upload/edit/export videos, and has no install step or unrelated credential requests.

Purpose & Capability

Name/description match the runtime instructions: the SKILL.md describes uploading clips, creating sessions, sending edits, and calling a rendering API at mega-api-prod.nemovideo.ai. Requiring a single NEMO_TOKEN credential is appropriate for this backend service.

Instruction Scope

Instructions are focused on the stated purpose (session creation, SSE chat, uploads, export polling). They expect the agent to accept user video files and call the listed endpoints. Note: the skill asks the agent to detect install path (to set X-Skill-Platform header) and the YAML frontmatter includes a configPaths entry (~/.config/nemovideo/), which implies the platform or agent may check a local config path — this is not strictly necessary for basic upload/render functionality but is explained as used for attribution headers.

Install Mechanism

No install spec and no code files — instruction-only. This minimizes disk/write risk; nothing is downloaded or executed by the skill itself.

Credentials

The skill requests exactly one credential (NEMO_TOKEN) and describes obtaining an anonymous token if none is present. This is proportional for a cloud rendering service. Consider that if you supply a personal NEMO_TOKEN it may consume your account's credits; anonymous tokens are short-lived and limited.

Persistence & Privilege

always is false and the skill does not declare persistent system-wide changes. The only persistence implied is use of session tokens with the remote service. The only minor privilege-like behavior is detection of install path and a referenced config path in the frontmatter, which could cause local path checks but not obvious system modification.

Assessment

This skill appears to do what it says: it uploads clips to a cloud renderer and returns download URLs. Before installing/providing credentials, consider: (1) don't give a personal NEMO_TOKEN unless you trust the service—any job will use that token and may consume your credits, (2) uploading videos sends your media to mega-api-prod.nemovideo.ai (check privacy/terms before sending sensitive content), and (3) the SKILL.md frontmatter references a local config path (~/.config/nemovideo/) and install-path detection; if you are uncomfortable with the agent probing local paths, do not install or ensure your platform does not expose those paths. If you want higher assurance, ask the skill author for a homepage, documentation, or the official service domain ownership before use.

Getting Started

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

Try saying:

• "create my video clips"
• "export 1080p MP4"
• "add subway surfers gameplay, split-screen chaos,"

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.

Brainrot Video Maker Free — Create and Export Brainrot Videos

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

Here's a typical use: you send a a 30-second gameplay or meme clip, ask for add subway surfers gameplay, split-screen chaos, captions, and background music to make a brainrot video, 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 — shorter source clips under 60 seconds generate the most shareable brainrot output.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

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

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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)

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add subway surfers gameplay, split-screen chaos, captions, and background music to make a brainrot video" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across TikTok, YouTube Shorts, and Instagram Reels.

Common Workflows

Quick edit: Upload → "add subway surfers gameplay, split-screen chaos, captions, and background music to make a brainrot video" → 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.