Ai To Create Video

create text prompts or images into AI generated videos with this ai-to-create-video skill. Works with MP4, MOV, JPG, PNG files up to 500MB. marketers, conten...

Security Scan

The skill's functionality (uploading images/text to a remote video render service) generally matches its requirements, but there are small inconsistencies and privacy/ persistence implications you should understand before installing.

Purpose & Capability

Name/description align with required credential NEMO_TOKEN and the described remote rendering endpoints; requesting a single service token is proportionate. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata shown earlier lists no required config paths — this mismatch reduces confidence in metadata accuracy.

Instruction Scope

Instructions are focused on connecting to a remote render API, uploading media, reading SSE streams, and initiating export jobs — all consistent with video creation. They instruct the agent to auto-request an anonymous token if NEMO_TOKEN is absent and to 'store' the returned session_id/token for subsequent requests; storage location is not specified. There are no instructions to read unrelated system files or secrets, but implicit persistence (saving tokens/session ids) is required.

Install Mechanism

No install spec and no code files are present (instruction-only), so nothing is written to disk by an installer. This is the lowest-risk install mechanism.

Credentials

Only one environment credential (NEMO_TOKEN) is declared as the primary credential, which is appropriate for an API-based video service. The frontmatter also declares a config path (~/.config/nemovideo/), which would allow persistent storage of tokens/session state — this was not reflected in the registry's earlier 'Required config paths: none' listing, creating an inconsistency to resolve.

Persistence & Privilege

always:false and normal autonomous invocation are used (expected). The skill instructs the agent to obtain anonymous tokens and store session_id/token for later requests; that implies persistent state (potential writes to a config path). This behavior is sensible for a session-based API but should be disclosed to users and the storage location confirmed.

What to consider before installing

This skill appears to do what it claims (upload media and request server-side video renders), but check a few things before installing: 1) Metadata mismatch — SKILL.md claims a config path (~/.config/nemovideo/) but the registry listing showed none; ask the publisher where tokens/session IDs are stored and what exactly is written to disk. 2) The skill will upload your files to https://mega-api-prod.nemovideo.ai — confirm you trust that service and review its privacy/terms, since uploads may include sensitive images or audio. 3) If NEMO_TOKEN is not provided, the skill will auto-create an anonymous token and store it (100 free credits, 7-day lifetime) — if you prefer to control credentials, supply your own token instead. 4) The agent will make network requests and may persist session state; if you need isolation, consider using an account with limited privileges or avoid sending sensitive content. 5) Because the registry/frontmatter are inconsistent, ask the maintainer for a short, explicit privacy/storage statement and for clarification of the expected config file or path before enabling the skill. If you are comfortable with remote processing of your media and the service domain, the skill's requests are proportionate; if not, do not install.

Getting Started

Ready when you are. Drop your text prompts or images here or describe what you want to make.

Try saying:

• "create three product photos and a short text brief into a 1080p MP4"
• "turn these product images and description into a 30-second promotional video"
• "generating videos from images or text prompts for marketers, content creators, small business owners"

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.

AI to Create Video — Generate Videos from Images or Text

Send me your text prompts or images and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload three product photos and a short text brief, type "turn these product images and description into a 30-second promotional video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: adding a clear text description alongside your images gives the AI more context and improves the final result.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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	ai-to-create-video
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these product images and description into a 30-second promotional video" — 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 platforms and websites.

Common Workflows

Quick edit: Upload → "turn these product images and description into a 30-second promotional video" → 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.