Ai Video Generatore

Get generated MP4 videos ready to post, without touching a single slider. Upload your text or images (MP4, MOV, JPG, PNG, up to 500MB), say something like "g...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud video-generation integration: it asks for one service token, uses a documented set of API endpoints, and does not request unrelated credentials or install software.

Purpose & Capability

Name/description match the declared runtime actions: the SKILL.md describes uploading media, creating a session, streaming SSE edits, rendering exports, and uses a single service credential (NEMO_TOKEN). Requiring a token and upload capability is proportional to a cloud render service.

Instruction Scope

Instructions direct the agent to use NEMO_TOKEN (or obtain an anonymous token via the vendor's endpoint), create sessions, POST messages via SSE, and upload local files via multipart/form-data (files=@/path). These actions are expected for a video upload/workflow, but the skill also asks the agent to detect install path to set an X-Skill-Platform header and to include several custom headers on all requests — both trivial for functionality but worth noting since they imply the agent may probe its environment and send metadata with requests. The SKILL.md explicitly instructs not to print tokens or raw JSON.

Install Mechanism

No install spec or code is provided (instruction-only), so nothing will be written to disk by the skill itself. This is the lowest-risk install profile.

Credentials

Only one required environment variable (NEMO_TOKEN) is declared and used as the primary credential, which fits the stated purpose. The metadata also lists a config path (~/.config/nemovideo/), which is plausible for a client but not otherwise referenced in the instructions — benign but slightly unnecessary unless the agent will actually read that config.

Persistence & Privilege

The skill is not marked always:true and does not request persistent or elevated platform privileges. It instructs to create and hold a session_id for the current session, which is normal for this workflow.

Assessment

This skill appears to do what it says: it uploads your media and talks to a third-party API (mega-api-prod.nemovideo.ai) using a NEMO_TOKEN. Before installing, confirm you trust that service: any files you upload (images, video, audio, or text) and the generated session data will be sent to their servers. If you don't have a NEMO_TOKEN, the skill will request an anonymous token from the vendor (100 credits, 7-day expiry) which ties activity to that service. Consider using a dedicated account/token for this skill, avoid uploading sensitive/private material, and review or delete tokens/sessions from the vendor if you stop using the skill. If you want stronger assurance, ask the vendor for a privacy policy or inspect network requests through a trusted environment before sending real content.

Getting Started

Got text or images to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "generate a short product description text into a 1080p MP4"
• "generate a 30-second video from this text with background music and captions"
• "generating videos from text prompts or images for content creators, marketers"

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 Generatore — Generate Videos from Text or Images

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

Say you have a short product description text and want to generate a 30-second video from this text with background music and captions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter text prompts with clear instructions produce more accurate results.

Matching Input to Actions

User prompts referencing ai video generatore, 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.

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

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.

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.

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

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 30-second video from this text with background music and captions" → 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 video from this text with background music and captions" — 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.