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

Analyze Video

by @vynbosserman65

analyze video clips into video insights report with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. marketers use it for extracting scene break...

Versionv1.0.0
Downloads288
#clawhub
TERMINAL
clawhub install analyze-video

πŸ“– About This Skill

name: analyze-video version: "1.0.0" displayName: "Analyze Video β€” Extract Insights From Video Content" description: > analyze video clips into video insights report with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. marketers use it for extracting scene breakdowns and content summaries from videos β€” processing takes 30-60 seconds 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

> Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

  • "analyze a 3-minute product demo recording into a 1080p MP4"
  • "analyze this video and summarize what happens scene by scene"
  • "extracting scene breakdowns and content summaries from videos for marketers"

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

    Analyze Video β€” Extract Insights From Video Content

    This tool takes your video clips and runs AI video analysis through a cloud rendering pipeline. You upload, describe what you want, and download the result.

    Say you have a 3-minute product demo recording and want to analyze this video and summarize what happens scene by scene β€” the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

    Tip: shorter clips under 5 minutes get faster and more accurate analysis results.

    Matching Input to Actions

    User prompts referencing analyze video, 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.

    Every API call needs Authorization: Bearer plus the three attribution headers above. If any header is missing, exports return 402.

    Skill attribution β€” read from this file's YAML frontmatter at runtime:

  • X-Skill-Source: analyze-video
  • X-Skill-Version: from frontmatter version
  • X-Skill-Platform: detect from install path (~/.clawhub/ β†’ clawhub, ~/.cursor/skills/ β†’ cursor, else unknown)

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

    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=, 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

    • 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

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

    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)

    Common Workflows

    Quick edit: Upload β†’ "analyze this video and summarize what happens scene by scene" β†’ 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.

    Tips and Tricks

    The backend processes faster when you're specific. Instead of "make it look better", try "analyze this video and summarize what happens scene by scene" β€” concrete instructions get better results.

    Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

    MP4 with H.264 codec gives the most reliable analysis results across all video types.

    πŸ’‘ Examples

    > Ready when you are. Drop your video clips here or describe what you want to make.

    Try saying:

  • "analyze a 3-minute product demo recording into a 1080p MP4"
  • "analyze this video and summarize what happens scene by scene"
  • "extracting scene breakdowns and content summaries from videos for marketers"

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

    Analyze Video β€” Extract Insights From Video Content

    This tool takes your video clips and runs AI video analysis through a cloud rendering pipeline. You upload, describe what you want, and download the result.

    Say you have a 3-minute product demo recording and want to analyze this video and summarize what happens scene by scene β€” the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

    Tip: shorter clips under 5 minutes get faster and more accurate analysis results.