Ai Video Maker Gratis

create images or clips into ready-to-share videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. small business owners and social media cr...

Security Scan

The skill mostly matches an AI video-exporter but contains inconsistencies (undeclared local config/paths and filesystem probing) and asks the agent to upload user files to an external API owned by an unknown provider — proceed with caution.

Purpose & Capability

The skill's stated purpose (create/export videos) aligns with its runtime instructions and required credential (NEMO_TOKEN). However the SKILL.md metadata references a local config path (~/.config/nemovideo/) and logic to detect install paths (~/.clawhub/, ~/.cursor/skills/) that are not reflected in the registry's declared requirements. Reading those local paths is not necessary to perform basic video rendering and is an unexplained extra capability.

Instruction Scope

Instructions require the agent to read the NEMO_TOKEN env var (declared) and otherwise to obtain an anonymous token from an external API (expected). But the guidance also instructs detecting the agent's install platform by inspecting local install paths and to include an attribution header derived from that detection. That implies filesystem access beyond the skill's core purpose. The skill also routes user files to an external endpoint (the render service) — expected — but uploading user content to a third-party service is a privacy risk and should be explicit to users.

Install Mechanism

This is an instruction-only skill with no install spec or code to write to disk, which is the lower-risk option for installation.

Credentials

Only one credential (NEMO_TOKEN) is declared and used, which is proportional for a remote API. However the SKILL.md metadata references a config directory (~/.config/nemovideo/) that could contain additional secrets/configs — the registry did not declare that path. That mismatch is unexplained and could broaden the skill's access if the agent follows it.

Persistence & Privilege

The skill is not forced-always; it is user-invocable and allows autonomous invocation (the platform default). It does not request elevated persistent presence or modify other skills in the manifest.

What to consider before installing

Things to consider before installing/using: - Source trust: the skill has no homepage and an unknown owner; verify the provider (nemovideo.ai) independently before sending files or credentials. - Token handling: the skill requires NEMO_TOKEN. If you don't want to provide a permanent token, use the anonymous-token flow but be aware that the token is stored in memory/environment for requests and grants upload access. - Local filesystem access: SKILL.md suggests detecting install paths (~/.clawhub, ~/.cursor/skills) and references ~/.config/nemovideo/. Ask whether the agent will actually read those directories — this is not necessary for basic video rendering and may expose local metadata. - Privacy of uploads: videos/images/audio are uploaded to an external API (mega-api-prod.nemovideo.ai). Do not upload sensitive or confidential media unless you trust the service and understand retention policies. - Verify headers and attribution: the skill auto-sends attribution headers derived from your environment/install path; if this leaks identifying info you may want to block or sanitize them. - If you need higher assurance: request the skill author/publisher info or an official homepage/API docs, or run the skill in an isolated/sandboxed environment and inspect network traffic. If the author is unknown, prefer the ephemeral anonymous token flow and avoid uploading sensitive files. Additional info that would change this assessment: an official homepage or publisher identity, clear statement about whether the skill reads ~/.config and install paths, and independent confirmation that nemovideo.ai is a reputable provider with clear data retention/privacy policies.

Getting Started

Got images or clips to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "create five product photos and a logo file into a 1080p MP4"
• "create a 30-second promotional video with music and text overlays"
• "generating polished videos from images or clips without paid software for small business owners and social media creators"

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.

AI Video Maker Gratis — Create and Export Free Videos

Drop your images or clips 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 five product photos and a logo file, ask for create a 30-second promotional video with music and text overlays, 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 — using fewer than 10 images keeps render times under a minute.

Matching Input to Actions

User prompts referencing ai video maker gratis, 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.

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry 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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a 30-second promotional video with music and 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 all platforms.

Common Workflows

Quick edit: Upload → "create a 30-second promotional video with music and text overlays" → 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.