Video Editor Entry Level Jobs

edit raw video clips into polished edited clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. aspiring video editors use it for editing...

Security Scan

The skill's declared requirements and runtime instructions are consistent with a cloud-based AI video editing service, but there are small privacy/operational notes to consider (automatic backend connection, token/session storage, and a service-specific config path).

Purpose & Capability

The name/description (cloud video editing) aligns with the declared requirement (NEMO_TOKEN) and the SKILL.md API endpoints. Required credential is the service token the backend expects. No unrelated credentials or binaries are requested.

Instruction Scope

Instructions stay focused on editing: creating/using a session token, uploading files, SSE editing, polling render status and returning a download URL. Two things to note: (1) the skill auto-connects to the backend on first open (it will generate an anonymous token if NEMO_TOKEN is not present), which means network calls may occur before explicit user action; (2) the skill expects to store and reuse session_id/token but does not specify storage location/details (metadata references a config path). There are no instructions to read unrelated system files or exfiltrate data to third parties.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing is written to disk by installation. That minimizes install-time risk.

Credentials

Only one environment variable is required (NEMO_TOKEN), which is appropriate for a service-authenticated API. The metadata also lists a service-specific config path (~/.config/nemovideo/); that is plausible for caching tokens/sessions but is not strictly necessary and should be clarified. No unrelated secrets or system credentials are requested.

Persistence & Privilege

The skill is not always-enabled and uses normal autonomous invocation settings. It does request persistent session state (session_id/token) for workflow continuity, but it does not ask to modify other skills or system-wide settings.

Assessment

This skill appears to do what it says: it talks to a single backend (mega-api-prod.nemovideo.ai) to create a session, accept uploads, run edits, and return a download URL. Before installing or using it, consider the following: - Privacy: uploading video will send your media to the remote service. Avoid uploading sensitive or private footage unless you trust the service and its privacy policy. - Automatic connection: the skill may automatically create an anonymous token and connect the first time it is opened. If you prefer to control network activity, set NEMO_TOKEN yourself or avoid opening the skill until ready. - Token/session storage: the skill instructs storing session_id and token for later calls and metadata lists a config path (~/.config/nemovideo/). Ask or verify where tokens and session data are stored and for how long they persist; clear them if you want to revoke access. - Domain trust: the backend domain is not described beyond the SKILL.md. If you need higher assurance, request the skill owner or vendor info, privacy policy, or a homepage before uploading sensitive content. - No local installs: the skill does not install binaries or run local code, which reduces install-time risk, but network calls are the primary surface to review. If these behaviours are acceptable (remote processing of uploaded media and ephemeral tokens), the skill is coherent with its stated purpose. If you need more assurance, ask the maintainer to clarify token storage, retention, and the service's privacy/security practices.

Getting Started

Send me your raw video clips and I'll handle the AI video editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute interview recording shot on a phone into a 1080p MP4"
• "trim the pauses, add lower-third titles, and export a clean final cut"
• "editing raw footage into clean finished videos without professional software for aspiring video editors"

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 Entry Level Jobs — Edit and Export Portfolio Videos

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

A quick example: upload a 2-minute interview recording shot on a phone, type "trim the pauses, add lower-third titles, and export a clean final cut", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 3 minutes process faster and are great for building quick portfolio samples.

Matching Input to Actions

User prompts referencing video editor entry level jobs, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-editor-entry-level-jobs, 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).

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.

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.

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

Common Workflows

Quick edit: Upload → "trim the pauses, add lower-third titles, and export a clean final cut" → 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 "trim the pauses, add lower-third titles, and export a clean final cut" — 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 submission portals and client reviews.