To Video Professional

content creators and marketers convert raw video footage into professional edited videos using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, renders o...

Security Scan

The skill's instructions largely match a cloud video-rendering integration, but there are provenance inconsistencies and privacy/behavior details you should understand before installing.

Purpose & Capability

Name/description claim cloud GPU video editing and the SKILL.md instructs calls to a video-processing API (nemovideo endpoints) and upload/export flows — this is coherent with the stated purpose. However the package has no homepage or known publisher and the frontmatter references a config path (~/.config/nemovideo/) which is not present in the registry metadata, an internal inconsistency about what the skill expects to access.

Instruction Scope

Runtime instructions tell the agent to obtain or reuse an Authorization token (NEMO_TOKEN), create sessions, stream SSE, upload user files, and poll rendering endpoints. Uploading user video files to an external domain (mega-api-prod.nemovideo.ai) is necessary for the stated function but is a privacy/attack surface you should consider. The skill also instructs the agent to detect install path and read YAML frontmatter for attribution headers — reading the install path is somewhat outside pure editing logic and could expose local environment structure.

Install Mechanism

No install spec and no code files — instruction-only skill. Lowest installation risk because nothing is downloaded or written by an installer. All runtime behavior happens via API calls described in SKILL.md.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which matches the API Bearer token used throughout the instructions. That is proportionate. Minor inconsistency: SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata in the manifest showed no required config paths — this mismatch should be clarified.

Persistence & Privilege

Skill is not always-enabled and doesn't request elevated platform privileges. It instructs saving a session_id and using/storing a token for API calls (normal for an API integration). Autonomous invocation is allowed (default) but not combined with other high-risk flags.

What to consider before installing

This skill appears to implement a cloud video-editing integration and will upload any video you give it to an external service (mega-api-prod.nemovideo.ai). Before installing: 1) Verify the publisher or service (there is no homepage or known owner listed). 2) Understand privacy: do not upload sensitive or private footage until you trust the service. 3) Prefer supplying your own NEMO_TOKEN only if you control/trust the account; anonymous tokens are short-lived and require posting a UUID to the external endpoint. 4) Ask the publisher to confirm the conflicting metadata (SKILL.md lists ~/.config/nemovideo/ but the registry metadata shows none) and whether any tokens/session IDs are persisted to disk. 5) Test the skill with non-sensitive, short clips first. If you want, provide the SKILL.md author/publisher info and I can re-evaluate with that provenance.

Getting Started

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

Try saying:

• "convert my raw video footage"
• "export 1080p MP4"
• "cut the pauses, add lower thirds,"

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.

To Video Professional — Convert Raw Footage to Pro Videos

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

Say you have a 3-minute unedited interview recording and want to cut the pauses, add lower thirds, and color grade for a professional look — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster and give more precise AI edits.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: to-video-professional
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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.

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

Common Workflows

Quick edit: Upload → "cut the pauses, add lower thirds, and color grade for a professional look" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the pauses, add lower thirds, and color grade for a professional look" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best balance of quality and file size.