Jianying Editor

Get edited video clips ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, MKV, up to 500MB), say something like "...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based AI video editor: it only needs a NEMO_TOKEN and talks to nemovideo.ai endpoints to upload, edit, and export videos.

Purpose & Capability

Name/description (video editing) aligns with required env var (NEMO_TOKEN), declared config path (~/.config/nemovideo/), and the documented API endpoints and upload/export workflow. Nothing requested appears unrelated to video editing.

Instruction Scope

The SKILL.md is instruction-only and directs the agent to authenticate (use NEMO_TOKEN or request an anonymous token), create a session, upload video files, use SSE for edits, and poll for export results — all appropriate for a cloud render pipeline. It also asks the agent to detect the agent install path (~/.clawhub/, ~/.cursor/skills/) to set an attribution header (X-Skill-Platform). Reading those install paths is a modest scope expansion beyond pure editing (it reveals filesystem layout) but is explained as attribution metadata rather than a functional necessity.

Install Mechanism

No install spec or code files — instruction-only. This is the lowest-risk install model: nothing is written to disk by an installer per the provided package metadata.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required and used for API Bearer authentication. The instructions also describe generating a short-lived anonymous token via the service's anonymous endpoint when a token is not present. No other unrelated secrets or environment variables are requested.

Persistence & Privilege

The skill does not request persistent/always-on privileges (always:false). It instructs saving a session_id for the render workflow, which is normal for a session-based cloud service. It does not ask to modify other skills or global agent settings.

Assessment

This skill appears internally consistent for a cloud video-editing capability, but understand what that means before installing: uploaded videos and metadata will be sent to mega-api-prod.nemovideo.ai and processed there, and the skill needs a NEMO_TOKEN (or it will request a short-lived anonymous token). The skill may read your agent install path to populate an attribution header and may store session state (session_id) as part of normal operation. Verify you trust the nemovideo.ai service and avoid sending sensitive footage you wouldn't want uploaded to a third party. Also note the skill's source and homepage are unknown — if you need stronger assurance, ask the publisher for provenance or use a skill from a known provider.

Getting Started

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

Try saying:

• "edit a 2-minute smartphone video clip into a 1080p MP4"
• "cut the video, add background music, and apply auto captions"
• "editing short-form videos for TikTok and Reels for TikTok creators"

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.

Jianying Editor — Edit and Export Video Clips

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

Say you have a 2-minute smartphone video clip and want to cut the video, add background music, and apply auto captions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

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

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

• X-Skill-Source: jianying-editor
• 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.

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the video, add background music, and apply auto captions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "cut the video, add background music, and apply auto captions" → 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.