Video Maker Free Without Login

create video clips or images into ready-to-share videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. casual creators and small business...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video-rendering integration (it needs a NEMO_TOKEN and uploads media to nemovideo.ai), but there are minor metadata inconsistencies and expected privacy/network implications you should be aware of.

Purpose & Capability

The skill name/description (create/export videos) matches the actions in SKILL.md (upload media, start render, poll for result). Requesting a service token (NEMO_TOKEN) is appropriate. One inconsistency: the registry metadata shown above lists no required config paths, but the SKILL.md frontmatter declares a config path (~/.config/nemovideo/). This mismatch should be clarified.

Instruction Scope

Instructions focus on communicating with mega-api-prod.nemovideo.ai endpoints (auth, session, upload, SSE, render). They explicitly check environment for NEMO_TOKEN and, if missing, obtain an anonymous token by POSTing to the service — which is coherent for an anonymous usage mode. The skill also instructs reading its own YAML frontmatter and detecting install path for attribution headers (requires reading local file paths). These file reads are limited in scope but should be noted. The instructions direct uploads of user media to an external service — expected for cloud rendering but important for privacy.

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. Lowest-risk install posture.

Credentials

The only required credential is NEMO_TOKEN (declared primaryEnv) which is proportionate for a cloud rendering service. The SKILL.md also contains logic to obtain an anonymous NEMO_TOKEN if none provided. No unrelated credentials are requested. Users should understand that the token authorizes uploads and actions on the remote service, and that user media will be transmitted to that third party.

Persistence & Privilege

The skill does not request always:true, has no install script, and does not ask to modify other skills or system-wide settings. It will create ephemeral sessions (session_id) and may leave render jobs running on the provider side if the client disconnects — expected for this use case.

Assessment

This skill appears to do what it says: it uploads your media to a nemovideo.ai backend, renders video on cloud GPUs, and returns a downloadable MP4. Before installing/using it: 1) Confirm you are comfortable with your files being sent to https://mega-api-prod.nemovideo.ai (privacy/PII risk). 2) Prefer providing your own NEMO_TOKEN if you have one instead of allowing the skill to request an anonymous token on your behalf. 3) Note the small metadata inconsistency (SKILL.md lists a config path while registry metadata did not) — ask the provider to clarify what local files, if any, will be read. 4) Verify the service origin (no homepage or known owner listed) and test with non-sensitive media first. If you need higher assurance, request an explicit privacy/security statement or a verifiable source/repository for the skill.

Getting Started

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

Try saying:

• "create three product photos and a background music file into a 1080p MP4"
• "combine these clips into a 30-second promo video with text overlays"
• "creating short videos from clips or images without signing up for casual creators and small business owners"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Video Maker Free Without Login — Create and Export Videos Instantly

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

Here's a typical use: you send a three product photos and a background music file, ask for combine these clips into a 30-second promo video with text overlays, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 60 seconds process faster and export without delay.

Matching Input to Actions

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

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: video-maker-free-without-login
• 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 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "combine these clips into a 30-second promo video with text overlays" — 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 and devices.

Common Workflows

Quick edit: Upload → "combine these clips into a 30-second promo video with text overlays" → 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.