Shorts Maker

convert long-form video into vertical short clips with this shorts-maker skill. Works with MP4, MOV, AVI, WebM files up to 500MB. TikTok creators use it for...

Security Scan

The skill's runtime instructions match a video-processing service, but metadata mismatches and an unexplained config path requirement raise coherence and privacy concerns before you install or use it.

Purpose & Capability

The declared purpose (convert long videos to short vertical clips) aligns with the HTTP endpoints, upload/render/export workflow, and required single API token (NEMO_TOKEN). Nothing in the instructions claims unrelated capabilities (e.g., system administration).

Instruction Scope

Instructions direct the agent to upload user video files and user-supplied messages to an external API (mega-api-prod.nemovideo.ai) and to stream SSE responses back; that is expected for this purpose but has privacy implications. The skill also instructs obtaining an anonymous token automatically if NEMO_TOKEN is absent, which means the agent will contact the service on its own without further user confirmation.

Install Mechanism

No install script or code is present (instruction-only), so nothing is written to disk at install-time. This is lower risk from an install-origin perspective.

Credentials

The skill declares only one required env var (NEMO_TOKEN), which is reasonable. However, the SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) that was not listed in the registry metadata — this mismatch is unexplained and implies possible local config access that wasn't declared elsewhere.

Persistence & Privilege

always is false and the skill is not requesting elevated or persistent platform privileges. Autonomous model invocation is allowed (default) but is not combined with other high-risk attributes here.

What to consider before installing

This skill appears to implement what it claims (uploading videos to a cloud render API and returning processed MP4s) but you should be cautious before enabling it. Key things to consider: (1) It will send your raw video files to https://mega-api-prod.nemovideo.ai — do not upload sensitive or private footage unless you trust that service and have reviewed its privacy/retention policy. (2) The SKILL.md frontmatter mentions a local config path (~/.config/nemovideo/) even though the registry metadata did not — ask the publisher whether the agent will read local config files and why. (3) The agent will auto-acquire an anonymous token if no NEMO_TOKEN is provided, meaning it will make network calls without further confirmation. (4) There is no publisher, homepage, or source listed — prefer skills with an identifiable owner and privacy terms. If you still want to use it, require explicit consent before uploading files, avoid placing long-lived credentials in your environment, and ask the publisher for a canonical documentation/privacy link.

Getting Started

Send me your long-form video and I'll handle the AI shorts generation. Or just describe what you're after.

Try saying:

• "convert a 10-minute YouTube video recording into a 1080p MP4"
• "cut the best 60-second moments and format them for TikTok"
• "generating short clips from long recordings for TikTok creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Shorts Maker — Convert Long Videos Into Shorts

This tool takes your long-form video and runs AI shorts generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 10-minute YouTube video recording and want to cut the best 60-second moments and format them for TikTok — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: vertical 9:16 video works best for Reels and TikTok output.

Matching Input to Actions

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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

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

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.

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-second moments and format them for TikTok" → 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-second moments and format them 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 TikTok, Reels, and YouTube Shorts.