Video Making Free Online

create video clips or images into polished MP4 videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. students, small business owners, soci...

Security Scan

The skill's requests and runtime instructions are broadly consistent with its stated purpose (cloud video rendering) with a few small mismatches in metadata and a couple of behavior details you should review before installing.

Purpose & Capability

Name/description (create videos from clips/images) matches what the SKILL.md instructs: uploading media, creating a session, queuing render jobs, and returning download URLs from a remote video-rendering API. Required credential (NEMO_TOKEN) and network calls to a nemo-video API are appropriate for a cloud rendering service.

Instruction Scope

Instructions are narrowly scoped to the video rendering workflow (session creation, SSE chat, upload, export, polling). They require reading NEMO_TOKEN from the environment or obtaining an anonymous token. The SKILL.md also references deriving headers from an install path (~/.clawhub/, ~/.cursor/skills/) and lists a config path (~/.config/nemovideo/) in its YAML frontmatter — this implies the agent might check the agent install path or config dir, which is out-of-band relative to pure upload/rendering and should be confirmed. Otherwise no instructions ask the agent to read unrelated user files or additional secrets.

Install Mechanism

This is instruction-only with no install spec and no code files, so nothing is downloaded or written during install. That is the lowest-risk model for a skill of this type.

Credentials

Only one credential is declared (NEMO_TOKEN) which is appropriate for a third-party API. The SKILL.md, however, documents a fallback to obtain an anonymous token by POSTing to the vendor API if no NEMO_TOKEN is present; this makes the declared required-env semantics slightly inconsistent but not inherently dangerous. No other unrelated secrets or environment variables are requested.

Persistence & Privilege

always is false and the skill does not request permanent presence or modification of other skills. It does not require elevated privileges or persistent system-wide changes.

Assessment

This skill appears to do what it says (upload media to a cloud rendering API and return MP4s), but review these points before installing: 1) Trust & domain: media and any uploaded content will be sent to https://mega-api-prod.nemovideo.ai — confirm you trust this service and its privacy/retention policies before uploading sensitive media. 2) Token handling: the skill uses NEMO_TOKEN or will auto-request an anonymous token; if you supply a token, ensure it is scoped/rotatable and not reused for other services. 3) Metadata mismatch: the SKILL.md frontmatter references a config path (~/.config/nemovideo/) and install-path detection — confirm whether the agent will actually read those paths (you may prefer it not to). 4) No code available / unknown source: this is instruction-only with no homepage or repository listed; if you need stronger assurances, ask the publisher for a public code repo, privacy policy, or company identity. 5) Operational limits: check file-size limits, credit usage, and whether exports incur charges; revoke tokens if you stop using the skill. If you want higher assurance, request the skill's source or a vendor website and inspect network destinations and token scope.

Getting Started

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

Try saying:

• "create five product photos and a background music file into a 1080p MP4"
• "combine these photos into a 30-second promo video with transitions and text overlays"
• "creating shareable videos from images or clips without editing software for students, small business owners, social media creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Video Making Free Online — Create and Export Videos Online

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

Here's a typical use: you send a five product photos and a background music file, ask for combine these photos into a 30-second promo video with transitions and text overlays, 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 than longer recordings.

Matching Input to Actions

User prompts referencing video making free online, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-making-free-online, 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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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

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.

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 → "combine these photos into a 30-second promo video with transitions and text overlays" → 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 "combine these photos into a 30-second promo video with transitions and text overlays" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across social platforms and devices.