Video Trimmer Flutter

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

Security Scan

The skill's declared requirements mostly match a remote video-trimming service, but there are small metadata inconsistencies, an unknown upstream domain, and it asks the agent to obtain/store a bearer token and upload user videos — all of which deserve caution before installing.

Purpose & Capability

The skill name and description align with the runtime instructions (upload videos, create a session, request remote renders). Requesting a service token (NEMO_TOKEN) is appropriate for that purpose. Minor inconsistency: the registry metadata lists no required config paths but the SKILL.md frontmatter claims a config path (~/.config/nemovideo/).

Instruction Scope

SKILL.md instructions stay within the trimming/export domain: generate an anonymous token if none exists, create sessions, upload files, poll render status, handle SSE. The instructions require uploading user media to a remote API (expected for a cloud render service). They also require adding attribution headers and auto-detecting platform/install path — which implies the agent may inspect its install path. No instructions ask the agent to read unrelated files or harvest unrelated environment variables.

Install Mechanism

Instruction-only skill with no install spec or downloaded code, so nothing is written to disk by the skill itself. This is the lowest-risk install model.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv), which matches the service usage. However: (1) the skill instructs obtaining and saving an anonymous token (data.token) — agents must be careful where that token is stored; (2) the skill metadata also references a config path even though the registry said none; and (3) the upstream domain is unknown (mega-api-prod.nemovideo.ai). Users should ensure NEMO_TOKEN is not a reusable/high-privilege secret and understand that providing it grants the service access to uploaded files and account actions.

Persistence & Privilege

always is false and the skill does not request system-wide modifications or permanent agent privileges. It instructs saving session_id and using tokens for session lifetime, which is normal for a remote API client.

What to consider before installing

This skill mostly behaves like a normal cloud video-trimming client, but review these points before installing: - Privacy: the skill uploads your video/audio files to https://mega-api-prod.nemovideo.ai for processing. Don’t upload sensitive content unless you trust the provider and its policies. - Token scope: NEMO_TOKEN (or the anonymous token returned) is a bearer token — treat it like a secret. Confirm where the agent will store the token and prefer ephemeral/anonymous tokens if possible. Revoke tokens after use if the service supports it. - Unknown origin: there is no homepage/source listed. Verify the service/domain (nemovideo) independently (company, privacy policy, terms) before sending private data. - Metadata mismatch: SKILL.md mentions a config path (~/.config/nemovideo/) while the registry shows none — ask the publisher which is correct and whether the skill will read or write that path. - Test first with non-sensitive/sample media and monitor network activity to confirm requests go only to the stated API domain. If you’re uncomfortable, decline installation until the vendor/source is verified and you’ve confirmed token handling and storage behavior.

Getting Started

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

Try saying:

• "trim my video clips"
• "export 1080p MP4"
• "trim the first 30 seconds and"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Trimmer Flutter — Trim and Export Video Clips

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

A quick example: upload a 3-minute Flutter tutorial recording, type "trim the first 30 seconds and cut the last 10 seconds of dead air", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter source clips process faster and reduce export wait time.

Matching Input to Actions

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

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 "trim the first 30 seconds and cut the last 10 seconds of dead air" — 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 Android and iOS Flutter apps.

Common Workflows

Quick edit: Upload → "trim the first 30 seconds and cut the last 10 seconds of dead air" → 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.