Video Editor Career

Skip the learning curve of professional editing software. Describe what you want — cut the awkward pauses, add lower-thirds titles, and export a clean reel f...

Security Scan

The skill's requested token and cloud API calls match its editing purpose, but there are inconsistencies (missing homepage/owner provenance, a mismatched configPaths declaration, and the skill will upload your raw videos to an external API) that merit caution before installing.

Purpose & Capability

The skill claims to perform cloud-based AI video editing and the SKILL.md only requires a single NEMO_TOKEN and network calls to a nemo-video API — this is coherent with the stated purpose. However the frontmatter metadata mentions a configPaths entry (~/.config/nemovideo/) while the package metadata shown to the registry listed no required config paths; that mismatch is unexplained. The skill also attempts to detect the agent install path for attribution, which is plausible for analytics but is extra filesystem probing beyond pure editing functionality.

Instruction Scope

Instructions are detailed and stay within the editing workflow: check NEMO_TOKEN, optionally obtain an anonymous token from the provider, create sessions, upload video files, use SSE for edits, poll render status, and return download URLs. These actions are expected for a remote rendering service. The skill does instruct the agent to detect install path and to read its YAML frontmatter for attribution headers — these involve reading local paths/files and are not strictly necessary for editing, so they are worth noting to users.

Install Mechanism

No install spec or external packages are declared; this is an instruction-only skill (no code files). That minimizes risk from arbitrary code installation.

Credentials

Only one credential is required (NEMO_TOKEN) and it is the declared primary credential, which matches the cloud API usage. The SKILL.md also describes obtaining an anonymous token if none is present. The unexplained configPaths in the frontmatter (~/.config/nemovideo/) and the instruction to detect install path are additional accesses that were not declared in registry-level requirements — this inconsistency reduces transparency.

Persistence & Privilege

The skill is not always-included and does not request elevated or persistent platform privileges. It does not declare writing to other skills' config or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with other high-risk flags here.

What to consider before installing

This skill appears to do what it says: it uploads your raw video to a remote service (mega-api-prod.nemovideo.ai) for cloud rendering and requires a NEMO_TOKEN. Before installing, consider: (1) Privacy/ownership — your raw footage will be sent to an external API; verify the provider, retention policy, and whether sending sensitive content is acceptable. (2) Provenance — there is no homepage or clear owner info in the registry metadata; verify the service (NEMO) independently to ensure it's legitimate. (3) Token handling — the skill will accept an existing NEMO_TOKEN or obtain an anonymous token for you; prefer using short-lived or scoped tokens and avoid sharing long-lived credentials. (4) Minor inconsistencies — the skill frontmatter references a config path (~/.config/nemovideo/) and does install-path detection that weren't declared at registry level; ask the author why these are needed. If you need higher assurance, request the skill's homepage or source, confirm the API domain and privacy policy, and test with non-sensitive sample videos first.

Getting Started

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

Try saying:

• "edit my raw footage"
• "export 1080p MP4"
• "cut the awkward pauses, add lower-thirds"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Video Editor Career — Edit and Export Portfolio Videos

Send me your raw footage and describe the result you want. The AI-assisted video editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute interview recording, type "cut the awkward pauses, add lower-thirds titles, and export a clean reel for my portfolio", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 2 minutes process faster and are ideal for portfolio samples.

Matching Input to Actions

User prompts referencing video editor career, 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: video-editor-career
• 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 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)

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 awkward pauses, add lower-thirds titles, and export a clean reel for my portfolio" → 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 awkward pauses, add lower-thirds titles, and export a clean reel for my portfolio" — 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 widest compatibility across job application platforms.