Meme Video Generator Free

Get shareable meme videos ready to post, without touching a single slider. Upload your images or clips (MP4, MOV, JPG, PNG, up to 200MB), say something like...

Security Scan

The skill generally matches its stated purpose (remote meme-video rendering) but contains a few inconsistencies and behaviors you should review before installing — notably a metadata mismatch about config paths, file-system inspection for attribution, and automatic anonymous-token acquisition from an external domain.

Purpose & Capability

The skill name/description align with the runtime instructions: it uploads media, creates a session, submits render jobs, and returns MP4s. Requesting a single service token (NEMO_TOKEN) is appropriate for this API-backed video rendering service.

Instruction Scope

Instructions are explicit about network calls (session creation, SSE, uploads, render requests) and about including attribution headers. It also instructs reading the skill's YAML frontmatter and detecting an install path (~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform — this requires filesystem access and is broader than merely calling the remote API. The skill will generate an anonymous token if no NEMO_TOKEN is present, which implies automatic network authentication behavior.

Install Mechanism

There is no install spec and no code files — instruction-only. That minimizes disk-write risk; nothing is downloaded or extracted during install.

Credentials

The declared primary env var (NEMO_TOKEN) is consistent with the service. However SKILL.md frontmatter declares a configPaths entry (~/.config/nemovideo/) while registry metadata lists no required config paths — this metadata mismatch is inconsistent. Also the skill will POST to an external anonymous-token endpoint to obtain a short-lived token if none is supplied, which may create network activity and temporary credentials outside the user's control.

Persistence & Privilege

always is false and the skill does not request persistent installation or cross-skill config changes. It does create ephemeral sessions/tokens for rendering, which is expected for a remote-rendering service. No elevated platform privileges are requested.

What to consider before installing

This skill appears to do what it says (server-side meme video rendering), but review these points before installing: 1) NEMO_TOKEN: provide only a token you trust — it grants the skill access to your account and rendering/credit usage. 2) Anonymous token fallback: if you don't supply NEMO_TOKEN the skill will POST to https://mega-api-prod.nemovideo.ai to obtain a short-lived token — verify you are comfortable with uploads and generated credentials being handled by that service. 3) Filesystem reads: the skill will read its own SKILL.md frontmatter and inspect likely install paths to set X-Skill-Platform headers — make sure you are OK with that limited file access. 4) Metadata mismatch: the frontmatter lists a config path (~/.config/nemovideo/) but registry metadata declared none — ask the publisher to clarify whether the skill will read or write that directory. 5) Privacy: uploads are sent to a third-party render service; do not upload sensitive content unless you have read and accepted that service's privacy/rate/credit policies. If you need higher assurance, ask the publisher for a documented privacy/security policy or test with throwaway data and an account with limited privileges.

Getting Started

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

Try saying:

• "generate my images or clips"
• "export 1080p MP4"
• "turn this image into a meme"

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.

Meme Video Generator Free — Create and Export Meme Videos

Send me your images or clips and describe the result you want. The AI meme video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a reaction image and a short 5-second clip, type "turn this image into a meme video with Impact font captions and a trending sound", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: square or vertical crops work best for meme formats shared on social media.

Matching Input to Actions

User prompts referencing meme video generator 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.

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: meme-video-generator-free
• 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

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.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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)

Common Workflows

Quick edit: Upload → "turn this image into a meme video with Impact font captions and a trending sound" → Download MP4. Takes 20-40 seconds 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 "turn this image into a meme video with Impact font captions and a trending sound" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across all social platforms.