Online To Video Ai

content creators and marketers convert online content links into ready-to-share videos using this skill. Accepts URL, PDF, TXT, DOCX up to 200MB, renders on...

Security Scan

The skill's requested credential and runtime actions align with its stated purpose (converting online content to videos); it's instruction-only and requests only a single service token, but there are small metadata inconsistencies and you should confirm you trust the nemovideo.ai backend before use.

Purpose & Capability

The skill name/description (convert URLs/PDF/TXT/DOCX to videos) matches the instructions which call a nemovideo.ai API and require a NEMO_TOKEN. The only minor inconsistency is that the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata claimed no required config paths; this should be clarified but does not contradict the core purpose.

Instruction Scope

Runtime instructions stay within the video-rendering workflow: establish a session, upload content, use SSE for edits, poll export status, and return download URLs. They instruct creating an anonymous token if NEMO_TOKEN is absent. No instructions direct reading unrelated local files or harvesting unrelated env vars, but the frontmatter asks that the agent auto-detect 'X-Skill-Platform' from the install path (which implies reading install path/ENV) — clarify what path information is read and sent.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest-risk installation surface. All runtime actions are network calls to the declared API host; nothing is downloaded or written by an install step.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is appropriate for a cloud video service. The skill will obtain an anonymous token from the service if none is present (100 free credits, 7-day expiry). No unrelated credentials or broad system secrets are requested.

Persistence & Privilege

The skill does not request always: true, does not modify other skills, and has normal agent invocation settings. It keeps session_id for operations (expected for this workflow) and has no instructions to alter global agent configuration.

Assessment

This skill appears coherent: it needs a NEMO_TOKEN to call a nemovideo.ai backend and otherwise only runs API calls to that service. Before installing, consider: (1) Do you trust the nemovideo.ai domain (mega-api-prod.nemovideo.ai)? the skill will send uploaded content to that backend. (2) If you don't provide NEMO_TOKEN, the skill will request an anonymous token from the service (temporary 7-day token). (3) Clarify the frontmatter config path (~/.config/nemovideo/) and whether the skill will read any local install paths or files (the frontmatter and registry metadata disagree). (4) Because the skill is instruction-only and networked, verify the provider's privacy/terms for uploaded content and check for any required headers or telemetry you might not want sent. If you need stronger assurance, ask the author for a canonical homepage or source repo and confirmation of what local paths (if any) are read.

Getting Started

Send me your online content links and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "convert a URL to a blog post or article into a 1080p MP4"
• "convert this article into a 60-second explainer video with voiceover"
• "converting online articles or web content into short videos for content creators and marketers"

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.

Online to Video AI — Convert Online Content to Video

This tool takes your online content links and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a URL to a blog post or article and want to convert this article into a 60-second explainer video with voiceover — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter source content produces tighter, more focused videos.

Matching Input to Actions

User prompts referencing online to video ai, 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.

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

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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 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

Common Workflows

Quick edit: Upload → "convert this article into a 60-second explainer video with voiceover" → 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 "convert this article into a 60-second explainer video with voiceover" — concrete instructions get better results.

Max file size is 200MB. Stick to URL, PDF, TXT, DOCX for the smoothest experience.

Export as MP4 for widest compatibility across social platforms.