Short Video

create raw footage into trimmed short clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. TikTok creators use it for generating short cl...

Security Scan

The skill's declared requirements and runtime instructions are consistent with a cloud video-editing service: it only needs a single API token, makes network calls to a named API, and has no install step or unrelated credential requests.

Purpose & Capability

Name/description (short-form video editing) align with the instructions: uploading footage, session creation, SSE editing, and export endpoints. The single required env var (NEMO_TOKEN) is appropriate for an external render API. Declared configPath (~/.config/nemovideo/) and attribution headers are plausible for this service.

Instruction Scope

SKILL.md instructs the agent to create/use a bearer token, start sessions, upload files, stream SSE, poll state, and run exports — all within the stated purpose. It also instructs the agent to read this file's YAML frontmatter for attribution headers and to detect install-path to set X-Skill-Platform; this requires reading the skill file and checking known install paths. That is reasonable but worth noting because it involves inspecting the agent's skill location and the skill frontmatter.

Install Mechanism

No install spec and no code files are present (instruction-only). This is the lowest-risk install profile: nothing is downloaded or written to disk by an installer excerpt in the manifest.

Credentials

Only one credential (NEMO_TOKEN) is required and it's the expected credential for the described remote API. The skill provides an anonymous-token flow to obtain a temporary token if none is set. No unrelated secrets or multiple external credentials are requested.

Persistence & Privilege

The skill does not request always: true and uses default autonomous invocation settings. It indicates saving a session_id in-session, but does not ask to modify other skills or system-wide config. No elevated persistence is requested.

Assessment

This skill appears coherent for remote AI video editing: it will upload any footage you provide to the named nemovideo API and use a single bearer token (NEMO_TOKEN) to authenticate. Before installing/using: (1) confirm you trust the domain https://mega-api-prod.nemovideo.ai because your uploads (videos/audio/images) will be transmitted there; avoid sending sensitive footage to this service; (2) provide a dedicated NEMO_TOKEN (or use the anonymous-token flow) rather than reusing general-purpose credentials; (3) note the skill reads its own frontmatter and checks common install paths to set an attribution header — this requires only local read access to the skill file and known install directories; (4) there is no installer and no other credentials requested. If you need higher assurance, request the service's privacy/terms or run a test with non-sensitive sample files first.

Getting Started

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

Try saying:

• "create my raw footage"
• "export 1080p MP4"
• "cut this into a 60-second highlight"

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.

Short Video — Create and Export Short Clips

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

A quick example: upload a 10-minute phone recording, type "cut this into a 60-second highlight clip for TikTok", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: vertical 9:16 video works perfectly for Reels and TikTok exports.

Matching Input to Actions

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

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.

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

• X-Skill-Source: short-video
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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.

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

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 this into a 60-second highlight clip for TikTok" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut this into a 60-second highlight clip for TikTok" — 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 social platforms.