Video Editor Salary

Skip the learning curve of professional editing software. Describe what you want — create a portfolio video showcasing my editing skills to help me land high...

Security Scan

The skill is internally consistent with its stated purpose: it needs a NEMO_TOKEN to call the nemovideo cloud API, will (optionally) obtain an anonymous token, and uploads user media to that backend for processing.

Purpose & Capability

Name/description (cloud video editing / portfolio creation) aligns with required credential (NEMO_TOKEN) and the documented API endpoints; the declared config path (~/.config/nemovideo/) is plausible for storing session/token state used by the service.

Instruction Scope

Runtime instructions mostly stay within the editing use case: creating anonymous tokens, creating a session, uploading media, starting renders, and polling state/SSE. Important behavioral notes: the skill auto-generates an anonymous token if NEMO_TOKEN is not present and instructs the agent to upload user files to a third-party API; it also instructs not to display raw API/token values to users. These are expected for cloud-based editing but are privacy-relevant actions the user should know about.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk. No downloads or package installs are requested.

Credentials

Only one required credential (NEMO_TOKEN / primaryEnv) which is appropriate for calling the stated API. The metadata also declares a config path (~/.config/nemovideo/) which is reasonable for storing session state but the SKILL.md does not specify exactly where session/token persistence occurs — minor mismatch but not strongly suspicious.

Persistence & Privilege

always is false and the skill does not request elevated platform-wide privileges or modifications to other skills. It will create and use an API token and session for its own operations; autonomous invocation remains enabled (platform default) but that is expected behavior for a usable skill.

Assessment

This skill will upload your video footage and any text you provide to mega-api-prod.nemovideo.ai for cloud processing and will create an anonymous API token if you haven't supplied NEMO_TOKEN. That behavior is consistent with a cloud editor, but you should: (1) only upload material you are comfortable sharing with a third party (resumes may contain PII), (2) consider supplying your own NEMO_TOKEN only if you trust the service, (3) be aware the skill may persist session/token state (metadata lists ~/.config/nemovideo/), and (4) review the service's privacy/terms before using for sensitive content. If you want more assurance, ask the skill author for an explicit privacy statement or a way to opt out of automatic token creation and persistence.

Getting Started

Share your resume or footage and I'll get started on AI career content creation. Or just tell me what you're thinking.

Try saying:

• "create my resume or footage"
• "export 1080p MP4"
• "create a portfolio video showcasing my"

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.

Video Editor Salary — Build Reels That Get Hired

Drop your resume or footage in the chat and tell me what you need. I'll handle the AI career content creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute screen recording of a video editing reel, ask for create a portfolio video showcasing my editing skills to help me land higher-paying jobs, 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 — keep your demo reel under 90 seconds — hiring managers decide fast.

Matching Input to Actions

User prompts referencing video editor salary, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-editor-salary
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.

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.

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

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)

Common Workflows

Quick edit: Upload → "create a portfolio video showcasing my editing skills to help me land higher-paying jobs" → 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 "create a portfolio video showcasing my editing skills to help me land higher-paying jobs" — 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 across job portals and email attachments.