Video Gratuit

edit video clips into free edited videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. casual creators and students use it for editing a...

Security Scan

The skill's behavior mostly matches a cloud video-editing service, but there are inconsistencies between declared requirements and the runtime instructions (token provisioning, config path usage, and header/install-path detection) that warrant caution before installing.

Purpose & Capability

The skill claims to perform cloud video editing and its network endpoints and upload instructions align with that purpose. However, registry metadata declares no required config paths while the skill's YAML frontmatter lists ~/.config/nemovideo/ as a config path. Also the registry marks NEMO_TOKEN as required even though the runtime flow auto-provisions an anonymous token if none is present — this mismatch is inconsistent and should be clarified.

Instruction Scope

SKILL.md instructs the agent to upload user video files (multipart or by URL) to nemovideo API endpoints and to poll render status via SSE — which is expected for this service. It also instructs generating an anonymous token (POST to /api/auth/anonymous-token), storing session_id, and deriving attribution headers from YAML frontmatter and the agent's install path. The install-path based header derivation implies the agent would read its filesystem/install location to set X-Skill-Platform; that is a scope expansion beyond pure API calls and should be explicit to the user.

Install Mechanism

This is an instruction-only skill with no install spec and no code files; there is no package download or archive extraction. No filesystem writes are explicitly required by an installer, lowering installation risk.

Credentials

The only credential declared is NEMO_TOKEN (primaryEnv), which is appropriate for an external API. But the skill both lists NEMO_TOKEN as required and gives a flow to auto-create an anonymous token if it's missing — that's inconsistent. The YAML also references a config path for storing state; it's unclear whether long-lived credentials or session tokens will be written there. The skill does not request unrelated credentials, which is good.

Persistence & Privilege

The skill instructs storing a session_id and implies persistent config under ~/.config/nemovideo/ (per YAML), so it may persist tokens/session state locally. It does not request 'always: true' or other elevated platform privileges. Persisting tokens is reasonable for a client session but the exact storage location and lifecycle (where/how tokens are stored, how to clear them) are not specified.

What to consider before installing

This skill will upload your videos and related edit requests to an external service (mega-api-prod.nemovideo.ai). Before installing, confirm: (1) whether NEMO_TOKEN is actually required or will always be auto-created, (2) where session tokens and any credentials are stored on disk (the YAML mentions ~/.config/nemovideo/), and how you can delete them, (3) the service's privacy and data-retention policy for uploaded videos, and (4) whether deriving X-Skill-Platform by reading install paths is necessary and acceptable in your environment. If you do not want your videos or metadata sent to a third party, do not enable this skill. The mismatches between registry metadata and the SKILL.md (env/config requirements) are explainable but should be clarified by the publisher before trust.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "trim, add subtitles, and export my"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Gratuit — Edit and Export Videos Free

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

Here's a typical use: you send a a 2-minute MP4 recorded on a smartphone, ask for trim, add subtitles, and export my video for free, and about 30-60 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 60 seconds process faster and use fewer free credits.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-gratuit, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

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.

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, add subtitles, and export my video for free" → Download MP4. Takes 30-60 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, add subtitles, and export my video for free" — 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.