Short Video Auto

convert raw video footage into auto-edited short clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. TikTok and Reels creators use it fo...

Security Scan

The skill's requested access and runtime instructions are consistent with an auto-editing cloud video service — nothing requested appears disproportionate to its stated purpose, though you should still review privacy implications before uploading videos or providing a long-lived token.

Purpose & Capability

Name and description match the instructions: uploading video, creating sessions, starting renders, and returning download URLs. The declared primary env var (NEMO_TOKEN) matches the backend Authorization usage. Minor mismatch: metadata lists a config path (~/.config/nemovideo/) that the SKILL.md does not explicitly read; this is plausible (for caching tokens/sessions) but not strictly necessary for the described runtime flow.

Instruction Scope

SKILL.md only instructs the agent to interact with the documented backend endpoints, upload files, manage session tokens, and stream SSE responses — all within the scope of auto-editing video. It does not instruct reading unrelated system files or other credentials. One implementation note: it asks callers to auto-detect an install path value for an attribution header (X-Skill-Platform), which implicitly requires access to the agent’s install context; this is a minor scope expansion but not unexpected for attribution.

Install Mechanism

No install spec or code files are included; this is an instruction-only skill (lowest install risk). No downloads or third-party packages are specified.

Credentials

Only a single credential (NEMO_TOKEN) is required and is used as the Bearer token for API calls — this is proportionate. The skill will also generate an anonymous token via the backend if NEMO_TOKEN isn't present (documented). The declared configPaths value could allow reading local stored config, which is reasonable for token/session caching but should be considered by users who keep other secrets in that directory.

Persistence & Privilege

Skill is not always-enabled and does not request persistent or cross-skill privileges. Autonomous invocation is allowed by default (expected). The skill does not instruct modification of other skills or system-wide agent settings.

Scan Findings in Context

[no_matches] expected: The static regex scanner had no code to analyze (instruction-only SKILL.md). Absence of matches is not a guarantee of safety; runtime behavior is defined by the SKILL.md network calls and headers.

Assessment

This skill connects to a third-party cloud backend (mega-api-prod.nemovideo.ai) and uploads your videos for processing. Before installing or using it: (1) Confirm you trust that domain and are comfortable uploading the content (do not upload sensitive/private/proprietary footage). (2) Prefer supplying your own NEMO_TOKEN if you have an account; otherwise the skill will request an anonymous token from the backend (100 free credits, 7-day expiry) and use it for uploads/exports. (3) Be aware the skill may read or write its own config directory (~/.config/nemovideo/) for caching sessions/tokens; avoid storing other secrets there. (4) If you need stronger privacy controls, ask the developer for a privacy/retention policy or an on-prem alternative. (5) Because the skill's source and homepage are unknown, exercise caution: verify the vendor or test with non-sensitive sample videos first.

Getting Started

Got raw video footage to work with? Send it over and tell me what you need — I'll take care of the AI auto editing.

Try saying:

• "convert a 3-minute unedited phone recording into a 1080p MP4"
• "automatically cut, trim, and format this into a 30-second short video"
• "automatically editing long recordings into short social media clips 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.

Short Video Auto — Auto Edit and Export Short Clips

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

Say you have a 3-minute unedited phone recording and want to automatically cut, trim, and format this into a 30-second short video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: clips under 2 minutes produce the most accurate auto-edit results.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	short-video-auto
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "automatically cut, trim, and format this into a 30-second short video" — 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 TikTok, Reels, and YouTube Shorts.

Common Workflows

Quick edit: Upload → "automatically cut, trim, and format this into a 30-second short video" → Download MP4. Takes 30-60 seconds 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.