Trimmer By Link

trim video URL link into trimmed video clips with this skill. Works with YouTube, Vimeo, MP4, MOV files up to 500MB. content creators, researchers, social me...

Security Scan

The skill's declared requirements and runtime instructions mostly match a video-trimming service (it needs a NEMO_TOKEN and talks to nemovideo.ai), but there are small metadata inconsistencies and a few runtime behaviors (reading install/config paths, automatic anonymous auth) that deserve attention before installing.

Purpose & Capability

Name/description (trim video links) align with the only required credential (NEMO_TOKEN) and the documented API endpoints on mega-api-prod.nemovideo.ai. 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 verifying. Requiring a NEMO_TOKEN is proportionate to a remote render service.

Instruction Scope

SKILL.md gives explicit instructions to use NEMO_TOKEN or obtain an anonymous token via network calls to mega-api-prod.nemovideo.ai, create sessions, upload URLs/files, read SSE, and poll status — all expected for a remote trimming service. It also instructs the agent to read the skill's YAML frontmatter for attribution and to detect install path (~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform; that requires accessing local paths and is not strictly necessary for trimming functionality (it’s attribution-related). No instructions ask for unrelated system secrets, but the filesystem checks and attribution requirements are scope-expanding and should be validated.

Install Mechanism

Instruction-only skill with no install spec and no code files. This is lower risk because nothing is written or executed locally by an installer. All heavy work is performed on the remote service.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv) which is consistent with a service API key. The SKILL.md also documents an anonymous-token flow (POST to the API to get a short-lived token) which is reasonable. The frontmatter's mention of a local config path (~/.config/nemovideo/) is not explained by registry metadata and could imply optional local credential/config usage; flag that mismatch and confirm whether any local files will be read.

Persistence & Privilege

always:false and no install hooks — the skill does not request permanent system presence or elevated privileges. Autonomous invocation is allowed by default; that is normal. The skill does instruct the agent to read local install paths/frontmatter for attribution, but it doesn't request modifying other skills or writing system-wide settings.

What to consider before installing

This skill appears to be a client for a remote video-trimming service (nemovideo.ai) and requires a service token (NEMO_TOKEN) or will obtain a short-lived anonymous token. Before installing: (1) Confirm you trust mega-api-prod.nemovideo.ai (privacy of uploaded URLs/videos, retention, who can access generated clips). (2) Verify the mismatch: SKILL.md frontmatter lists ~/.config/nemovideo/ while registry metadata lists no config paths — ask the author whether the skill will read local config files. (3) Be aware the skill may inspect agent install paths (~/.clawhub, ~/.cursor/skills) for attribution headers; if you prefer not to expose local paths, ask for an option to disable that behavior. (4) Because the skill sends video URLs and possibly uploaded media to a third-party service, avoid sending private or sensitive videos unless you trust the service/legal terms. If the author can provide a homepage, privacy policy, or source repo, review those to raise confidence.

Getting Started

Got video URL link to work with? Send it over and tell me what you need — I'll take care of the AI clip trimming.

Try saying:

• "trim a YouTube link to a 10-minute tutorial video into a 1080p MP4"
• "trim this video from 1:30 to 4:45 and export the clip"
• "cutting specific segments from online videos by pasting a link for content creators, researchers, social media managers"

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.

Trimmer by Link — Trim and Export Video Clips

Send me your video URL link and describe the result you want. The AI clip trimming runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a YouTube link to a 10-minute tutorial video, type "trim this video from 1:30 to 4:45 and export the clip", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: paste the URL directly — no need to download the video before trimming.

Matching Input to Actions

User prompts referencing trimmer by link, 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: trimmer-by-link
• 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

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

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

Common Workflows

Quick edit: Upload → "trim this video from 1:30 to 4:45 and export the clip" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim this video from 1:30 to 4:45 and export the clip" — concrete instructions get better results.

Max file size is 500MB. Stick to YouTube, Vimeo, MP4, MOV for the smoothest experience.

Export as MP4 for widest compatibility.