Video Maker With Effects Free

Skip the learning curve of professional editing software. Describe what you want — add transitions, color filters, and background music to my video — and get...

Security Scan

The skill's requirements and runtime instructions mostly match a cloud video-editing integration (NEMO token + Nemo API endpoints); nothing appears to be trying to do unrelated work, but there are a few minor inconsistencies and privacy implications to be aware of.

Purpose & Capability

The skill's name/description (cloud video editing with effects) aligns with the declared primary credential (NEMO_TOKEN) and the runtime instructions which call a nemo-video API. One inconsistency: registry metadata listed no required config paths, but the SKILL.md frontmatter requests ~/.config/nemovideo/ in metadata — this mismatch should be clarified.

Instruction Scope

Instructions are focused on connecting to the Nemo backend, creating a session, uploading videos, triggering renders, polling status, and returning download URLs — all appropriate for the described purpose. The skill instructs the agent to: auto-request an anonymous token if none is present, store session_id for subsequent calls, and detect install path (~/.clawhub or ~/.cursor/skills/) for an attribution header. The install-path detection implies reading the agent filesystem; this is functionally plausible but worth noting as it touches local paths.

Install Mechanism

Instruction-only skill with no install spec and no code files. Lowest install risk — nothing is downloaded or written by an installer as part of the skill package itself.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required/primary, which fits the integration. SKILL.md also describes obtaining an anonymous token automatically if none is provided. The frontmatter mentions a config path (~/.config/nemovideo/) that is not listed in the registry metadata — this discrepancy should be resolved. No unrelated secrets (AWS, GitHub, etc.) are requested.

Persistence & Privilege

The skill does not request always:true and uses normal agent invocation. It asks to store a session_id for use during a session and may orphan server-side render jobs if the session closes; it does not request elevated system-wide privileges or to modify other skills. Persisted state handling (where session_id is stored) is unspecified — recommend clarifying persistence scope and lifetime.

Assessment

This skill appears to be a thin integration with an external Nemo video-processing API and will upload your video files to https://mega-api-prod.nemovideo.ai for editing. Before installing or using it: (1) Understand that your media will be transmitted to an external service — avoid uploading sensitive video/audio. (2) The skill will auto-obtain an anonymous NEMO_TOKEN if you don't provide one; if you prefer control, supply your own token instead. (3) Clarify the mismatch about config paths (~/.config/nemovideo/) vs. registry metadata and ask where session tokens/session_id are stored and for how long. (4) There is no homepage or publisher information; if you need stronger assurance, request publisher identity, privacy policy, and a service terms link before using. If you accept those tradeoffs, the skill's behavior is coherent with its stated purpose.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "add transitions, color filters, and background"

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 Maker With Effects Free — Add Effects and Export Videos

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

Say you have a 60-second smartphone clip and want to add transitions, color filters, and background music to my video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process faster and give cleaner effect results.

Matching Input to Actions

User prompts referencing video maker with effects 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: video-maker-with-effects-free
• 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.

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.

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)

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

Common Workflows

Quick edit: Upload → "add transitions, color filters, and background music to my video" → 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 transitions, color filters, and background music to my 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 social platforms.