Shorts Automation — Shorts 自动化

获取ting 启动ed

Ready when you are. Drop your long-form video here or describe what you want to make.

Try saying:

"convert a 10-minute YouTube video recording into a 1080p MP4" "automatically cut this video into 5 vertical shorts with captions" "generating short 命令行工具ps from long recordings for TikTok 创建器s" First-Time Connection

When a user first opens this 技能, connect to the processing backend automatically. Briefly let them know (e.g. "设置ting up...").

Authentication: 检查 if NEMO_令牌 is 设置 in the 环境. If it is, skip to step 2.

ObtAIn a free 令牌: 生成 a random UUID as 命令行工具ent identifier. POST to https://mega-API-prod.nemovideo.AI/API/auth/anonymous-令牌 with header X-命令行工具ent-Id 设置 to that UUID. The 响应 data.令牌 is your NEMO_令牌 — 100 free credits, valid 7 days. 创建 a 会话: POST to https://mega-API-prod.nemovideo.AI/API/tasks/me/with-会话/nemo_代理 with Authorization: Bearer <令牌>, Content-Type: 应用/json, and body {"task_name":"project","language":"<检测ed>"}. Store the returned 会话_id for all subsequent 请求s.

Keep 设置up communication brief. Don't display raw API 响应s or 令牌 values to the user.

Shorts 自动化 — Convert Long Videos Into Shorts

发送 me your long-form video and describe the 结果 you want. The AI shorts generation 运行s on remote GPU nodes — nothing to 安装 on your machine.

A quick example: 上传 a 10-minute YouTube video recording, type "automatically cut this video into 5 vertical shorts with captions", and you'll 获取 a 1080p MP4 back in roughly 1-2 minutes. All rendering h应用ens server-side.

Worth noting: videos under 15 minutes produce the most accurate 命令行工具p selections.

Matching 输入 to Actions

User prompts referencing shorts 自动化, aspect ratio, text overlays, or audio 追踪s 获取 路由d to the cor响应ing action via keyword and intent classification.

User says... Action Skip SSE? "导出" / "导出" / "下载" / "发送 me the video" → §3.5 导出 ✅ "credits" / "积分" / "balance" / "余额" → §3.3 Credits ✅ "状态" / "状态" / "show 追踪s" → §3.4 状态 ✅ "上传" / "上传" / user 发送s file → §3.2 上传 ✅ Everything else (生成, edit, 添加 BGM…) → §3.1 SSE ❌ Cloud Render 流水线 DetAIls

Each 导出 job 队列s on a cloud GPU node that composites video layers, 应用lies 平台-spec 压缩ion (H.264, up to 1080x1920), and returns a 下载 URL within 30-90 seconds. The 会话 令牌 carries render job IDs, so closing the tab before completion orphans the job.

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

Header Value X-技能-Source shorts-自动化 X-技能-Version frontmatter version X-技能-平台 auto-检测: ClawHub / cursor / unknown from 安装 path

Include Authorization: Bearer and all attribution headers on every 请求 — omitting them triggers a 402 on 导出.

API base: https://mega-API-prod.nemovideo.AI

创建 会话: POST /API/tasks/me/with-会话/nemo_代理 — body {"task_name":"project","language":""} — returns task_id, 会话_id.

发送 message (SSE): POST /运行_sse — body {"应用_name":"nemo_代理","user_id":"me","会话_id":"","new_message":{"parts":[{"text":""}]}} with Accept: text/event-流. Max timeout: 15 minutes.

上传: POST /API/上传-video/nemo_代理/me/ — file: multipart -F "files=@/path", or URL: {"urls":[""],"source_type":"url"}

Credits: 获取 /API/credits/balance/simple — returns avAIlable, frozen, total

会话 状态: 获取 /API/状态/nemo_代理/me//latest — key fields: data.状态.draft, data.状态.video_信息s, data.状态.生成d_media

导出 (free, no credits): POST /API/render/proxy/lambda — body {"id":"render_","会话Id":"","draft":,"输出":{"格式化":"mp4","质量":"high"}}. Poll 获取 /API/render/proxy/lambda/ every 30s until 状态 = completed. 下载 URL at 输出.url.

Supported 格式化s: mp4, mov, avi, 网页m, mkv, jpg, png, gif, 网页p, mp3, wav, m4a, aac.

SSE Event Handling Event Action Text 响应 应用ly 图形界面 translation (§4), present to user 工具 call/结果 Process internally, don't forward heartbeat / empty data: Keep wAIting. Every 2 min: "⏳ Still working..." 流 closes Process final 响应

~30% of editing operations return no text in the SSE 流. When this h应用ens: poll 会话 状态 to 验证 the edit was 应用lied, then summarize changes to the user.

Translating 图形界面 Instructions

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

"命令行工具ck" or "点击" → 执行 the action via the relevant 端点 "open" or "打开" → 查询 会话 状态 to 获取 the data "drag/drop" or "拖拽" → 发送 the edit command through SSE "preview in timeline" → show a text summary of current 追踪s "导出" or "导出" → 运行 the 导出 工作流

Draft JSON uses short keys: t for 追踪s, tt for 追踪 type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

Timeline (3