Video Editing With Ai Free

edit raw video footage into edited video clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and social media users use...

Security Scan

The skill's runtime instructions match a video-editing service and only request a single service token, but there's an unexplained metadata/config-path mismatch and a few minor scope ambiguities you should verify before trusting it with sensitive data or a long-lived token.

Purpose & Capability

The name/description and runtime instructions consistently describe a cloud-based video editing service and require a single service credential (NEMO_TOKEN), which is coherent. However, the SKILL.md frontmatter lists a required config path (~/.config/nemovideo/) while the registry metadata above the SKILL.md reports no required config paths — that mismatch is unexplained and may indicate the skill expects to read local config files.

Instruction Scope

The SKILL.md instructs the agent to obtain/use an API token, create a session, upload media, stream SSE chat, poll export status, and return download URLs — all within the stated video-editing purpose. It does not instruct reading arbitrary unrelated files or other environment variables. Minor scope items to verify: auto-detection of install path for X-Skill-Platform (requires inspecting agent install environment) and the frontmatter configPaths which imply filesystem access.

Install Mechanism

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

Credentials

The only declared credential is NEMO_TOKEN, which is appropriate for a third-party editing API. However, the presence of a declared config path (~/.config/nemovideo/) in the SKILL.md frontmatter (contradicting the registry report) suggests the skill may try to read local config, which could expose other stored credentials. NEMO_TOKEN is a bearer token and should be treated as sensitive; the skill also instructs generating and storing an anonymous token if none is present, which is acceptable but you should avoid supplying a personal/long-lived token unless you trust the service.

Persistence & Privilege

always is false (default). The skill requests to save a session_id in-session but does not demand persistent system-level changes or modifications to other skills. Autonomous invocation is allowed by default (normal for skills).

What to consider before installing

This skill appears to implement a cloud video-editing workflow and needs a NEMO_TOKEN bearer token to operate — that's expected. Things to check before installing or providing secrets: - Confirm the source/domain: the API host is mega-api-prod.nemovideo.ai. If you don't recognize this service, find an official homepage or privacy policy before providing a real NEMO_TOKEN. - Ask why the SKILL.md frontmatter includes ~/.config/nemovideo/ (filesystem access) when the registry metadata lists no required config paths. If the skill will read that directory, ask what it reads and why. - Prefer using the anonymous-token flow for testing (the skill supports generating a short-lived anonymous token) instead of supplying a personal/long-lived NEMO_TOKEN. - Do not provide sensitive footage or account tokens until you verify logging, retention, and billing behavior of the service. Treat NEMO_TOKEN like any bearer API key (can enable billing or data access). - Because the skill auto-detects X-Skill-Platform from install path, it may inspect the agent environment; confirm exactly what filesystem reads it will perform. - If you need higher assurance, request the skill owner/publisher metadata or source code (there is no homepage listed). Without provenance, use a throwaway account/token and non-sensitive test videos. If the owner or a public homepage/source repo is provided (or if the registry metadata is corrected to include the config path), I can reassess with higher confidence.

Getting Started

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

Try saying:

• "edit a 2-minute unedited phone recording into a 1080p MP4"
• "trim the silences, add transitions, and export as a clean short video"
• "automatically editing raw footage into polished videos without manual work for content creators and social media users"

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 Editing with AI Free — Edit and Export AI Videos

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

Here's a typical use: you send a a 2-minute unedited phone recording, ask for trim the silences, add transitions, and export as a clean short video, and about 1-2 minutes 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 60 seconds process significantly faster and give more precise AI results.

Matching Input to Actions

User prompts referencing video editing with ai free, 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 calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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-editing-with-ai-free
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.

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)

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.

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

Common Workflows

Quick edit: Upload → "trim the silences, add transitions, and export as a clean short video" → Download MP4. Takes 1-2 minutes 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 the silences, add transitions, and export as a clean short video" — 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 platforms and devices.