Flexclip Alternative

Skip the learning curve of professional editing software. Describe what you want — create a 30-second promo video with text overlays and background music — a...

Security Scan

The skill's stated purpose (cloud AI video creation) lines up with most instructions, but there are small inconsistencies and a few behaviors you should understand before installing—notably a mismatch about configuration paths and implicit filesystem/headers access and the fact that user media is uploaded to an external service.

Purpose & Capability

Name/description (AI video creation, uploads, exports) match the runtime instructions and the single required credential (NEMO_TOKEN). There are no unrelated credentials or binaries requested.

Instruction Scope

Instructions direct the agent to obtain or use NEMO_TOKEN, create sessions, upload user media, and poll/export via HTTPS SSE endpoints on mega-api-prod.nemovideo.ai. They also describe deriving an X-Skill-Platform header by inspecting install path and reference a config path in the SKILL.md frontmatter (~/.config/nemovideo/). Those operations imply the agent may read local install/config paths and will transmit user files to an external backend—behavior that should be explicit to the user. The SKILL.md does not instruct reading other unrelated host secrets, but the implicit path-platform detection and frontmatter configPaths are a scope mismatch with registry metadata.

Install Mechanism

Instruction-only skill with no install spec or code files. This is low-risk from a disk-writing/install perspective.

Credentials

The skill only declares a single credential (NEMO_TOKEN), which is appropriate for a backend service. However, SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that the registry listing did not, producing an inconsistency: either the skill may try to read local config or that frontmatter is stale. The skill also instructs fetching an anonymous token if NEMO_TOKEN is missing (no secrets required for that flow).

Persistence & Privilege

always:false and no install steps. The skill does not request permanent/always-on presence or changes to other skills' configs. Autonomous invocation is allowed by default (normal).

What to consider before installing

This skill appears to do what it says—upload media and use a NEMO_TOKEN to render videos on a third‑party cloud service—but a few things to check before using it: 1) The SKILL.md frontmatter mentions a local config path (~/.config/nemovideo/) and deriving a platform header from install paths; confirm whether the skill will read those local paths (the registry metadata lists no required config paths). 2) Your media files are uploaded to https://mega-api-prod.nemovideo.ai; only upload content you are comfortable sharing with that service and verify its privacy/retention policy. 3) If you don’t supply NEMO_TOKEN the skill will request an anonymous token from the service (no secrets required), but confirm how long tokens are stored and whether tokens are persisted. 4) If you require higher assurance, ask the publisher for proof of domain ownership/terms and for clarification about any local file access. Given the metadata inconsistency and the fact user files are sent off‑host, proceed only if you’re comfortable with those tradeoffs.

Getting Started

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

Try saying:

• "create my video clips, images"
• "export 1080p MP4"
• "create a 30-second promo video with"

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.

FlexClip Alternative — Create and Export Promo Videos

Drop your video clips, 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 logo file, ask for create a 30-second promo video with text overlays and background music, 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 — using fewer than 10 clips keeps render times under a minute.

Matching Input to Actions

User prompts referencing flexclip alternative, 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 flexclip-alternative, 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).

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.

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

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

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.

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 → "create a 30-second promo video with text overlays and background music" → 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 "create a 30-second promo video with text overlays and background 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.