Video Maker For Business Free

Turn three product photos and a logo file into 1080p polished promo videos just by typing what you need. Whether it's creating promotional videos from produc...

Security Scan

The skill's behavior mostly matches a cloud video-rendering service, but there are inconsistencies between the registry metadata and the runtime instructions and a few details you should confirm before installing or giving it access to files.

Purpose & Capability

Name and description match the instructions: the skill uploads media to a cloud rendering API and returns download URLs. Requesting a single service token (NEMO_TOKEN) is coherent. However, the registry metadata earlier listed no config paths while the SKILL.md frontmatter references ~/.config/nemovideo/ — this metadata mismatch should be resolved.

Instruction Scope

The SKILL.md instructs the agent to generate anonymous tokens, create sessions, upload user files, stream SSE responses, poll render status, and re-auth when tokens expire — all expected for a cloud video service. But it contradicts the registry's 'required env vars' behavior: the instructions explicitly implement anonymous-token generation when NEMO_TOKEN is absent, yet the registry claims NEMO_TOKEN is required. Also the instructions require adding custom attribution headers on every request; confirm this is safe and the headers do not leak sensitive local metadata. There is no instruction to read unrelated local files or other env vars.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk. The skill does network calls to an external API, which is expected for this functionality.

Credentials

Only one credential is declared (NEMO_TOKEN), which fits a cloud API. But SKILL.md provides a flow to obtain an anonymous token if NEMO_TOKEN isn't set, making the registry's 'required' designation potentially inaccurate. The token grants upload and rendering capabilities for user media — reasonable for the stated purpose but potentially sensitive depending on what you upload.

Persistence & Privilege

The skill is not marked always:true and is user-invocable. It asks the agent to save a session_id and to use/store a bearer token; this is normal for session-based cloud APIs. No other system-wide modifications or persistent privileges are requested.

What to consider before installing

This skill appears to implement a legitimate cloud video-rendering workflow, but there are some inconsistencies and privacy considerations to check before installing: - Confirm the provider: the runtime endpoints use mega-api-prod.nemovideo.ai but the skill has no listed homepage or source; verify the service's identity and reputation before giving it tokens or uploading business/PII images. - Check the token behavior: the registry marks NEMO_TOKEN as required, but SKILL.md documents an anonymous-token flow. Ask whether the platform will force you to set NEMO_TOKEN or whether the skill will create short-lived anonymous tokens automatically. Know where tokens/session IDs will be stored and how long they are valid. - Review attribution headers: the skill requires adding X-Skill-Source/Version/Platform on every request. Confirm these headers are acceptable for your environment and do not leak local installation paths or other sensitive metadata. - Limit sensitive uploads: because the token allows uploading media to a third-party rendering service, avoid uploading images/videos containing sensitive personal data, credentials, or proprietary content unless you trust the provider and their retention policy. - Resolve metadata mismatches: ask the skill author/registry to fix inconsistencies between registry metadata (no configPaths) and SKILL.md frontmatter (references ~/.config/nemovideo/), and to clarify required vs optional environment variables. If you cannot verify the provider or these points, treat the skill cautiously or test it first with non-sensitive sample media.

Getting Started

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

Try saying:

• "create my images or clips"
• "export 1080p MP4"
• "create a 30-second promo video with"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Maker for Business Free — Create and Export Business 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 three product photos and a logo file, ask for create a 30-second promo video with text overlays and background music for my small business, 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 3-5 images keeps the video tight and processes faster than longer clip sequences.

Matching Input to Actions

User prompts referencing video maker for business 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.

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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-maker-for-business-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

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

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

Common Workflows

Quick edit: Upload → "create a 30-second promo video with text overlays and background music for my small business" → 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 "create a 30-second promo video with text overlays and background music for my small business" — 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 media and email platforms.