Browser Free Ai

edit video clips into edited MP4 files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. casual creators and remote workers use it for editi...

Security Scan

The skill mostly matches its stated purpose (cloud video editing) but has a few inconsistent declarations and privacy-relevant behaviour you should understand before installing.

Purpose & Capability

The skill claims to provide cloud video editing and the runtime instructions call a nemo video backend (upload, render, export) — this is coherent. However the registry metadata says 'Required config paths: none' while the SKILL.md frontmatter lists ~/.config/nemovideo/ as a config path, and the registry marks NEMO_TOKEN as required even though the instructions describe auto-generating an anonymous token if none is present. These mismatches are small but unexplained.

Instruction Scope

Instructions direct the agent to upload user media and metadata to https://mega-api-prod.nemovideo.ai, open SSE streams, poll render state, and store a session_id. All of that is expected for cloud editing, but it means user files and derived metadata will be transmitted to an external service. The skill also instructs the agent to read the skill file frontmatter and detect install path (e.g., ~/.clawhub/ or ~/.cursor/) to set attribution headers — reading the local install path is not strictly necessary for editing and leaks environment/platform info.

Install Mechanism

No install steps or downloaded code are present (instruction-only). Nothing is written to disk by an installer, which is the lowest install risk.

Credentials

Only a single credential (NEMO_TOKEN) is used, which is appropriate for a third‑party cloud service. But the registry marks NEMO_TOKEN as required while the SKILL.md explains the agent can obtain an anonymous token automatically via an API call. The skill also references a config path in frontmatter that the registry omitted. These inconsistencies make it unclear whether the skill truly needs a pre-provided secret or will always self-provision ephemeral tokens.

Persistence & Privilege

The skill is not set to always:true and does not request elevated platform privileges. It instructs storing a session_id for the lifetime of the session, which is normal for service integration and does not indicate system-wide persistence.

What to consider before installing

This skill will upload your video and media files to a third‑party service (https://mega-api-prod.nemovideo.ai) for processing — review privacy and terms before sending any sensitive content. The skill can auto-generate an anonymous NEMO_TOKEN if none is provided; the registry nevertheless lists NEMO_TOKEN as required, and the SKILL.md also references a local config path (~/.config/nemovideo/) that the registry omitted. Before installing, decide whether you want to provision your own token (so the skill uses your account) or allow anonymous tokens, and confirm you’re comfortable with uploads to the listed domain. If you need stronger guarantees, ask the publisher for clarity on why NEMO_TOKEN is labeled 'required', what (if anything) is stored locally, and whether attribution headers / install-path detection are necessary.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "edit and export this video without"

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.

Browser Free AI — Edit Videos Without Installing Software

This tool takes your video clips and runs AI video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute MP4 recorded on a smartphone and want to edit and export this video without installing any software — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes process significantly faster in the browser environment.

Matching Input to Actions

User prompts referencing browser free ai, 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: browser-free-ai
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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

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 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 "edit and export this video without installing any software" — 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 devices and platforms.

Common Workflows

Quick edit: Upload → "edit and export this video without installing any software" → 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.