Bing Ai Video Creator

Cloud-based bing-ai-video-creator tool that handles generating videos from text prompts or images. Upload JPG, PNG, MP4, MOV files (up to 200MB), describe wh...

Security Scan

The skill mostly fits a cloud video-generation use case, but there are multiple mismatches and automatic network/file-access behaviors that don't fully align with its name and registry metadata and deserve caution.

Purpose & Capability

The skill is named "Bing Ai Video Creator" but all runtime instructions and the auth token (NEMO_TOKEN) point to a third-party service at mega-api-prod.nemovideo.ai (Nemo). That naming mismatch (Bing vs Nemo) is misleading. The SKILL.md frontmatter also declares a config path (~/.config/nemovideo/) while the registry summary showed no required config paths — an internal metadata inconsistency.

Instruction Scope

Instructions direct the agent to perform network calls (obtain anonymous token, create sessions, upload files, poll render status) and to read/write session state and detect install paths. Uploading user files to the external API is expected for a cloud render skill, but the skill also instructs checking local install paths and a config directory, which broadens filesystem access beyond purely handling explicit user-provided media. It will automatically obtain an anonymous token and create a session if NEMO_TOKEN is absent, which means outbound network activity can occur on first use without explicit user approval.

Install Mechanism

This is instruction-only with no install spec or code files, so nothing is written to disk by an installer. That is low-risk from an install-mechanism perspective.

Credentials

The sole required environment variable is NEMO_TOKEN, which is reasonable for authenticating to the described API. However, the SKILL.md also references a config path (~/.config/nemovideo/) that could contain credentials or data; that extra filesystem access was not reflected in the registry summary and is not justified in the top-level description.

Persistence & Privilege

always is false and the skill does not request permanent/force-included presence. It will, however, autonomously perform initial authentication network calls if NEMO_TOKEN isn't present (normal for many integrations but worth user awareness).

What to consider before installing

This skill appears to implement a Nemo-backed cloud video renderer but is marketed as "Bing Ai Video Creator" — that mismatch is suspicious. Before installing or supplying credentials: 1) Confirm the publisher and privacy/terms for mega-api-prod.nemovideo.ai and why the skill uses "Bing" in its name. 2) Ask where NEMO_TOKEN and session IDs are stored (memory only vs written to ~/.config/nemovideo/). 3) If you plan to upload sensitive media, understand uploads go to the external API and may persist there. 4) Consider not setting a long-lived NEMO_TOKEN in your environment; prefer ephemeral anonymous token behavior if acceptable. 5) If you need stronger assurance, request the skill author to clarify the configPath usage and to correct the metadata mismatch (configPaths and the skill name). If you are unsure, run the skill in a restricted environment or decline until the above are clarified.

Getting Started

Ready when you are. Drop your text prompts or images here or describe what you want to make.

Try saying:

• "generate three product photos and a short description into a 1080p MP4"
• "create a 30-second promotional video from these images with background music"
• "generating videos from text prompts or images for marketers, content creators, social media managers"

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.

Bing AI Video Creator — Create Videos from Text or Images

Drop your text prompts or images in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a three product photos and a short description, ask for create a 30-second promotional video from these images with background music, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter, clearer prompts produce more accurate results than long vague descriptions.

Matching Input to Actions

User prompts referencing bing ai video creator, 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 <NEMO_TOKEN> 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: bing-ai-video-creator
• 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":"<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.

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a 30-second promotional video from these images with background music" — concrete instructions get better results.

Max file size is 200MB. Stick to JPG, PNG, MP4, MOV for the smoothest experience.

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "create a 30-second promotional video from these images with background music" → 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.