Invideo Alternative

marketers and content creators create text or video clips into ready-to-publish videos using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, renders on...

Security Scan

The skill's behavior mostly matches a cloud video-rendering service, but there are mismatches and unclear instructions around where tokens/sessions are stored and a hidden config path declared in the skill metadata that isn't reflected in the registry — this inconsistency and automatic token generation/storage warrant caution.

Purpose & Capability

The name/description (cloud video creation and export) aligns with the network endpoints and upload/export workflow in SKILL.md and the single required credential NEMO_TOKEN. However the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that the registry listing did not; that discrepancy is unexplained and suggests the skill may read/write a local config directory not declared in the registry.

Instruction Scope

Instructions direct the agent to auto-connect on first use, POST to external endpoints (including obtaining an anonymous token), upload user files, stream SSE, poll render status, and 'store the returned session_id' but do not specify where or how to persist that token/session. The skill also instructs detecting install path to set X-Skill-Platform, implying filesystem access. Automatic token creation and unspecified token/session storage are scope creep that should be clarified.

Install Mechanism

Instruction-only skill with no install spec or external downloads; nothing is written to disk by an installer step. This is low-risk from installation mechanics.

Credentials

Only NEMO_TOKEN is required and is appropriate for a third-party video API. But SKILL.md metadata lists a config path (~/.config/nemovideo/) and the runtime instructions imply storing tokens/session IDs; the registry summary shows no required config paths. Requesting storage or access to a local config directory should be explicit and justified.

Persistence & Privilege

always:false (normal) and the skill is user-invocable. However the skill instructs creating anonymous tokens and storing session IDs (potentially persistently) and references a local config path — this persistent storage behavior is not clearly declared and could leave credentials or session state on disk. The agent will also perform automatic network calls on first open.

What to consider before installing

This skill appears to be a cloud video-rendering front end and will upload files and call nemo-video APIs. Before installing or using it: 1) Confirm where the skill will store tokens/session IDs (in-memory vs a file like ~/.config/nemovideo/) and whether you approve that path; 2) Be aware the skill will automatically obtain an anonymous NEMO_TOKEN if none is provided — ask whether you can opt out or supply your own token; 3) Do not upload sensitive/private footage or secrets to the service until you review nemo-video's privacy/terms; 4) Ask the publisher for source code or a homepage so you can verify behavior, and request the registry metadata be corrected to declare any config paths; 5) If in doubt, test with non-sensitive sample media first.

Getting Started

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

Try saying:

• "create a 300-word blog post or product script into a 1080p MP4"
• "turn this script into a short promo video with voiceover and visuals"
• "creating marketing or social media videos from text or footage for marketers and content creators"

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.

InVideo Alternative — Create and Export Social Videos

Drop your text or video clips 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 a 300-word blog post or product script, ask for turn this script into a short promo video with voiceover and visuals, 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 scripts under 60 seconds generate faster and perform better on social platforms.

Matching Input to Actions

User prompts referencing invideo 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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 invideo-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).

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

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

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)

Common Workflows

Quick edit: Upload → "turn this script into a short promo video with voiceover and visuals" → 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 "turn this script into a short promo video with voiceover and visuals" — 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 YouTube, Instagram, and TikTok.