Best Shorts Editor

edit raw video footage into polished short clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. TikTok and YouTube Shorts creators use it...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video-editing service: it needs a NEMO_TOKEN and instructs the agent to upload videos and orchestrate remote rendering; however the source is unknown and it transmits user media to an external API, so you should review privacy before use.

Purpose & Capability

Name/description (short-form video editing) aligns with the runtime instructions and the single required credential (NEMO_TOKEN) for a cloud render backend. The declared config path (~/.config/nemovideo/) and session semantics match the described service.

Instruction Scope

SKILL.md tells the agent to upload user video files (multipart or via URL), create/refresh an anonymous token if NEMO_TOKEN is absent, create sessions, send SSE messages, poll renders, and return download URLs. These actions are appropriate for a remote editing service but do mean user media and session tokens will be transmitted off-device; the skill also detects install path to set an attribution header (minor privacy surface). The instructions explicitly say not to expose tokens or raw API output.

Install Mechanism

Instruction-only skill with no install spec or code files — nothing written to disk by an installer. This is the lowest-risk install mechanism for a skill that delegates work to a cloud API.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is appropriate for calling the described API. The skill will generate an anonymous token if none is present. No unrelated secrets or system credentials are requested.

Persistence & Privilege

always:false and normal autonomous invocation; the skill keeps ephemeral session IDs and uses tokens for API calls but does not request persistent system-wide privileges or modify other skills. Nothing indicates escalation of privileges.

Assessment

This skill appears coherent for a cloud-based video-editing service, but note: it will upload your raw video files and use a NEMO_TOKEN (or obtain an anonymous token) to a remote endpoint (mega-api-prod.nemovideo.ai). Before installing or invoking it, confirm you are comfortable with that service handling and storing your media and that you trust the backend (there is no homepage or known publisher listed). If you want tighter control, avoid sending sensitive videos, provide a token from an account you control (not a privileged system token), and consider asking for more information about the service's privacy/data-retention policy. If you need higher assurance, request a skill with a verifiable homepage, source, or documented API owner.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "cut the best 60 seconds, add"

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.

Best Shorts Editor — Edit and Export Short Clips

Send me your raw video footage and describe the result you want. The AI shorts editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 10-minute vlog recorded on a smartphone, type "cut the best 60 seconds, add captions, and format for YouTube Shorts", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: vertical 9:16 video works best for Shorts and Reels output.

Matching Input to Actions

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

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

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

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the 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.

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 → "cut the best 60 seconds, add captions, and format for YouTube Shorts" → 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 "cut the best 60 seconds, add captions, and format for YouTube Shorts" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for widest platform compatibility.