🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί Clip Assistant
πŸ¦€ ClawHub

Clip Assistant

by @peand-rover

Turn a 2-minute raw interview recording into 1080p edited video clips just by typing what you need. Whether it's trimming and enhancing short clips for socia...

Versionv1.0.0
Downloads283
#video#legal#hr
TERMINAL
clawhub install clip-assistant

πŸ“– About This Skill

name: clip-assistant version: "1.0.0" displayName: "Clip Assistant β€” Edit and Export Video Clips" description: > Turn a 2-minute raw interview recording into 1080p edited video clips just by typing what you need. Whether it's trimming and enhancing short clips for social media or quick social content, drop your video clips and describe the result you want. No timeline dragging, no export settings β€” 30-60 seconds from upload to download. metadata: {"openclaw": {"emoji": "βœ‚οΈ", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "short_prompts"}}

Getting Started

> Share your video clips and I'll get started on AI clip editing. Or just tell me what you're thinking.

Try saying:

  • "edit my video clips"
  • "export 1080p MP4"
  • "trim the best 30 seconds and"

    • 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.

    Clip Assistant β€” Edit and Export Video Clips

    Drop your video clips in the chat and tell me what you need. I'll handle the AI clip editing on cloud GPUs β€” you don't need anything installed locally.

    Here's a typical use: you send a a 2-minute raw interview recording, ask for trim the best 30 seconds and add a text overlay with my channel name, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

    One thing worth knowing β€” shorter clips under 60 seconds process significantly faster.

    Matching Input to Actions

    User prompts referencing clip assistant, 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.

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

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

    Every API call needs Authorization: Bearer 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":""} β€” returns task_id, session_id.

    Send message (SSE): POST /run_sse β€” body {"app_name":"nemo_agent","user_id":"me","session_id":"","new_message":{"parts":[{"text":""}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

    Upload: POST /api/upload-video/nemo_agent/me/ β€” file: multipart -F "files=@/path", or URL: {"urls":[""],"source_type":"url"}

    Credits: GET /api/credits/balance/simple β€” returns available, frozen, total

    Session state: GET /api/state/nemo_agent/me//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_","sessionId":"","draft":,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/ 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.

    SSE Event Handling

    | Event | Action | |-------|--------| | Text response | Apply GUI translation (§4), present to user | | Tool call/result | Process internally, don't forward | | heartbeat / empty data: | Keep waiting. Every 2 min: "⏳ Still working..." | | Stream closes | Process final response |

    ~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

    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)

    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= (get 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 |

    Tips and Tricks

    The backend processes faster when you're specific. Instead of "make it look better", try "trim the best 30 seconds and add a text overlay with my channel name" β€” 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 all platforms.

    Common Workflows

    Quick edit: Upload β†’ "trim the best 30 seconds and add a text overlay with my channel name" β†’ 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.

    πŸ’‘ Examples

    > Share your video clips and I'll get started on AI clip editing. Or just tell me what you're thinking.

    Try saying:

  • "edit my video clips"
  • "export 1080p MP4"
  • "trim the best 30 seconds and"

    • 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.

    Clip Assistant β€” Edit and Export Video Clips

    Drop your video clips in the chat and tell me what you need. I'll handle the AI clip editing on cloud GPUs β€” you don't need anything installed locally.

    Here's a typical use: you send a a 2-minute raw interview recording, ask for trim the best 30 seconds and add a text overlay with my channel name, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

    One thing worth knowing β€” shorter clips under 60 seconds process significantly faster.