Editor Ai Korean

Cloud-based editor-ai-korean tool that handles adding Korean subtitles and edits to videos. Upload MP4, MOV, AVI, WebM files (up to 500MB), describe what you...

Security Scan

The skill's actions (uploading and controlling a cloud video-edit API) match its description, but there are inconsistencies and small scope-creep items (local config/install-path access and metadata differences) that merit caution before installing or using it with sensitive data.

Purpose & Capability

The skill is presented as a cloud video editor and its declared primary credential (NEMO_TOKEN) and the described API calls are coherent with that purpose. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that the registry metadata did not declare — it's unclear why local config access is required for a cloud service.

Instruction Scope

Instructions are network-heavy (create sessions, upload files, call render endpoints) which is expected. The runtime guidance also asks the agent to read the skill's YAML frontmatter and detect install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform — that requires probing the user's home filesystem and is not strictly required to perform cloud editing. The skill also recommends keeping technical details out of chat and mandates attribution headers on every request. No instructions ask the agent to read arbitrary unrelated files, but the install-path/config-path checks are unnecessary scope creep and should be verified.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk by an installer. This is the lowest install risk.

Credentials

Only NEMO_TOKEN is declared as required, which fits a cloud API service. The SKILL.md also documents a fallback anonymous-token flow (POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token) so the skill can operate without a pre-provided token. The unexpected metadata reference to ~/.config/nemovideo/ is the main proportionality concern: a purely cloud service typically doesn't need local config access.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It does use session tokens for job management, which is normal for this kind of service. Autonomous invocation is allowed by default but not combined with other high-risk factors here.

What to consider before installing

This skill largely does what it says (cloud-based Korean subtitle/editing) and needs a NEMO_TOKEN or will obtain a temporary anonymous token from https://mega-api-prod.nemovideo.ai. Before installing or using it: 1) Verify the backend domain (mega-api-prod.nemovideo.ai) and its privacy policy — uploaded videos and audio will be sent to that service. 2) Prefer using a trusted account token rather than relying on anonymous flows for sensitive media. 3) Ask the publisher or maintainer why the skill metadata references a local config path (~/.config/nemovideo/) and why the agent should check install paths — if the skill will probe or read local config, get explicit details about what is read and why. 4) If you need stronger assurance, request the skill's source code or a homepage and confirm there are no instructions that read or transmit files outside the declared upload flow. These clarifications would raise confidence to 'high' and could make the skill appear benign.

Getting Started

Share your video clips and I'll get started on AI Korean editing. Or just tell me what you're thinking.

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "add Korean subtitles and cut out"

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 Editor Korean — Edit Videos with Korean Captions

Drop your video clips in the chat and tell me what you need. I'll handle the AI Korean editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute vlog recorded on a smartphone, ask for add Korean subtitles and cut out silent pauses, 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 clips under 3 minutes generate Korean captions most accurately.

Matching Input to Actions

User prompts referencing editor ai korean, 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: editor-ai-korean
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

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.

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 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 → "add Korean subtitles and cut out silent pauses" → 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 "add Korean subtitles and cut out silent pauses" — 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 with Korean video platforms.