Ai Video Generator Free Inappropriate

generate text prompts into generated video clips with this skill. Works with MP4, MOV, WebM, AVI files up to 500MB. content creators use it for generating vi...

Security Scan

The skill's requested variables and runtime instructions match its stated purpose (AI video generation); nothing obviously unrelated is requested, but some privacy and provenance cautions apply.

Purpose & Capability

Name/description match the actions in SKILL.md: it calls a third-party video-generation API, accepts uploads, creates sessions, and uses a single API token (NEMO_TOKEN). Requested env var and config path (~/.config/nemovideo/) are plausible for this purpose.

Instruction Scope

Instructions stick to video-generation workflows (auth, session creation, upload, SSE, render/polling). Two minor scope items to note: (1) headers expect an X-Skill-Platform value derived from the agent's install path (this implies the agent may inspect local install paths), and (2) uploads use multipart file paths, so the agent will transmit user files to the external API when asked. Both are explainable by the skill's function but have privacy implications.

Install Mechanism

No install spec or code files — instruction-only. Nothing is downloaded or written by an installer in the manifest.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportionate. The metadata also lists a config path for persistence; storing session_id there is reasonable but means local files will contain session info. Treat NEMO_TOKEN as sensitive and rotate/revoke if shared widely.

Persistence & Privilege

Skill is not always-enabled and does not request elevated system privileges. It expects to store session data in its own ~/.config/nemovideo/ area, which is normal for session persistence.

Assessment

This skill is internally consistent for a cloud-based AI video generator: it needs one API token (NEMO_TOKEN), will contact https://mega-api-prod.nemovideo.ai, and will upload any media you ask it to process. Before installing, consider: (1) provenance — the skill has no homepage or source URL, so you can't easily verify the backend operator; (2) privacy — it may read install paths to set X-Skill-Platform and will store session data under ~/.config/nemovideo/; avoid uploading sensitive files; (3) credential safety — use an ephemeral or limited-scope token if possible and revoke it after use; (4) content policy — the skill advertises "relaxed content filters," which could enable generation of inappropriate material. If you require stronger guarantees about who runs the backend or what data is retained, do not install until you can verify the service operator or review their privacy/terms.

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 30-second video from my"

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 Inappropriate — Generate Videos From Text Prompts

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 scene or concept, ask for generate a 30-second video from my script without content restrictions, 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 produce more accurate video results.

Matching Input to Actions

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

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

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.

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 30-second video from my script without content restrictions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "generate a 30-second video from my script without content restrictions" → 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.