What Is Video Clip Example

Turn a 30-second screen recording or phone video into 1080p sample video clips just by typing what you need. Whether it's understanding what a video clip is...

Security Scan

The skill's requests and runtime instructions are generally consistent with a cloud video-clip export tool, but there are a few small inconsistencies and privacy considerations you should review before installing.

Purpose & Capability

The skill claims to create/export short 1080p clips and only requires a single API token (NEMO_TOKEN), which fits the stated purpose. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) and refers to detecting install paths (~/.clawhub/, ~/.cursor/skills/) to set an attribution header — these are not strictly necessary for basic clip export and are inconsistent with the registry summary that listed no required config paths.

Instruction Scope

All runtime instructions map to the described cloud service: session creation, SSE-based messaging, multipart video uploads, credit/status checks, and export polling. The skill expects to upload user video files to mega-api-prod.nemovideo.ai and to store a session_id for subsequent requests. It does not instruct the agent to read unrelated local files, other credentials, or external endpoints unrelated to the service.

Install Mechanism

This is an instruction-only skill with no install spec and no code written to disk, which is the lowest-risk model. There is no package download or extraction.

Credentials

The only declared credential is NEMO_TOKEN, which is appropriate for an API-backed service. Two notes: (1) the skill will attempt to obtain an anonymous NEMO_TOKEN automatically if one isn't present (POST to the service), which means it may create/store ephemeral credentials without an explicit separate user action; (2) the SKILL.md metadata lists a config path (~/.config/nemovideo/) not surfaced in the registry entry — this mismatch should be clarified.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and only asks to store a session_id for the session it creates. Autonomous invocation is allowed by default but is not combined with broad access or system-wide persistence.

Assessment

This skill appears to do what it says: upload short videos to a cloud rendering API and return exported clips. Before installing, consider: (1) The skill will upload your media to https://mega-api-prod.nemovideo.ai — do not send sensitive videos you don't want off your device. (2) It will create an anonymous API token automatically if NEMO_TOKEN is not set; if you prefer control, set a token manually or refuse automatic token creation. (3) There's a minor metadata mismatch (a config path is listed in the SKILL.md but not in the registry summary) and the skill attempts to detect the agent install path for an attribution header — ask the publisher to clarify why that local-path detection is needed. (4) The skill has no homepage and the source is unknown; if you need stronger assurance, request provenance or documentation from the publisher before trusting it with private content.

Getting Started

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

Try saying:

• "create my video clips"
• "export 1080p MP4"
• "show me an example of a"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

What Is a Video Clip Example — Create and Export Sample Clips

Drop your video clips in the chat and tell me what you need. I'll handle the clip example generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 30-second screen recording or phone video, ask for show me an example of a video clip I can create from this footage, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — start with a clip under 60 seconds to get a fast, clear example output.

Matching Input to Actions

User prompts referencing what is video clip example, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is what-is-video-clip-example, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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.

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.

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "show me an example of a video clip I can create from this footage" — 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.

Common Workflows

Quick edit: Upload → "show me an example of a video clip I can create from this footage" → Download MP4. Takes 20-40 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.