Video Trimmer Download For Pc

Turn a 10-minute raw screen recording into 1080p trimmed video clips just by typing what you need. Whether it's cutting unwanted sections from long video rec...

Security Scan

The skill mostly matches a cloud-based video-trimming service but has small incoherences (metadata vs registry) and instructions that may require reading local paths / fingerprinting the environment and will upload user videos to an external API — review before installing.

Purpose & Capability

Stated purpose (cloud video trimming/export) aligns with required credential NEMO_TOKEN and the API endpoints described. Asking for a token and calling a render/upload API is coherent with the described feature set. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) even though the registry metadata earlier showed no required config paths — that mismatch is unexplained and worth clarifying.

Instruction Scope

Instructions direct the agent to examine the environment for NEMO_TOKEN (expected) and, if missing, to call an anonymous auth endpoint to obtain a token. They also require attaching attribution headers and ask to auto-detect an install path to populate X-Skill-Platform (i.e., reading install filesystem information). The skill will upload user-supplied video files to an external domain (mega-api-prod.nemovideo.ai). These behaviors are understandable for a cloud service but expand scope to network access and potential filesystem inspection/fingerprinting — the SKILL.md does not justify reading install/config paths or explain token persistence.

Install Mechanism

Instruction-only skill with no install spec and no code files. This is the lowest install risk (no downloads or extracts).

Credentials

The skill declares a single required environment variable (NEMO_TOKEN), which is proportionate. But the frontmatter's configPaths entry (~/.config/nemovideo/) implies the agent may read local config files, and the instructions ask to auto-detect an install path for X-Skill-Platform — both would grant access to filesystem metadata beyond a single API token. The registry metadata earlier contradicted that (it showed no config paths), creating an unexplained discrepancy.

Persistence & Privilege

always:false and no install steps that modify other skills or agent-wide settings. The skill does create session tokens and may reuse anonymous tokens but does not request permanent elevated presence.

What to consider before installing

What to check before installing: - Understand that using this skill will upload your videos to an external service (mega-api-prod.nemovideo.ai). Do not send sensitive/private footage unless you trust the service and its privacy policy. - The skill will look for NEMO_TOKEN in the environment; if absent it will call an anonymous auth endpoint to obtain a temporary token. Decide whether you prefer to supply your own token rather than letting the agent request one. - Clarify the metadata mismatch: SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) and requests auto-detection of an install path for X-Skill-Platform — ask the publisher why filesystem access is needed and whether the agent will read or store files in that location. - The skill requires adding custom headers that identify the skill and platform; these can fingerprint your environment. If you are uncomfortable exposing install-path-derived platform info, do not enable the skill or request the publisher to remove that requirement. - Verify the service domain and ownership (nemovideo.ai) and confirm retention/usage policies for uploaded video and extracted metadata. If you cannot validate the backend operator, treat the skill as higher risk. If you need help composing specific questions for the publisher (e.g., token persistence, config path usage, data retention), I can draft them.

Getting Started

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

Try saying:

• "trim my video clips"
• "export 1080p MP4"
• "trim the intro and cut out"

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.

Video Trimmer Download for PC — Trim and Export Video Clips

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

Here's a typical use: you send a a 10-minute raw screen recording, ask for trim the intro and cut out the silent pauses in the middle, and about 20-40 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 5 minutes process in under 30 seconds.

Matching Input to Actions

User prompts referencing video trimmer download for pc, 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	video-trimmer-download-for-pc
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 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.

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the intro and cut out the silent pauses in the middle" — 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 all PC media players.

Common Workflows

Quick edit: Upload → "trim the intro and cut out the silent pauses in the middle" → 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.