edit raw video footage into edited video clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. Hindi-speaking content creators use it for...
---
name: video-editing-karne-ka-ai
version: "1.0.0"
displayName: "Video Editing Karne Ka AI β Edit and Export Polished Videos"
description: >
edit raw video footage into edited video clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. Hindi-speaking content creators use it for editing raw footage into polished videos using AI β processing takes 1-2 minutes on cloud GPUs and you get 1080p MP4 files.
metadata: {"openclaw": {"emoji": "π¬", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "greeting_v2"}}
---
## 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 video editing.
**Try saying:**
- "edit a 2-minute phone-recorded vlog clip into a 1080p MP4"
- "trim unnecessary pauses, add transitions, and put Hindi subtitles"
- "editing raw footage into polished videos using AI for Hindi-speaking content 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.
# Video Editing Karne Ka AI β Edit and Export Polished Videos
Send me your raw video footage and describe the result you want. The AI video editing runs on remote GPU nodes β nothing to install on your machine.
A quick example: upload a 2-minute phone-recorded vlog clip, type "trim unnecessary pauses, add transitions, and put Hindi subtitles", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.
Worth noting: shorter clips under 3 minutes process significantly faster.
## Matching Input to Actions
User prompts referencing video editing karne ka ai, 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.
Skill attribution β read from this file's YAML frontmatter at runtime:
- `X-Skill-Source`: `video-editing-karne-ka-ai`
- `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.
**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.
### 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.
### 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 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)
```
### 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 β "trim unnecessary pauses, add transitions, and put Hindi subtitles" β 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 "trim unnecessary pauses, add transitions, and put Hindi subtitles" β 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 platforms.
don't have the plugin yet? install it then click "run inline in claude" again.