Korean Editor Ai

v1.0.0

K-content creators edit raw video footage into Korean-edited videos using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, renders on cloud GPUs at 1080p...

⭐ 0· 87·0 current·0 all-time

by@mory128

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mory128/korean-editor-ai.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Korean Editor Ai" (mory128/korean-editor-ai) from ClawHub.
Skill page: https://clawhub.ai/mory128/korean-editor-ai
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 korean-editor-ai

ClawHub CLI

Package manager switcher

npx clawhub@latest install korean-editor-ai

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Suspicious

medium confidence

✓

Purpose & Capability

Name/description align with the runtime instructions: the SKILL.md exclusively describes using a remote video-processing API, uploading files, starting sessions, streaming edits, and exporting MP4s. Requesting a service token (NEMO_TOKEN) is expected for this purpose.

Instruction Scope

Most runtime steps are within scope (auth, upload, SSE, render polling). However the instructions ask the agent to detect the installation path to set X-Skill-Platform (checking ~/.clawhub/, ~/.cursor/skills/, etc.), which requires inspecting the user's filesystem/environment even though the registry metadata did not declare config paths for that. The SKILL.md frontmatter itself lists a configPaths entry (~/.config/nemovideo/) that is not reflected in the registry metadata — an inconsistency. The instructions also direct sending user media to an external host (mega-api-prod.nemovideo.ai), which is expected but privacy-sensitive.

✓

Install Mechanism

Instruction-only skill with no install spec or downloaded code. This is low-risk from an install mechanism perspective (nothing will be written to disk by an installer).

ℹ

Credentials

The skill only requires a single credential (NEMO_TOKEN), which is proportionate for a remote video service. But the SKILL.md frontmatter references a config path (~/.config/nemovideo/) and the instructions imply checking installation directories — access to these paths was not declared in the registry metadata. Confirm whether the agent will read local paths and how session tokens are stored.

✓

Persistence & Privilege

always:false and no install-time hooks are present. The instructions ask to save session_id and use tokens for API calls (ephemeral usage), but there is no request for permanent agent-wide privileges or modifications to other skills.

What to consider before installing

This skill appears to do what it claims (upload your video to a cloud renderer using NEMO_TOKEN), but verify the following before enabling it: 1) Provenance: there is no source/homepage — ask the publisher for a code repo or company page. 2) Token safety: only set NEMO_TOKEN if you trust the service; anonymous-token generation is supported but yields short-lived credits. 3) Privacy: your raw footage will be uploaded to mega-api-prod.nemovideo.ai — avoid uploading sensitive content unless you accept that. 4) Filesystem access: the SKILL.md asks the agent to detect install paths to set an attribution header; confirm whether the skill will inspect your home directories and whether that behavior is necessary. 5) Ask the publisher to reconcile the registry metadata vs SKILL.md (configPaths mismatch) and to publish a homepage or privacy/terms link. If you proceed, prefer using the anonymous token flow or a disposable token and keep monitoring for unexpected network requests.

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

Runtime requirements

🇰🇷 Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk973tdt31586pjb1bdft0qzntx84jarm

87downloads

0stars

1versions

Updated 2w ago

v1.0.0

MIT-0

Getting Started

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

Try saying:

"edit my raw video footage"
"export 1080p MP4"
"edit this video with Korean-style cuts,"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Korean Editor AI — Edit Videos with Korean Style

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

Say you have a 2-minute vlog recorded on a smartphone and want to edit this video with Korean-style cuts, add Korean subtitles, and apply clean transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds produce the most accurate Korean subtitle sync.

Matching Input to Actions

User prompts referencing korean 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is korean-editor-ai, 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.

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

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 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 → "edit this video with Korean-style cuts, add Korean subtitles, and apply clean transitions" → 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 "edit this video with Korean-style cuts, add Korean subtitles, and apply clean transitions" — 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 Korean social platforms like Naver and KakaoTV.

Comments

Loading comments...