Text To Video Ai Japanese

Turn a three-sentence Japanese product description into 1080p Japanese text videos just by typing what you need. Whether it's generating videos from Japanese...

Security Scan

The skill largely matches a text-to-video service but includes several incoherent or privacy-relevant instructions (filesystem/install-path probing, a configPath mismatch, and ambiguous header attribution) that you should review before installing or providing credentials.

Purpose & Capability

The declared purpose (convert short Japanese text into videos) aligns with the API endpoints and actions in SKILL.md (session creation, SSE generation, upload, render, export). However there are small inconsistencies: the SKILL.md session creation uses language="en" despite a Japanese-focused skill, and the frontmatter declares a config path (~/.config/nemovideo/) even though the registry metadata earlier listed no required config paths.

Instruction Scope

The runtime instructions tell the agent to: read NEMO_TOKEN from the environment (expected); optionally generate an anonymous token via the remote auth endpoint (reasonable); upload files using multipart form with a local file path (expected for uploads, but implies the agent may read arbitrary user-specified local paths); and detect the install path to set X-Skill-Platform by inspecting local directories (~/.clawhub/, ~/.cursor/skills/). That last step involves probing the filesystem for unspecified install locations which is unnecessary for basic service use and expands the data the agent will access.

Install Mechanism

Instruction-only skill; no install spec and no code files. This is low risk from an installation perspective because nothing is downloaded or written by a packaged installer.

Credentials

Only one credential is declared (NEMO_TOKEN) which is proportional for a remote API. But SKILL.md also references a config path (~/.config/nemovideo/) in its frontmatter and requires detecting local install paths to form headers — both broaden the scope of local data accessed and are not clearly necessary for the stated functionality.

Persistence & Privilege

The skill does not request always:true and is user-invocable. There is no install-time persistence or instruction to modify other skills or system-wide settings.

What to consider before installing

This skill behaves like a client for a remote video-rendering API and will need a NEMO_TOKEN (or it will obtain an anonymous token). Before installing/proceeding: (1) confirm you trust the domain mega-api-prod.nemovideo.ai and the skill owner — there is no homepage or clear provenance; (2) avoid pasting or uploading sensitive local files (the instructions accept file paths and could upload any file you point it to); (3) prefer using an anonymous or limited-scope token rather than a long-lived credential; (4) ask the author why the skill probes local install paths and why the frontmatter lists a local config path (these operations expand what the agent reads from your machine); and (5) request clarification on the language/session mismatch (skill is Japanese but creates sessions with language="en"). If you cannot validate the service or do not want the agent to inspect your filesystem, do not provide NEMO_TOKEN and avoid giving file paths for upload.

Getting Started

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

Try saying:

• "generate my Japanese text prompts"
• "export 1080p MP4"
• "日本語のテキストからプロモーション動画を作成してください"

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.

Text to Video AI Japanese — Generate Videos from Japanese Text

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

A quick example: upload a three-sentence Japanese product description, type "日本語のテキストからプロモーション動画を作成してください", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter Japanese scripts under 100 characters render noticeably faster.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is text-to-video-ai-japanese, 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)

Common Workflows

Quick edit: Upload → "日本語のテキストからプロモーション動画を作成してください" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "日本語のテキストからプロモーション動画を作成してください" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across Japanese social platforms like LINE and NicoNico.