Youtube Video Editor For Hire

edit raw video footage into polished edited videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. YouTubers use it for editing raw YouTub...

Security Scan

The skill's declared purpose (AI video editing) matches most of its instructions, but there are inconsistencies and transparency concerns (metadata vs registry mismatch about config paths, instruction to hide technical details, and automatic anonymous-token acquisition) that warrant caution before installing.

Purpose & Capability

Name/description align with the runtime instructions (upload video, create session, render/export). Requiring NEMO_TOKEN as the primary credential is coherent. However, the SKILL.md frontmatter declares a configPaths entry (~/.config/nemovideo/) while the registry metadata lists no required config paths — this discrepancy is unexplained and could indicate either stale metadata or an undocumented filesystem access requirement.

Instruction Scope

Instructions stay largely within video-editing scope (session creation, upload, SSE editing, render/polling). Two things to notice: (1) the skill instructs the agent to generate an anonymous token and call an external auth endpoint when no NEMO_TOKEN is present (meaning network calls will happen automatically), and (2) the SKILL.md explicitly tells the agent to 'keep the technical details out of the chat' which reduces transparency for the user about what the skill is doing.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. This minimizes installation-time risk.

Credentials

Only one declared env var (NEMO_TOKEN) which is proportional to an API-backed service. But the frontmatter also lists a config path (~/.config/nemovideo/) not shown in the registry metadata, creating inconsistency about what filesystem access is required. Also the skill will create and use an anonymous token if none is provided, meaning it will perform external auth calls and obtain a temporary credential without the user supplying one explicitly.

Persistence & Privilege

always:false and no install behavior that modifies other skills or system settings. The skill does create sessions on the remote service (server-side jobs may persist there), but it does not request elevated persistent presence on the agent.

What to consider before installing

This skill appears to do what it says (send videos to a cloud API for editing) but there are a few things to consider before installing or using it: - NEMO_TOKEN is the primary credential: only provide it if you trust the remote service. If you do not want to give a permanent token, rely on the anonymous token path, but be aware the skill will automatically request one from https://mega-api-prod.nemovideo.ai when no token is present. - Metadata mismatch: the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while the registry metadata does not. Ask the publisher whether the skill will read that directory (which could contain local credentials or config) and why. - Transparency: the instructions explicitly direct the agent to 'keep technical details out of the chat.' That hides API calls and tokens from users and makes auditing harder. Prefer skills that are explicit about what they send and store. - Data exposure: uploaded videos (up to 500MB) will be transmitted to a third-party domain. Confirm the service's privacy policy, retention practices, and whether uploaded content may be stored or used for model training. - Lack of provenance: there is no homepage or source/repository for the skill. If you need stronger assurance, request the skill's source or a publisher contact and a privacy/security statement. What would change my assessment to benign: availability of the skill's source or a trustworthy homepage, reconciliation of the configPaths/registry metadata mismatch, explicit documentation of token scope/storage and data-retention/privacy policies, or confirmation that the skill does not read arbitrary local config files beyond what's necessary. Without that, treat the skill as functional but with transparency and data-exposure concerns.

Getting Started

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

Try saying:

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

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

YouTube Video Editor for Hire — Edit and Export YouTube Videos

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 10-minute unedited YouTube vlog recording, ask for trim the dead air, add transitions, and put my channel intro at the start, 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 — shorter clips under 5 minutes process significantly faster and use fewer credits.

Matching Input to Actions

User prompts referencing youtube video editor for hire, 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.

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.

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

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

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.

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

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

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.

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)

Common Workflows

Quick edit: Upload → "trim the dead air, add transitions, and put my channel intro at the start" → 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 dead air, add transitions, and put my channel intro at the start" — 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 on YouTube.