Bing Video

Turn a 2-minute recorded lecture clip into 1080p compiled video clips just by typing what you need. Whether it's finding and assembling relevant video conten...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-compile service: it only needs a service token (NEMO_TOKEN), uploads user-provided video, and talks to the nemo video API — there are minor metadata inconsistencies but no evidence of unrelated credential access or suspicious install behavior.

Purpose & Capability

The skill name/description (cloud video search + compile) aligns with the runtime instructions that upload clips, create a session, run SSE-based edits, and request exports from https://mega-api-prod.nemovideo.ai. Requiring a NEMO_TOKEN and an anonymous-token fallback is coherent for a hosted service. Note: the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this is an internal inconsistency (likely harmless) that should be clarified.

Instruction Scope

SKILL.md stays within the stated scope: it instructs creating/using a service token, creating a session, uploading video files, issuing edits via SSE, polling export status, and returning download URLs. It does not instruct reading unrelated system files or other environment variables. It does recommend treating some tool outputs as internal and not forwarding them to the chat, which is reasonable for internal API events but merits awareness.

Install Mechanism

This is instruction-only with no install spec or code files, so nothing is written to disk or downloaded by the skill itself — lowest-risk install posture.

Credentials

Only one credential is required: NEMO_TOKEN (declared as primary). That matches the described behavior (Bearer token sent to the nemo API). The skill also documents an anonymous-token flow that generates a temporary token if none is present — expected but worth noting because the skill will obtain and use a token automatically if you don't supply one. The SKILL.md frontmatter lists a config path; the registry metadata omitted it — clarify whether local config/token files may be read/written.

Persistence & Privilege

The skill is not always-enabled and has no install-time persistence. It can be invoked autonomously (platform default) but does not request system-wide config changes or cross-skill credentials.

Assessment

This skill appears to do what it says: it uploads video clips to a nemo-video cloud service, uses a bearer token (NEMO_TOKEN) or automatically obtains a 7-day anonymous token, and returns rendered download URLs. Before installing, consider: (1) you will be uploading video files to https://mega-api-prod.nemovideo.ai — don't upload sensitive or private footage unless you trust the operator; (2) the skill will send whatever NEMO_TOKEN you provide to that domain as Authorization: Bearer — ensure the token's scope is limited; (3) clarify the metadata inconsistency about a local config path (~/.config/nemovideo/) so you know whether local token/config files might be read or written; (4) there's no source/homepage listed for the skill — if provenance matters, ask the publisher for a homepage, privacy policy, or contact info before using.

Getting Started

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

Try saying:

• "generate my video clips"
• "export 1080p MP4"
• "find and compile video clips related"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Bing Video — Search and Compile Video Clips

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

Say you have a 2-minute recorded lecture clip and want to find and compile video clips related to space exploration — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: shorter search queries return more precise video matches.

Matching Input to Actions

User prompts referencing bing 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.

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	bing-video
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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.

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

Common Workflows

Quick edit: Upload → "find and compile video clips related to space exploration" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "find and compile video clips related to space exploration" — 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.