Ai Video Generator Free Girl

Get AI-generated video clips ready to post, without touching a single slider. Upload your text prompts or images (JPG, PNG, MP4, MOV, up to 200MB), say somet...

Security Scan

The skill's runtime instructions generally match a cloud video-generation purpose, but there are metadata inconsistencies (an undeclared config path) and behaviors (automatic token acquisition, file uploads to an external API) that you should review before installing.

Purpose & Capability

The skill claims to generate AI videos and requires a NEMO_TOKEN, which is proportional to that purpose. However the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that is not reflected in the registry 'Required config paths' field — this mismatch is unexplained and could indicate the skill expects to read local configuration that wasn't declared.

Instruction Scope

Instructions are primarily API calls to a remote backend (session creation, SSE-based message sending, file upload, render polling). They instruct uploading user-supplied files (multipart local paths or URLs) and reading an environment var (NEMO_TOKEN). There is no explicit instruction to read arbitrary system files or other credentials, but the doc asks to 'auto-detect' platform from install path and references a local config path in metadata — both could require filesystem access if implemented. The skill also describes creating an anonymous token from the backend if NEMO_TOKEN is absent, which lets it operate without a pre-provisioned key.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — lowest install risk. Nothing is written to disk by an installer here; runtime behavior depends on network requests.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv), which is appropriate for calling the described API. That said, the skill can obtain an anonymous NEMO_TOKEN itself via the auth endpoint, so requiring the env var may be optional. The presence of a declared config path in the frontmatter (but not in the registry) is disproportionate unless the skill truly needs to read local nemovideo config; this should be clarified.

Persistence & Privilege

always:false and no install actions mean the skill does not request permanent platform-wide presence. Nothing in the SKILL.md attempts to modify other skills or system settings. Be aware autonomous invocation is allowed by default (normal), which would let the agent call these APIs without repeated prompts if granted.

What to consider before installing

Things to consider before installing: - Confirm the backend domain (mega-api-prod.nemovideo.ai) is a legitimate service you trust. This skill will upload any images/video you provide to that remote API. - Ask the author to explain the config-path discrepancy: SKILL.md metadata mentions ~/.config/nemovideo/ but the registry did not declare any required config paths. Ask whether the skill will read or write files there. - Decide whether you are comfortable with the skill creating an anonymous token itself (the skill can POST to an auth endpoint and obtain a short-lived NEMO_TOKEN), and understand that doing so allows the service to track usage tied to that token. - Because uploads contain images/videos of people, check the service's privacy, retention, and acceptable-use policies before sending sensitive content (especially minors or identifying information). - If you need stronger assurances, ask for (or audit) an installation spec or code that shows exactly what filesystem or network calls the skill makes; without code, the SKILL.md is the only runtime spec and you should trust it only if the provider is known and reputable.

Getting Started

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

Try saying:

• "generate a photo of a girl walking in a park into a 1080p MP4"
• "generate a short video of a girl dancing in a studio with upbeat music"
• "generating free AI videos featuring female subjects from images or text prompts for TikTok creators"

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.

AI Video Generator Free Girl — Generate AI Girl Videos Free

Drop your text prompts or images 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 photo of a girl walking in a park, ask for generate a short video of a girl dancing in a studio with upbeat music, 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 text prompts with clear descriptions produce more accurate results.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-video-generator-free-girl
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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 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 "generate a short video of a girl dancing in a studio with upbeat music" — concrete instructions get better results.

Max file size is 200MB. Stick to JPG, PNG, MP4, MOV for the smoothest experience.

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "generate a short video of a girl dancing in a studio with upbeat music" → 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.