Jianying Video

Turn a 2-minute smartphone recording into 1080p edited MP4 videos just by typing what you need. Whether it's editing short-form videos with auto-captions and...

Security Scan

The skill's requests and runtime instructions are coherent with a cloud-based video-editing service: it needs a NEMO_TOKEN, uploads media to nemovideo.ai, and contains only API-driven instructions — no unrelated credentials or installs.

Purpose & Capability

Name/description, declared env (NEMO_TOKEN), and the SKILL.md all describe a cloud video-editing workflow. Required env var and the documented endpoints are consistent with that purpose; no unrelated credentials or binaries are requested.

Instruction Scope

Instructions stay within the editing workflow (create/check session, upload video, use SSE, poll export). They explicitly instruct uploading user videos to https://mega-api-prod.nemovideo.ai and include sending Authorization: Bearer <NEMO_TOKEN>. This is expected for a cloud editor, but it means raw user media and metadata will be transmitted to that third party — users should be aware.

Install Mechanism

No install spec or code files — instruction-only skill. Lowest risk from install mechanism because nothing is downloaded or written by an installer.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv). The frontmatter also lists ~/.config/nemovideo/ as a config path, which is plausible for cached tokens. The skill will also attempt to obtain an anonymous token from the service if none is present. That behavior is reasonable for this service but means the skill can operate without an explicit user-provided token by requesting one from the remote API.

Persistence & Privilege

always is false, no install or background persistence requested, and the skill does not claim to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but is not combined with other elevated privileges here.

Assessment

This skill appears internally consistent for a cloud-based video editor, but before installing consider: (1) Uploaded videos and any associated metadata will be sent to mega-api-prod.nemovideo.ai and processed on their GPUs — do not upload sensitive or confidential footage. (2) The skill uses an Authorization: Bearer <NEMO_TOKEN> header; it can accept a user-provided token or request an anonymous token automatically — if you prefer control, provide your own token or avoid anonymous provisioning. (3) The skill may read its own config directory (~/.config/nemovideo/) to find cached tokens; clear that directory if you want to revoke local cached credentials. (4) Verify the service's privacy, terms, and billing (the skill mentions credits and 402 on export) before using with large or private data. (5) The package has no install step (instruction-only) and no code files to review, and the skill's source/homepage are unknown — if provenance matters, seek a published homepage or vendor info before trusting production data.

Getting Started

Ready when you are. Drop your raw video footage here or describe what you want to make.

Try saying:

• "edit a 2-minute smartphone recording into a 1080p MP4"
• "auto-cut the video, add subtitles, and sync background music"
• "editing short-form videos with auto-captions and music for social media for TikTok and Reels creators"

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.

Jianying Video Editor — Edit and Export Social Videos

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

Here's a typical use: you send a a 2-minute smartphone recording, ask for auto-cut the video, add subtitles, and sync background music, 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 60 seconds process significantly faster and yield cleaner auto-captions.

Matching Input to Actions

User prompts referencing jianying video, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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 jianying-video, 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.

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)

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

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.

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

Common Workflows

Quick edit: Upload → "auto-cut the video, add subtitles, and sync background music" → 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 "auto-cut the video, add subtitles, and sync background music" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best compatibility across TikTok, Instagram, and YouTube.