Japanese Editor Ai

edit raw video footage into Japanese-edited videos with this japanese-editor-ai skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators tar...

Security Scan

The skill's runtime instructions mostly match a cloud video-editing service, but there are inconsistencies in the declared requirements and a few scope details you should review before installing.

Purpose & Capability

Name and description (Japanese video editing, subtitles, cloud render) align with the runtime endpoints and actions in SKILL.md — the required NEMO_TOKEN and the listed API endpoints are consistent with a remote video-processing backend.

Instruction Scope

The SKILL.md contains concrete network calls, SSE handling, upload and render flows and instructs the agent how to interact with the remote API. It also instructs the agent to read the skill's YAML frontmatter and detect install paths to populate X-Skill-Platform — this requires the agent to read local paths (install path and the SKILL.md itself) but is limited in scope to attribution and header population.

Install Mechanism

This is an instruction-only skill with no install spec or downloaded artifacts, so nothing is written to disk by an installer. That is the lowest-risk install model.

Credentials

Registry metadata lists NEMO_TOKEN as a required primary credential, but SKILL.md explicitly describes a fallback flow to obtain an anonymous token if NEMO_TOKEN is not present. SKILL.md also references a config path (~/.config/nemovideo/) in its frontmatter metadata which is not reflected in the registry requirement summary — this mismatch is an inconsistency that could lead to the agent reading local config files unexpectedly. Otherwise only the single service token is requested, which is proportionate for a cloud API integration.

Persistence & Privilege

always is false and the skill does not request permanent elevated privileges. Autonomous invocation is allowed (default) but not combined with other high-risk flags.

What to consider before installing

This skill appears to be a wrapper for a cloud video-editing backend (nemovideo.ai) and mostly behaves as expected, but note two issues before installing: (1) the registry metadata says NEMO_TOKEN is required while the SKILL.md also explains how to auto-create an anonymous token — confirm whether you must set a persistent token or the skill will use anonymous tokens. (2) SKILL.md references reading local config/install paths (~/.config/nemovideo/, install path detection) to set attribution headers; confirm you are comfortable with the skill reading those paths. Also consider: the skill will upload your raw video footage to an external service — verify the service owner, privacy policy, and that you trust the domain (mega-api-prod.nemovideo.ai). Because the skill source/homepage is unknown, prefer not to inject long-lived or sensitive credentials into NEMO_TOKEN until you confirm the provider and review a trusted source repository or documentation. If you want more confidence, ask the publisher for a homepage/repo or request clarification on the token/config path behavior.

Getting Started

Send me your raw video footage and I'll handle the AI Japanese editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute vlog recorded in Japan into a 1080p MP4"
• "edit this footage with Japanese-style cuts and add Japanese subtitles"
• "editing videos with Japanese subtitles and localized style for content creators targeting Japanese audiences"

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.

Japanese Editor AI — Edit Videos with Japanese Subtitles

This tool takes your raw video footage and runs AI Japanese editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute vlog recorded in Japan and want to edit this footage with Japanese-style cuts and add Japanese subtitles — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster and yield cleaner subtitle timing.

Matching Input to Actions

User prompts referencing japanese editor ai, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: japanese-editor-ai
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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

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.

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

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 "edit this footage with Japanese-style cuts and add Japanese subtitles" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across Japanese social platforms like Niconico and YouTube Japan.

Common Workflows

Quick edit: Upload → "edit this footage with Japanese-style cuts and add Japanese 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.