Youtube Video Editor Effects

Skip the learning curve of professional editing software. Describe what you want — add cinematic color grading, transitions, and motion blur effects between...

Security Scan

The skill's instructions, required token, and cloud API usage are coherent with a cloud-based AI video-effects service, with only minor metadata inconsistencies (no code is installed on the host).

Purpose & Capability

The name/description match the instructions for a cloud-based AI video effects pipeline. Requesting a single service token (NEMO_TOKEN) and describing upload/render endpoints is appropriate. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) but the registry metadata reported no required config paths — it's plausible the skill wants a local cache, but the registry and frontmatter disagree.

Instruction Scope

Runtime instructions focus on authenticating, creating sessions, uploading media, SSE streaming, render polling, and returning download URLs — all expected for this purpose. The only additional action of note is 'auto-detect X-Skill-Platform from install path', which implies reading the agent's install path; this is minor but should be limited to deriving the header value. The skill instructs not to expose tokens or raw API output.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk or downloaded during install. This is the lowest-risk install model.

Credentials

Only one credential (NEMO_TOKEN) is required and is the primary credential — this is proportionate to a cloud API client. The skill also documents a flow to acquire an anonymous token from the vendor if NEMO_TOKEN is missing; that behavior is reasonable but means the agent will contact an external API and receive a short-lived credential. The frontmatter config path (~/.config/nemovideo/) is not reflected in the registry metadata, which could indicate the skill intends to read/write a local token cache — this should be clarified.

Persistence & Privilege

always is false and model invocation is permitted (platform defaults). The skill does not request elevated or permanent platform privileges. No instructions attempt to modify other skills or system-wide settings.

Assessment

This skill appears to do what it says: upload user video files to a third-party cloud service (mega-api-prod.nemovideo.ai), run AI effects, and return a download URL. Before installing or using it, consider: (1) Privacy: your videos will be uploaded to an external service—check the vendor's privacy/retention policy and whether you’re comfortable with that. (2) Credentials: the skill uses a NEMO_TOKEN; it can also obtain an anonymous token automatically by calling the vendor's auth endpoint — you may prefer to supply your own token rather than let the skill auto-provision one. (3) Local files/config: the SKILL.md references a local config path (~/.config/nemovideo/) not declared in the registry — ask the publisher whether the skill will read/write that directory and why. (4) Attribution headers: the skill requires specific X-Skill-* headers; the agent will derive one value from its install path — confirm that behavior is acceptable. (5) Service trust & billing: anonymous tokens are limited (100 free credits, 7-day expiry) and some responses indicate subscription/402 behavior — confirm pricing/limits. Finally, the skill has no install code (lower installation risk) but will transmit your media and create short-lived credentials on an external domain; verify the service domain and publisher reputation before uploading sensitive content.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "add cinematic color grading, transitions, and"

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.

YouTube Video Editor Effects — Add Effects and Export Videos

This tool takes your video clips and runs AI effects editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute YouTube vlog in MP4 format and want to add cinematic color grading, transitions, and motion blur effects between scenes — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster and let you preview effects quickly.

Matching Input to Actions

User prompts referencing youtube video editor effects, 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	youtube-video-editor-effects
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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)

Common Workflows

Quick edit: Upload → "add cinematic color grading, transitions, and motion blur effects between scenes" → 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 "add cinematic color grading, transitions, and motion blur effects between scenes" — 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 YouTube upload compatibility.