Video Speed Changer

Get speed-adjusted clips ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "spe...

Security Scan

The skill's requests and runtime instructions line up with its stated purpose (uploading videos to a remote rendering API using a NEMO_TOKEN); nothing obviously unrelated or excessive is being requested, but it will upload your media to an external service and reads a couple of local paths for attribution which you should be aware of.

Purpose & Capability

The skill is an instruction-only connector to a remote 'nemovideo' render API and declares a single primary credential (NEMO_TOKEN) which is appropriate for authorizing API requests. Endpoints, actions (upload, SSE, render, credits), and required headers in the SKILL.md match the video-processing purpose. Minor metadata inconsistency: the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) while the registry 'Requirements' listed no required config paths.

Instruction Scope

Runtime instructions send user media and control messages to the remote API (expected). The skill also instructs the agent to read its own frontmatter for X-Skill-Version and to detect install path by checking well-known home paths (~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform. These filesystem checks are limited and attributable to header construction, but they are extra local reads beyond simple network calls and could reveal which client/platform is in use.

Install Mechanism

Instruction-only skill with no install spec or code files — nothing is written to disk or downloaded by the skill itself. This is the lowest-risk install posture.

Credentials

Requesting NEMO_TOKEN as the sole primary credential is proportionate for a remote rendering API. The instructions also describe creating an anonymous token from the service if no NEMO_TOKEN is provided. Be aware that any token grants the remote service access to uploaded media/operations and that tokens expire after 7 days per the doc. The frontmatter's configPaths suggests the skill might check ~/.config/nemovideo/ for stored credentials or settings — that may be reasonable but is not declared in the registry requirements (inconsistency noted).

Persistence & Privilege

The skill does not request always:true and is user-invocable. It does not ask to modify other skills or system-wide settings. The agent-autonomous invocation flag is left at the default (not a unique privilege) and is not concerning by itself.

Assessment

This skill will upload your video files to a third‑party service (mega-api-prod.nemovideo.ai) for server-side rendering and needs a NEMO_TOKEN to authorize requests. Before installing or invoking: 1) Verify you are comfortable having your videos sent to that external domain and review the service's privacy/terms if possible. 2) Only provide a NEMO_TOKEN you intend the skill to use; do not expose unrelated secrets. 3) Be aware the skill may read limited local paths (its own frontmatter and common install directories) to set attribution headers — this is for bookkeeping but is a local filesystem access to note. 4) If you prefer not to upload sensitive content, do not use this skill for those files. 5) If you need higher assurance, verify the service domain and organization behind it before submitting sensitive data. If you want me to, I can list the exact API calls and headers the skill will send so you can review them in more detail.

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

• "convert a 2-minute tutorial recording into a 1080p MP4"
• "speed up the video to 2x and slow down the intro to 0.5x"
• "speeding up or slowing down video playback rate for YouTubers, TikTok creators, educators"

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.

Video Speed Changer — Adjust Video Speed and Export

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

A quick example: upload a 2-minute tutorial recording, type "speed up the video to 2x and slow down the intro to 0.5x", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing video speed changer, 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.

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

• X-Skill-Source: video-speed-changer
• X-Skill-Version: from frontmatter version
• X-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.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "speed up the video to 2x and slow down the intro to 0.5x" — 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 platforms and devices.

Common Workflows

Quick edit: Upload → "speed up the video to 2x and slow down the intro to 0.5x" → Download MP4. Takes 20-40 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.