Ai Video Maker Free Hindi

Turn a 200-word Hindi product description into 1080p Hindi AI videos just by typing what you need. Whether it's creating Hindi language videos from text usin...

Security Scan

The skill's requirements and runtime instructions are consistent with an AI video creation service: it calls an external nemo video API, uses a single service token (NEMO_TOKEN) or anonymous tokens, and has no install steps or surprising local privileges.

Purpose & Capability

The name/description map to the runtime behavior: the skill talks to mega-api-prod.nemovideo.ai and uses an API token to create/upload/render videos. Requiring NEMO_TOKEN is appropriate. One minor mismatch: the metadata lists a config path (~/.config/nemovideo/) but the SKILL.md does not actually instruct reading files from that path; this is plausible but unexplained.

Instruction Scope

SKILL.md is explicit about network calls, session creation, SSE streaming, uploads, and exports — all expected for a cloud video rendering workflow. The instructions do not ask the agent to read unrelated system files or other credentials. They do mention detecting install path to set an X-Skill-Platform header (probing known skill dirs), which could require checking typical skill locations but is limited in scope.

Install Mechanism

No install steps or downloaded code are present (instruction-only). This minimizes filesystem/persistence risk.

Credentials

Only one credential (NEMO_TOKEN) is declared as required and is used directly by the API calls, which is proportionate. The metadata also lists a config path (~/.config/nemovideo/) that isn't referenced elsewhere; it's unclear why that path is declared as required.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and has no install-time persistence. Autonomous invocation is allowed (platform default) but is not combined with other high-risk privileges.

Assessment

This skill appears to do what it says: it will call an external nemo video API, use a single service token (NEMO_TOKEN) if provided, or obtain a short-lived anonymous token, and upload any files you provide to that service for rendering. Before installing or providing a persistent NEMO_TOKEN: (1) verify the API host (mega-api-prod.nemovideo.ai) and the service’s privacy policy; (2) avoid giving a long-lived or highly-privileged token if you’re unsure — prefer anonymous tokens or scoped credentials; (3) do not upload sensitive personal or secret files (the service will receive them); (4) note the small unexplained metadata entry for ~/.config/nemovideo/ — ask the publisher why that config path is declared. Because the skill is instruction-only (no install), local risk is lower, but network/data-exfiltration risks depend entirely on whether you trust the external service.

Getting Started

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

Try saying:

• "create a 200-word Hindi product description into a 1080p MP4"
• "create a Hindi explainer video from this script with voiceover and subtitles"
• "creating Hindi language videos from text using AI for Hindi content creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

AI Video Maker Free Hindi — Create Hindi Videos with AI

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

Say you have a 200-word Hindi product description and want to create a Hindi explainer video from this script with voiceover and subtitles — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 150 words generate faster and more accurate Hindi voiceovers.

Matching Input to Actions

User prompts referencing ai video maker free hindi, 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-maker-free-hindi, 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).

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.

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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)

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 "create a Hindi explainer video from this script with voiceover and subtitles" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across WhatsApp, YouTube, and Instagram.

Common Workflows

Quick edit: Upload → "create a Hindi explainer video from this script with voiceover and subtitles" → 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.