Video Editing With Microsoft

edit raw video footage into edited MP4 clips with this skill. Works with MP4, MOV, AVI, WMV files up to 500MB. Windows users and Microsoft 365 creators use i...

Security Scan

The skill's runtime instructions are coherent for a third‑party video editing service (nemovideo.ai) but the skill name and some metadata misleadingly invoke Microsoft and there are minor metadata inconsistencies; you should verify the external service and privacy implications before uploading files or providing tokens.

Purpose & Capability

The skill is named and marketed as "Video Editing With Microsoft" but every runtime endpoint and the required credential (NEMO_TOKEN) point to a third‑party service (mega-api-prod.nemovideo.ai). That naming is misleading; Microsoft credentials are not requested and there is no Microsoft API usage. Also the SKILL.md metadata lists a config path (~/.config/nemovideo/) even though the registry metadata reported no required config paths — an internal inconsistency.

Instruction Scope

The SKILL.md instructs the agent to obtain or use NEMO_TOKEN, create sessions, upload user files, stream SSE, poll render status, and include custom headers. All of these actions are consistent with a cloud video‑editing service. The instructions do not request unrelated system files or other credentials, but they do direct user video files and session tokens to an external domain (nemovideo.ai), which has privacy implications.

Install Mechanism

The skill is instruction‑only with no install spec and no code files, so nothing is downloaded or written by an installer. This lowers code‑supply risk, though network activity will occur at runtime when the agent calls the external API.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportionate to calling a cloud API. However, the skill suggests generating an anonymous token automatically if none is provided, and the metadata mentions a local config path (~/.config/nemovideo/) that may imply storing credentials or state — this conflicts with registry metadata and should be clarified. Providing NEMO_TOKEN grants the service access to uploads and rendering on your behalf.

Persistence & Privilege

always:false and normal autonomous invocation are fine. There is no explicit install or request for system‑wide privileges. Still, the SKILL.md references saving a session_id and a config path in metadata, which could imply local persistence of session/state; the registry did not list config paths, so clarify whether tokens/session data are written to disk.

What to consider before installing

This skill will upload your videos and use a NEMO_TOKEN to call a third‑party API at mega-api-prod.nemovideo.ai — despite the Microsoft‑focused name. Before installing: 1) Verify the external domain and service (privacy policy, who runs nemovideo.ai). 2) Do not provide Microsoft credentials (none are required). 3) Prefer testing with non‑sensitive sample videos to confirm behavior. 4) Ask the skill author whether tokens or session data are stored locally (~/.config/nemovideo/) and how long uploaded media are retained or deleted. 5) If you expected official Microsoft integration, consider using Microsoft's documented tools/APIs instead. If these points aren’t clarified, treat the skill as potentially misleading and avoid uploading private content or long‑lived tokens.

Getting Started

Share your raw video footage and I'll get started on AI-assisted video editing. Or just tell me what you're thinking.

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "trim the intro, add transitions, and"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Editing with Microsoft — Edit and Export Microsoft Videos

This tool takes your raw video footage and runs AI-assisted video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute screen recording from Microsoft Clipchamp and want to trim the intro, add transitions, and export as a clean MP4 — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: WMV files from older Windows tools convert cleanly — just keep them under 500MB.

Matching Input to Actions

User prompts referencing video editing with microsoft, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-editing-with-microsoft, 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.

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

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the intro, add transitions, and export as a clean MP4" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across Windows, web, and mobile platforms.

Common Workflows

Quick edit: Upload → "trim the intro, add transitions, and export as a clean MP4" → 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.