Video Making Free Ai

Skip the learning curve of professional editing software. Describe what you want — turn these photos and audio into a 30-second promo video with transitions...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video-rendering service: it needs a NEMO_TOKEN (or will obtain an anonymous one), uploads user media to nemovideo.ai, and stores a session_id for rendering — nothing in the instructions suggests unrelated data access or hidden behaviors.

Purpose & Capability

Name/description, required env var (NEMO_TOKEN), and the API endpoints in SKILL.md all match a cloud video-processing workflow. Requiring NEMO_TOKEN is proportional and expected. The SKILL.md also offers to obtain an anonymous token if none is provided, which is coherent with providing a user-friendly onboarding flow.

Instruction Scope

Instructions stay within the video-service domain (mega-api-prod.nemovideo.ai) and only reference storing a session_id and sending/receiving render state, SSE, and uploads. Important user-impacting behavior: the skill will upload user media (up to 500MB each) to the external service and poll for render results. It also instructs to read the skill file's YAML frontmatter and detect install path to set attribution headers — that requires access to the skill file/agent install path but not unrelated system secrets. No instructions request unrelated system files or other credentials.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. There is nothing being downloaded or written by an installer step according to the manifest.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv). The skill is explicit that if NEMO_TOKEN is absent it will request an anonymous token from the service and use it for 7 days/100 credits. Metadata mentioning ~/.config/nemovideo/ and reading install paths is plausible for attribution but not strictly necessary — benign but worth noting. No other secrets are requested.

Persistence & Privilege

always:false and default autonomous invocation are normal. The skill stores a session_id for ongoing requests (expected for a session-based API) but does not request elevated system-wide privileges or modify other skills' configs.

Assessment

This skill appears to do what it says: it uploads your media to mega-api-prod.nemovideo.ai and uses a bearer token (NEMO_TOKEN) to render and return MP4s. Before installing or using it, consider: (1) privacy — any uploaded photos, video, or audio are sent to an external service; avoid sensitive content unless you trust the provider; (2) tokens — the skill can generate and store an anonymous token for you (valid ~7 days); know where tokens/session IDs are stored and how to revoke them; (3) provenance — the skill source is unknown (no homepage), so if you require stronger trust, verify the service domain and provider policies or avoid using confidential material; (4) network usage — large uploads may consume bandwidth and possibly incur costs. If you want a deeper check, ask for the exact storage location for session/tokens, the retention policy for uploaded media on the provider side, and proof of the provider's privacy/security practices.

Getting Started

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

Try saying:

• "create my video clips or images"
• "export 1080p MP4"
• "turn these photos and audio into"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Making Free AI — Create and Export AI Videos

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 five product photos and a voiceover MP3, ask for turn these photos and audio into a 30-second promo video with transitions, 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 process significantly faster.

Matching Input to Actions

User prompts referencing video making free ai, 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-making-free-ai
• 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.

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

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 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

Common Workflows

Quick edit: Upload → "turn these photos and audio into a 30-second promo video with transitions" → 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.

Tips and Tricks

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