Video Maker Easy

Get finished MP4 videos ready to post, without touching a single slider. Upload your video clips or images (MP4, MOV, JPG, PNG, up to 500MB), say something l...

Security Scan

The skill's behavior (cloud video uploads and API usage) matches its description, but metadata and runtime instructions contain inconsistencies (required env var vs an anonymous-token flow, an unexplained config path) and it will upload user files to an external service — review before installing.

Purpose & Capability

The skill claims to create/export videos via a cloud backend and all runtime instructions call the nemo video API (session creation, SSE, multipart uploads, render/export). Requesting a NEMO_TOKEN is coherent for this purpose. However the registry metadata marks NEMO_TOKEN as required while the SKILL.md also documents an anonymous-token acquisition flow (POST /api/auth/anonymous-token) that can create a token automatically. The metadata also declares a config path (~/.config/nemovideo/) that the instructions never reference. These mismatches are inconsistent but not necessarily malicious.

Instruction Scope

SKILL.md instructs the agent to POST files (multipart or URL) and stream SSE responses from mega-api-prod.nemovideo.ai — this is expected for a cloud video service. It does not instruct reading arbitrary system config files, but the multipart upload example uses -F "files=@/path" which implies access to user-supplied file paths; users should expect their media (and only that media) will be transmitted to the external API. The skill also instructs generation of UUID, session handling, and header inclusion on every request (Authorization and attribution headers).

Install Mechanism

This is an instruction-only skill with no install spec and no code files — nothing is written to disk by the skill bundle itself. That minimizes supply-chain risk.

Credentials

Only one credential, NEMO_TOKEN, is declared as primary — appropriate for a single-service integration. However, since SKILL.md supports anonymously acquiring a temporary token, declaring NEMO_TOKEN as a required env var is misleading. The declared config path (~/.config/nemovideo/) is unexplained and not used in the instructions, which is an unnecessary scope declaration and should be clarified.

Persistence & Privilege

The skill does not request always-on presence and uses the platform default for autonomous invocation. It does not ask to modify other skills or system-wide settings in the provided instructions.

What to consider before installing

This skill appears to do what it says (upload media to a cloud service, create/export MP4s). Before installing, consider: 1) The skill will upload any media you give it to https://mega-api-prod.nemovideo.ai — do not upload sensitive content you wouldn't want sent to an external service. 2) Metadata lists NEMO_TOKEN as required but the skill can also request an anonymous token itself; ask the publisher which workflow is expected and whether tokens are persisted locally (the SKILL.md says not to expose tokens but doesn't describe storage). 3) The metadata includes a config path (~/.config/nemovideo/) not referenced in the instructions — request clarification. 4) There is no homepage or publisher info; if you plan to use this for business or sensitive material, ask for provenance (official site, privacy policy, support contact) and prefer a skill with a verifiable publisher. If you are comfortable with the external endpoint and only plan to upload non-sensitive media, the functional behavior is consistent with a video-rendering cloud service.

Getting Started

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

Try saying:

• "create my video clips or images"
• "export 1080p MP4"
• "combine these photos into a 30-second"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Video Maker Easy — Create and Export Videos Fast

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 video with transitions and music, 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 — using fewer than 10 clips keeps render time under a minute.

Matching Input to Actions

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

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-maker-easy
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

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.

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 "combine these photos into a 30-second video with transitions and music" — 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.

Common Workflows

Quick edit: Upload → "combine these photos into a 30-second video with transitions and music" → 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.