Ai Video Generator Free Hugging

generate text prompts or images into AI generated clips with this skill. Works with MP4, MOV, WebM, GIF files up to 200MB. content creators use it for genera...

Security Scan

The skill's requirements and runtime instructions are coherent with an AI video-generation integration: it only needs a NEMO_TOKEN (which it can obtain anonymously), communicates with a specific remote API, and asks to upload user files for rendering.

Purpose & Capability

Name/description (AI video generator) match the requested credential (NEMO_TOKEN) and the API endpoints described in SKILL.md. Minor inconsistency: the registry metadata earlier reported no required config paths, but the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/). This appears to be for saving session/token data and is proportionate to the skill's purpose.

Instruction Scope

The SKILL.md instructs the agent to obtain or use NEMO_TOKEN, create a session, upload user-supplied media (local path or URL), stream SSE for generation, and poll for render completion. All referenced files, endpoints, and headers are in scope for a cloud video-rendering workflow. It does instruct detection of the install path to set X-Skill-Platform header (reading known install locations), which is slightly beyond core functionality but not excessive. The instructions explicitly warn not to print tokens/raw JSON.

Install Mechanism

Instruction-only skill with no install steps or bundled code; nothing is written to disk by an installer. This is the lowest-risk install posture.

Credentials

Only one credential is declared (NEMO_TOKEN) and it is the primary credential for communicating with the service. The skill can also obtain an anonymous token via the service's /api/auth/anonymous-token endpoint, reducing need for pre-provisioned secrets. No unrelated secrets or broad system credentials are requested.

Persistence & Privilege

The skill is not marked always:true and does not request privileged or system-wide configuration changes. It instructs storing session_id and using a token (typical for API clients). Autonomous invocation is allowed but is the platform default and not in itself a red flag here.

Assessment

This skill appears to do what it says: it talks to a remote nemo-video API, will upload media you provide (up to ~200MB), and will generate or use a NEMO_TOKEN for authenticated calls. Before installing, consider: (1) the skill will send your uploaded files to https://mega-api-prod.nemovideo.ai — avoid uploading sensitive or private files you don't want sent to an external service; (2) the skill can create an anonymous token on your behalf (7‑day expiry) or use an existing NEMO_TOKEN you set — prefer using an account token only if you trust the service; (3) the SKILL.md reads its install path to set an attribution header (minor metadata leak of environment), and SKILL.md lists a config path (~/.config/nemovideo/) for storing session state — if you want to avoid persisted tokens, watch where session data is stored. If you don't recognize the nemovideo.ai domain or can't verify it, do not install or use with sensitive content.

Getting Started

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

Try saying:

• "generate my text prompts or images"
• "export 1080p MP4"
• "generate a free video clip of"

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.

AI Video Generator Free Hugging — Generate free AI video clips

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

Say you have a short text description of a hugging scene between two people and want to generate a free video clip of two people hugging using AI — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter and more specific text prompts produce more accurate video results.

Matching Input to Actions

User prompts referencing ai video generator free hugging, 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 ai-video-generator-free-hugging, 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 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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a free video clip of two people hugging using AI" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "generate a free video clip of two people hugging using AI" → 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.