Ai Video Creator From Text

Cloud-based ai-video-creator-from-text tool that handles generating videos from written content or scripts. Upload TXT, DOCX, PDF, copied text files (up to 5...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-generation service (it needs a service token and uploads user files), but there are small metadata inconsistencies and privacy considerations you should review before using it.

Purpose & Capability

The skill claims to be a cloud AI video generator and only requests a single service credential (NEMO_TOKEN), which is coherent. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata declared no required config paths — this mismatch is an inconsistency to verify.

Instruction Scope

The SKILL.md stays within the expected scope: it instructs how to obtain/use a session token, create sessions, upload files, stream SSE events, and export renders. It explicitly requires sending user text and uploaded files to the external nemovideo.ai API (expected for this purpose). It also instructs storing session/token values for subsequent requests and not showing raw tokens to users.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing is written to disk by an installer — the lowest-risk install model.

Credentials

Only one credential (NEMO_TOKEN) is declared as required and is the primary credential — appropriate for a cloud API. The SKILL.md, however, describes an automatic anonymous-token acquisition flow that will generate and store a token if none is present; you should confirm where the token/session will be persisted (memory, env, or disk) and whether that storage location matches your security policy.

Persistence & Privilege

The skill does not request always:true, elevated privileges, or modifications to other skills. It will store session state/token for its own use (normal for API integrations).

Assessment

This skill appears internally consistent for a cloud video-generation tool, but take these precautions before installing or using it: - Understand that any text and uploaded files will be sent to an external service at mega-api-prod.nemovideo.ai; do not upload sensitive or proprietary content unless you trust the provider and have reviewed their policies. - The skill will use or obtain a NEMO_TOKEN. Confirm where that token and the session_id will be stored (in-memory vs. written to ~/.config/nemovideo/ or other files) and whether that storage aligns with your security requirements. - There is no homepage or known source listed — consider verifying the vendor (nemovideo.ai), looking for documentation or a privacy policy, and testing with non-sensitive data first. - Note the small metadata mismatch: the SKILL.md frontmatter references a config path but the registry metadata listed none; ask the publisher to clarify whether the skill will read/write ~/.config/nemovideo/ before installing. - If you need the agent to never contact external services for sensitive projects, do not enable this skill or ensure it is only invoked with explicit user consent.

Getting Started

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

Try saying:

• "create my text prompts"
• "export 1080p MP4"
• "turn this blog post intro into"

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 Video Creator from Text — Turn Text into Shareable Videos

Send me your text prompts 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 a 150-word product description, type "turn this blog post intro into a 30-second video with visuals and voiceover", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter, clearer text prompts produce more accurate visuals than long paragraphs.

Matching Input to Actions

User prompts referencing ai video creator from text, 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: ai-video-creator-from-text
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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.

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this blog post intro into a 30-second video with visuals and voiceover" — concrete instructions get better results.

Max file size is 500MB. Stick to TXT, DOCX, PDF, copied text for the smoothest experience.

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

Common Workflows

Quick edit: Upload → "turn this blog post intro into a 30-second video with visuals and voiceover" → 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.