Japanese Ai Video Generator Free

v1.0.0

Get Japanese AI videos ready to post, without touching a single slider. Upload your text or images (MP4, MOV, PNG, JPG, up to 200MB), say something like "cre...

0· 64·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mory128/japanese-ai-video-generator-free.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Japanese Ai Video Generator Free" (mory128/japanese-ai-video-generator-free) from ClawHub.
Skill page: https://clawhub.ai/mory128/japanese-ai-video-generator-free
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install japanese-ai-video-generator-free

ClawHub CLI

Package manager switcher

npx clawhub@latest install japanese-ai-video-generator-free
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill is described as a cloud-hosted Japanese AI video generator and its instructions only call the nemo video API endpoints and require a NEMO_TOKEN. Requesting a token for the vendor API is proportionate to the stated purpose.
Instruction Scope
Instructions direct the agent to obtain an anonymous token if NEMO_TOKEN is absent, create sessions, stream SSE messages, and upload user-provided files (multipart or URL). Uploading user media to the vendor API is expected for this service, but the SKILL.md references local file paths for multipart uploads and a config path in frontmatter — confirm how the platform will mediate file access and whether the agent will attempt to read local paths directly.
Install Mechanism
There is no install spec and no code to download or run; this is instruction-only, which minimizes installation risk.
Credentials
Only one credential (NEMO_TOKEN) is required, which is appropriate for a third-party API. However, SKILL.md metadata includes a configPaths entry (~/.config/nemovideo/) while the registry metadata reported 'none' for required config paths — this mismatch should be clarified (does the skill attempt to read that config directory?).
Persistence & Privilege
The skill is not marked always:true and does not request any elevated platform-wide privileges. Autonomous invocation is allowed (default) but not unusual; nothing indicates it attempts to alter other skills or global settings.
Assessment
This skill appears to do what it says: it sends text/images to nemo's API to generate videos and needs a NEMO_TOKEN (or will create a short-lived anonymous token). Before installing, confirm the vendor domain (mega-api-prod.nemovideo.ai) and privacy terms — anything you upload will be sent off-platform. Ask the author to clarify the configPaths reference (does it try to read ~/.config/nemovideo/?) and how file uploads are handled by the host (the skill mentions multipart file paths which you should not let the agent read from your local filesystem without explicit platform mediation). Prefer using an anonymous token or a limited scope token rather than long-lived secrets, and avoid uploading sensitive PII or secrets to the service. If you’re unsure about the domain or policy, don’t provide your permanent NEMO_TOKEN and revoke any tokens after testing.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎌 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97965nq5jqy5cdsmaj7825f1d85h4tg
64downloads
0stars
1versions
Updated 3d ago
v1.0.0
MIT-0

Getting Started

Send me your text or images and I'll handle the AI video generation. Or just describe what you're after.

Try saying:

  • "generate a short Japanese product description text into a 1080p MP4"
  • "create a 30-second Japanese promotional video from this text with subtitles"
  • "generating Japanese-language videos from text or images for free for Japanese 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.

Japanese AI Video Generator Free — Generate Japanese Videos with AI

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

Say you have a short Japanese product description text and want to create a 30-second Japanese promotional video from this text with subtitles — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 60 words generate faster and more accurately in Japanese.

Matching Input to Actions

User prompts referencing japanese ai video generator free, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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.

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

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

HeaderValue
X-Skill-Sourcejapanese-ai-video-generator-free
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-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 Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend saysYou 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

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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.

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 → "create a 30-second Japanese promotional video from this text with 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a 30-second Japanese promotional video from this text with subtitles" — concrete instructions get better results.

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

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

Comments

Loading comments...