Free Maker Generation

Turn a short text description of a product demo scene into 1080p ready-to-share videos just by typing what you need. Whether it's generating videos from text...

Security Scan

The skill's declared requirements and API calls match a cloud video-generation service, but its runtime instructions include automatic anonymous auth (network calls) and guidance to hide tokens from users and to probe install paths — behaviors that warrant caution before installing from an unknown source.

Purpose & Capability

Name/description (AI video generation) align with required env var NEMO_TOKEN and the documented API endpoints for uploading, rendering, and exporting videos.

Instruction Scope

SKILL.md instructs the agent to automatically obtain an anonymous token (POST to an external API) and create/store sessions on first use, to upload user files/URLs to the external service, and to suppress showing raw API responses/tokens to the user. It also instructs deriving a header from the agent install path (implies probing filesystem). Automatic outbound network activity and hiding tokens are privacy-sensitive and expand scope beyond simply 'generate when requested.'

Install Mechanism

Instruction-only skill with no install spec or code to write to disk — lowest install risk. All external behavior is performed via the described API endpoints at runtime.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is appropriate for a cloud API. However the skill will obtain an anonymous token itself if NEMO_TOKEN is unset and will store/use it for 7-day access — this automatic credential creation may occur without explicit user consent.

Persistence & Privilege

The skill is not always-enabled and is user-invocable. Still, it instructs an automatic 'first-time connection' (network auth and session creation) when opened, which could run without explicit user confirmation if the agent invokes the skill autonomously.

What to consider before installing

This skill talks to an external API (mega-api-prod.nemovideo.ai) to upload files and render videos and will automatically request an anonymous API token if none is provided. Before installing: 1) Confirm you trust the unknown source or obtain the skill from a verifiable homepage/owner. 2) Understand that files you upload will be sent to the external service and that the skill will make outbound network requests automatically on first use. 3) Consider setting your own NEMO_TOKEN (if you have an account) instead of allowing the skill to create one, and be aware the skill instructs hiding token values from users. 4) If you need to audit activity, check whether the agent will prompt before uploading and whether it records session IDs or logs responses. If uncertain, prefer manual use of the service's official API/website rather than installing an unverified skill.

Getting Started

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

Try saying:

• "generate my text prompts or clips"
• "export 1080p MP4"
• "generate a 30-second promotional video from"

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.

Free Maker Generation — Generate Videos Free with AI

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

Say you have a short text description of a product demo scene and want to generate a 30-second promotional video from my script for free — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter prompts with clear scene descriptions produce more accurate results.

Matching Input to Actions

User prompts referencing free maker generation, 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 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.

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

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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.

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)

Common Workflows

Quick edit: Upload → "generate a 30-second promotional video from my script for free" → 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 "generate a 30-second promotional video from my script for free" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, WebM, AVI for the smoothest experience.

Export as MP4 for widest compatibility.