Video Generator Free No Login

generate text or images into ready-to-share videos with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. casual creators and marketers use it for...

Security Scan

The skill's requirements and runtime instructions mostly match a cloud video-generation service, but there are inconsistencies and a few scope-creep behaviors (reading install paths, local config path reference, and automatic anonymous-token acquisition) that warrant caution before installing.

Purpose & Capability

The skill claims to generate videos via a cloud API and requires a single credential (NEMO_TOKEN) — that aligns with its purpose. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths, which is an internal inconsistency. Also the instructions require adding attribution headers and detecting an install path on the user's filesystem to populate X-Skill-Platform, which goes beyond a minimal API client.

Instruction Scope

Instructions direct the agent to upload user files and messages to https://mega-api-prod.nemovideo.ai and to poll/export results — expected for this service. Concerning points: (1) the agent is told to detect the install path (checking ~/.clawhub/ or ~/.cursor/skills/) which requires reading the user's filesystem beyond the skill file; (2) it reads this file's YAML frontmatter at runtime; (3) it will create anonymous tokens by POSTing a generated UUID if no NEMO_TOKEN is present. The skill also instructs the agent to “keep technical details out of the chat,” which could hide network activity from the user. These broaden what the agent will access or transmit compared to a minimal client.

Install Mechanism

No install spec and no code files — instruction-only skill — so nothing is written to disk by an installer. This is the lowest-risk install mechanism.

Credentials

Only NEMO_TOKEN is declared as required, which is proportionate for a cloud API. However, the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) that was not listed in the registry metadata; the runtime instructions also ask the agent to inspect user home paths to determine platform, which implies filesystem access not declared in requires.env. The anonymous-token fallback reduces the need for a pre-provided secret, but it still causes the agent to send identifying info (UUID) to the third-party endpoint.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request permanent presence or elevated platform-wide privileges and does not modify other skills' configurations in these instructions.

What to consider before installing

This skill appears to be a straight client for a cloud video rendering API and mostly behaves as expected, but review these points before installing: - Network and data exfiltration: using the skill will upload your files (videos, images, audio, and text) to https://mega-api-prod.nemovideo.ai. Do not upload sensitive or confidential material unless you trust that service. - Token handling: it will use NEMO_TOKEN if provided, or acquire a temporary anonymous token by POSTing a generated UUID. If you do not want automatic network auth, do not install or remove network access. - Filesystem checks: the skill instructs the agent to detect install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) and to read this file's YAML frontmatter — this requires reading parts of your home directory. Ask the developer why this is needed and request that filesystem reads be limited or documented. - Metadata headers: every API call includes X-Skill-Source, X-Skill-Version, and X-Skill-Platform. These can reveal which skill/version and (via install-path detection) possibly which client you use. If you are concerned about metadata leakage, ask for an option to disable or minimize these headers. Because of the filesystem-inspection instruction and the metadata/anonymous-token behaviors (and the inconsistency about config paths), treat this skill as suspicious until you can verify the backend domain and get clarification from the publisher. If you proceed, avoid uploading sensitive content and prefer providing your own trusted NEMO_TOKEN rather than relying on the anonymous-token flow.

Getting Started

Send me your text or images and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "generate a short text prompt describing a product demo into a 1080p MP4"
• "create a 30-second video from my product description without signing up"
• "generating short videos from text or images instantly without an account for casual creators and marketers"

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 Generator Free No Login — Generate Videos Instantly, No Account

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

Say you have a short text prompt describing a product demo and want to create a 30-second video from my product description without signing up — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter prompts with clear instructions produce more accurate results faster.

Matching Input to Actions

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

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

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

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.

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 "create a 30-second video from my product description without signing up" — 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 social platforms.

Common Workflows

Quick edit: Upload → "create a 30-second video from my product description without signing up" → Download MP4. Takes 30-60 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.