Skill: whitejohnk-26/editor-cinematic (version 1.0.0)

--- name: editor-cinematic version: "1.0.0" displayName: "Editor Cinematic — Turn Footage into Cinematic Videos" description: > transform raw video footage into cinematic edited video with this skill. Works with MP4, MOV, AVI, ProRes files up to 500MB. filmmakers, content creators, videographers use it for transforming raw footage into cinematic-style videos with color grading and dramatic cuts — processing takes 1-2 minutes on cloud GPUs and you get 4K MP4 files. metadata: {"openclaw": {"emoji": "🎬", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "short_prompts"}} --- ## Getting Started > Share your raw video footage and I'll get started on cinematic AI editing. Or just tell me what you're thinking. **Try saying:** - "transform my raw video footage" - "export 4K MP4" - "apply cinematic color grading, add dramatic" ### 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. # Editor Cinematic — Turn Footage into Cinematic Videos Drop your raw video footage in the chat and tell me what you need. I'll handle the cinematic AI editing on cloud GPUs — you don't need anything installed locally. Here's a typical use: you send a a 2-minute handheld camera recording of a city street, ask for apply cinematic color grading, add dramatic transitions, and sync cuts to the background music, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 4K by default. One thing worth knowing — clips under 3 minutes render faster and give the AI more precise control over cinematic pacing. ## Matching Input to Actions User prompts referencing editor cinematic, 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. All calls go to `https://mega-api-prod.nemovideo.ai`. The main endpoints: 1. **Session** — `POST /api/tasks/me/with-session/nemo_agent` with `{"task_name":"project","language":"<lang>"}`. Gives you a `session_id`. 2. **Chat (SSE)** — `POST /run_sse` with `session_id` and your message in `new_message.parts[0].text`. Set `Accept: text/event-stream`. Up to 15 min. 3. **Upload** — `POST /api/upload-video/nemo_agent/me/<sid>` — multipart file or JSON with URLs. 4. **Credits** — `GET /api/credits/balance/simple` — returns `available`, `frozen`, `total`. 5. **State** — `GET /api/state/nemo_agent/me/<sid>/latest` — current draft and media info. 6. **Export** — `POST /api/render/proxy/lambda` with render ID and draft JSON. Poll `GET /api/render/proxy/lambda/<id>` every 30s for `completed` status and download URL. Formats: 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` | `editor-cinematic` | | `X-Skill-Version` | frontmatter `version` | | `X-Skill-Platform` | auto-detect: `clawhub` / `cursor` / `unknown` from install path | **All requests** must include: `Authorization: Bearer <NEMO_TOKEN>`, `X-Skill-Source`, `X-Skill-Version`, `X-Skill-Platform`. Missing attribution headers will cause export to fail with 402. Draft JSON uses short keys: `t` for tracks, `tt` for track type (0=video, 1=audio, 7=text), `sg` for segments, `d` for duration in ms, `m` for metadata. Example timeline summary: ``` Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s) ``` ### 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 ### 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. ### 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 ## Common Workflows **Quick edit**: Upload → "apply cinematic color grading, add dramatic transitions, and sync cuts to the background music" → 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 "apply cinematic color grading, add dramatic transitions, and sync cuts to the background music" — concrete instructions get better results. Max file size is 500MB. Stick to MP4, MOV, AVI, ProRes for the smoothest experience. Export as MP4 with H.264 codec for the best balance of cinematic quality and file size.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)