Ai Effect Video Generator Free

Turn a 30-second clip from a phone camera into 1080p effects-enhanced videos just by typing what you need. Whether it's adding AI visual effects to short vid...

Security Scan

The skill mostly matches a cloud video-rendering helper, but there are inconsistencies about what filesystem/config paths it needs and it instructs the agent to probe local install paths and persist tokens — ask for clarification before installing or give limited/trial credentials.

Purpose & Capability

The skill's stated purpose (cloud AI video effects) aligns with the network calls and the single required credential (NEMO_TOKEN). However the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) and runtime instructions that detect install directories (~/.clawhub/, ~/.cursor/skills/) while the registry metadata provided with the skill lists no required config paths — this mismatch is an incoherence that should be explained.

Instruction Scope

Instructions are detailed and largely scoped to interacting with the nemovideo API (auth, session creation, uploads, SSE, export). Two items to note: (1) the skill tells the agent to read its own YAML frontmatter at runtime and to detect installation platform by checking specific user-paths (~/.clawhub, ~/.cursor/skills), which requires filesystem access beyond purely sending/receiving video. (2) It instructs saving session_id and using/setting NEMO_TOKEN (but does not specify where persistent storage occurs). These behaviors are plausible for attribution and UX but should be explicit in metadata.

Install Mechanism

There is no install spec and no code files — this is instruction-only, so nothing is downloaded or written by a packaged installer. That minimizes install-time risk.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportionate for a cloud rendering API. The skill also describes a workflow to obtain a short-lived anonymous token by POSTing to the service; that flow is reasonable. Still, the skill implies saving tokens/session IDs and checking local paths; verify whether those are stored to disk and where.

Persistence & Privilege

always:false and no special privileges requested. Autonomous invocation is allowed (default) but not in itself a concern. The only persistence-related behavior is saving session_id / token — the mechanism/location is not specified and should be clarified.

What to consider before installing

This skill appears to be a wrapper for a cloud video-rendering API and only requests one credential (NEMO_TOKEN), which is reasonable. Points to check before installing: 1) Ask the author to explain the configPaths discrepancy (SKILL.md references ~/.config/nemovideo/ and runtime checks for ~/.clawhub or ~/.cursor/skills, but registry metadata showed none). 2) Confirm where tokens and session IDs are stored (memory only or written to disk), and whether the skill will create files under your home directory. 3) Be aware that using the skill uploads your video clips to an external service (mega-api-prod.nemovideo.ai) — do not upload sensitive content unless you trust the provider. 4) Test with a throwaway/anonymous token or unprivileged account first. If the author cannot justify the filesystem probes and storage behavior, treat the mismatch as a red flag and avoid granting persistent credentials.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI effects application.

Try saying:

• "add a 30-second clip from a phone camera into a 1080p MP4"
• "add cinematic AI visual effects to my video for free"
• "adding AI visual effects to short video clips for TikTok creators"

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.

AI Effect Video Generator Free — Add AI Effects to Videos

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

Say you have a 30-second clip from a phone camera and want to add cinematic AI visual effects to my video for free — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing ai effect video generator 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: ai-effect-video-generator-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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.

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.

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 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)

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 → "add cinematic AI visual effects to 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 "add cinematic AI visual effects to 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.