Free Video Generation Like Grok

generate text prompts into AI generated videos with this skill. Works with MP4, MOV, WebM, GIF files up to 500MB. content creators use it for generating shor...

Security Scan

The skill's requirements and runtime instructions are broadly consistent with a cloud video-generation connector that uses a single service token, but there are a few small metadata/instruction mismatches and privacy considerations to review before installing.

Purpose & Capability

Name/description align with what the SKILL.md instructs: connecting to a nemo video backend, creating sessions, uploading media, streaming SSE, and exporting rendered MP4s. Requested primary credential (NEMO_TOKEN) is appropriate for that purpose. Minor incoherence: the registry metadata reported no required config paths, but the skill frontmatter and runtime instructions reference a config path (~/.config/nemovideo/) and require reading the SKILL.md frontmatter for X-Skill headers.

Instruction Scope

Instructions are focused on the video-generation workflow (token check, session creation, SSE messaging, upload, export, polling). Expected network calls are to the documented nemovideo API endpoints. Notable runtime actions: auto-requesting an anonymous token if NEMO_TOKEN is absent, reading the skill's YAML frontmatter and checking install paths to set X-Skill-Platform, and reading local files for uploads. These actions are explainable for this connector but warrant user awareness (network calls, file reads).

Install Mechanism

Instruction-only skill with no install spec and no binaries; nothing will be written to disk by an installer step. This is the lowest-risk install surface.

Credentials

The skill declares a single primary env var, NEMO_TOKEN, which is reasonable for authenticating to a single third-party service. The SKILL.md will attempt to obtain an anonymous NEMO_TOKEN via an API call if none is present — this behavior is reasonable for convenience but means network activity and issuance of short-lived credentials can occur without the user pre-providing a key. Also note the frontmatter's configPaths reference (~/.config/nemovideo/) which wasn't listed in the registry metadata.

Persistence & Privilege

always is false and the skill does not request persistent platform-wide privileges. The instructions do read local paths (to detect platform and read frontmatter) and may upload user-supplied files, but the skill does not request to modify other skills or agent-wide settings.

Assessment

This skill appears to do what it says: connect to a nemo video backend, accept text prompts or uploads, run cloud renders, and return download URLs. Before installing: 1) Consider trust — the skill talks to https://mega-api-prod.nemovideo.ai and may auto-obtain an anonymous token if you don't provide one, so there will be network calls and short-lived credentials issued. 2) The skill will read the skill frontmatter and check install paths (~/.clawhub, ~/.cursor/skills) to set headers — if you are concerned about local path reads, avoid installing or review what the agent can access. 3) Do not send sensitive data or secrets in prompts or uploads. 4) If you have an account, prefer providing your own NEMO_TOKEN rather than allowing anonymous token creation. 5) The registry metadata and SKILL.md disagree about config paths — if you need clarity, ask the publisher for a canonical manifest or a privacy/security policy for the backend before enabling the skill.

Getting Started

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

Try saying:

• "generate my text prompts"
• "export 1080p MP4"
• "generate a 15-second video clip of"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Free Video Generation Like Grok — Generate AI Videos From Text

Drop your text prompts in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short text description of a beach sunset scene, ask for generate a 15-second video clip of a futuristic city at night from a text prompt, 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 and more specific prompts tend to produce more accurate video results.

Matching Input to Actions

User prompts referencing free video generation like grok, 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: free-video-generation-like-grok
• 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.

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.

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.

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

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 → "generate a 15-second video clip of a futuristic city at night from a text prompt" → 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 15-second video clip of a futuristic city at night from a text prompt" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and devices.