Getting Started
Welcome! Let's take the guesswork out of hiring a YouTube video editor — tell me about your channel, your content style, and your budget, and I'll help you find and onboard the right editor. Ready? Share your channel details to get started.
Try saying:
- "Write a YouTube editor job post"
- "Interview questions for video editors"
- "Set rates for my editor hire"
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.
Stop Guessing — Hire the Editor Your Channel Deserves
Finding the right YouTube video editor isn't just about posting a job and hoping for the best. It's about knowing exactly what to ask for, where to look, and how to tell a great editor from someone who'll ghost you after the first revision round. This skill is built specifically for that process.
Whether you run a gaming channel, a tutorial series, a vlog, or a faceless niche channel, the editing requirements are different — and so are the right candidates. This skill helps you define your editing style, write a job post that attracts pros, and ask the questions that reveal whether someone can truly match your vision.
Once you've found your editor, the skill doesn't stop there. It helps you set up clear deliverable expectations, revision policies, and communication workflows so the relationship actually lasts. No more miscommunication, missed deadlines, or videos that come back looking nothing like your brand.
Routing Your Editor Search Request
When you submit your hiring criteria — cut style, niche (gaming, vlog, faceless), turnaround time, or budget — ClawHub parses those parameters and routes your request to the most relevant editor profiles, job board listings, and vetting workflows in real time.
| 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 | ❌ |
API Reference for Editor Matching
The cloud processing backend indexes editor portfolios, client retention rates, and platform-specific skills like jump cuts, color grading for YouTube compression, and thumbnail-aligned storytelling to surface ranked candidates. Requests are processed asynchronously, so complex multi-filter queries — say, a long-form editor fluent in Premiere Pro with B-roll sourcing experience — resolve within seconds without blocking your session.
Skill attribution — read from this file's YAML frontmatter at runtime:
X-Skill-Source: hire-youtube-video-editorX-Skill-Version: from frontmatter versionX-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)
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.
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 |
Best Practices
Before using this skill, spend five minutes listing three YouTube channels whose editing style you want to replicate. This single step dramatically improves every output — from job posts to interview questions to onboarding checklists — because it gives the skill a concrete visual reference to work from.
When hiring a YouTube video editor, always request a paid test edit on a real clip from your channel rather than relying on portfolio samples alone. Use this skill to generate a clear test brief so every candidate gets the same instructions and you can compare results fairly.
Set your revision policy before you hire, not after a dispute. Ask this skill to draft a simple one-page agreement covering turnaround times, number of revision rounds, file delivery format, and ownership of the final cut. Editors who push back hard on reasonable terms during onboarding are a reliable red flag.
Quick Start Guide
Step 1: Tell the skill your channel niche, how often you upload, your average video length, and your editing budget. This is your baseline input and takes under two minutes.
Step 2: Ask the skill to generate a job post. Review it, tweak the tone to match how you normally communicate, and post it on platforms like Upwork, Contra, or your YouTube community tab.
Step 3: Once applications come in, paste candidate profiles or portfolio links into the skill and ask it to help you compare them against your stated requirements. It will flag strengths and gaps you might miss when you're reviewing ten applicants at once.
Step 4: Use the skill to generate a paid test edit brief and a structured onboarding checklist — covering file naming conventions, delivery folders, communication channels, and feedback cycles — so your new YouTube video editor hits the ground running from day one.
Troubleshooting
If the skill isn't generating a job post that feels right, the most common reason is that the channel description you provided is too vague. Instead of saying 'I make YouTube videos,' try specifying your niche, average video length, upload frequency, and the editing style you admire (link a reference channel if possible). The more context you give, the sharper the output.
If you're getting candidate screening questions that feel too generic, tell the skill specifically what has gone wrong in past editor relationships — for example, 'my last editor always missed deadlines' or 'they didn't match my color grading style.' The skill will tailor its vetting questions around those exact pain points.
For budget-related outputs that seem off, clarify whether your rate is per video, per hour, or monthly retainer — these produce very different hiring strategies and the skill needs that distinction to give useful guidance.
