Editor And Downloader

Skip the learning curve of professional editing software. Describe what you want — trim the intro, add text overlays, and download as MP4 — and get edited do...

Security Scan

The skill's behavior (uploading videos to an external API using a token) matches its stated purpose, but there are metadata inconsistencies and an unknown third-party endpoint — verify origin and token use before installing.

Purpose & Capability

Name/description (cloud video editing + download) align with the runtime instructions (upload files, create session, render/export). Requiring a NEMO_TOKEN is reasonable for a hosted editing service. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained and worth clarifying.

Instruction Scope

Runtime instructions are narrowly focused on authenticating, creating a session, uploading video files, and polling for render results on the nemo API. They do not ask the agent to read unrelated system files or other environment variables. They do instruct generating an anonymous token if NEMO_TOKEN is absent and to include specific attribution headers on each request.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. This is the lowest-risk install mechanism.

Credentials

The declared primary credential is NEMO_TOKEN, which is appropriate for calling the service. However, the SKILL.md frontmatter's mention of a config path (~/.config/nemovideo/) (not reflected in registry requirements) suggests possible undisclosed local config access. Also, uploaded videos (potentially sensitive) will be sent to an external domain; ensure the token scope and privacy policy are acceptable.

Persistence & Privilege

always:false and normal model invocation; the skill does not request permanent/always-on inclusion or modifications to other agent configs in the instructions. No privileged persistence behavior is evident.

What to consider before installing

This skill appears to do what it says (upload a clip, call a cloud render API, and return a download), but two things to check before installing: (1) confirm the skill's publisher and the legitimacy of the API host (mega-api-prod.nemovideo.ai) — unknown domains can be risky; (2) clarify the configPath discrepancy in SKILL.md (it suggests access to ~/.config/nemovideo/) and confirm whether the skill will read any local files beyond the user-supplied videos. Treat NEMO_TOKEN as sensitive (it authorizes uploads/renders), test with non-sensitive videos first, and review the service's privacy/retention policy for uploaded media.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI editing and downloading.

Try saying:

• "edit a 3-minute YouTube clip saved locally into a 1080p MP4"
• "trim the intro, add text overlays, and download as MP4"
• "editing videos and downloading the final cut instantly for content creators"

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.

Editor and Downloader — Edit and Download Videos Fast

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

Here's a typical use: you send a a 3-minute YouTube clip saved locally, ask for trim the intro, add text overlays, and download as MP4, and about 30-60 seconds 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 2 minutes process and download significantly faster.

Matching Input to Actions

User prompts referencing editor and downloader, 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.

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

Header	Value
X-Skill-Source	editor-and-downloader
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the intro, add text overlays, and download as MP4" — 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 devices and platforms.

Common Workflows

Quick edit: Upload → "trim the intro, add text overlays, and download as MP4" → Download MP4. Takes 30-60 seconds 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.