Free To Online

publish video files into shareable online videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for uploading and...

Security Scan

The skill's declared purpose (uploading/publishing videos) is generally consistent with its runtime instructions, but there are mismatches and unknowns (unknown source, an unverified external API host, and a metadata/config-path inconsistency) that warrant caution before installing or giving it credentials.

Purpose & Capability

Name/description match the actions in SKILL.md: it calls a video-processing backend, uploads files, creates sessions, polls render jobs, and returns download URLs. Required env var NEMO_TOKEN is consistent with a dedicated backend token. However, the skill frontmatter (inside SKILL.md) includes a configPaths entry (~/.config/nemovideo/) while the registry metadata reported no required config paths — this mismatch is unexplained. The skill's source and homepage are unknown and the API host (mega-api-prod.nemovideo.ai) is not documented elsewhere in the package metadata.

Instruction Scope

Instructions are specific and scoped to creating an anonymous token, creating a session, uploading user-provided video files, SSE interactions, and exporting. They instruct the agent to look for NEMO_TOKEN in the environment and otherwise obtain an anonymous token via the backend API. They require multipart uploads (local file paths) which is expected for file uploads. The instructions do not appear to request unrelated system data, but they do mention a config path in frontmatter (potential read/write) and require generating and sending a client identifier header — both of which could touch local config or persistent state if implemented; the SKILL.md does not clearly say whether tokens should be stored locally.

Install Mechanism

No install spec and no code files (instruction-only). This minimizes on-disk execution risk because nothing in the package will be extracted or installed by default.

Credentials

Only one credential (NEMO_TOKEN) is declared, which is appropriate for a service-backed upload skill. However, the frontmatter also lists a config path (~/.config/nemovideo/) that could give the skill access to files under the user's home directory; the registry metadata did not list this config path, creating inconsistency. The SKILL.md also instructs creating an anonymous token when NEMO_TOKEN is not present — if the implementation stores that token on disk (not specified), this could persist credentials beyond the session. No other unrelated secrets are requested.

Persistence & Privilege

always is false (not force-included) and autonomous invocation is the platform default. The SKILL.md does not instruct modifying other skills or system-wide settings. The only potential persistence vector is the ambiguous config path/token storage noted above — but the skill does not explicitly state it will write to that path.

What to consider before installing

This skill appears to do what it says (upload and render videos) and only asks for a single token (NEMO_TOKEN), but exercise caution because: - The package source and homepage are missing and the backend domain (mega-api-prod.nemovideo.ai) is unverified. Verify the service/owner before providing a token. - SKILL.md frontmatter references a config directory (~/.config/nemovideo/) while the registry metadata did not — ask the author whether the skill will read or write files there and why. - The skill will accept and upload local video files; avoid sending any sensitive files or unrelated secrets in the chat. - If you already have NEMO_TOKEN, consider creating a limited-scope or ephemeral token for this skill rather than a long-lived credential. If the skill creates/stores an anonymous token, ask if it persists it to disk and where. - Prefer using this only with non-sensitive sample videos until you confirm the backend is trustworthy. If you need higher assurance, request the skill author/source code or an official homepage and review how tokens are stored and used.

Getting Started

Share your video files and I'll get started on online video publishing. Or just tell me what you're thinking.

Try saying:

• "publish my video files"
• "export 1080p MP4"
• "publish my video online so anyone"

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.

Free to Online — Upload and Share Videos Online

Drop your video files in the chat and tell me what you need. I'll handle the online video publishing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute edited travel video, ask for publish my video online so anyone can watch it for free, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips upload and process faster for quicker sharing.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

Header	Value
X-Skill-Source	free-to-online
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 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

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

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.

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 "publish my video online so anyone can watch it for free" — 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 all platforms and devices.

Common Workflows

Quick edit: Upload → "publish my video online so anyone can watch it for free" → Download MP4. Takes 20-40 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.