Video Link Generator Free Download

Get shareable video links ready to post, without touching a single slider. Upload your video files (MP4, MOV, AVI, WebM, up to 500MB), say something like "ge...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video-processing/linking service — it only needs a NEMO_TOKEN and interacts with nemovideo.ai endpoints to upload and render videos.

Purpose & Capability

Requesting a NEMO_TOKEN and calling the nemovideo.ai API is coherent with a video render/link generator. Minor inconsistency: the registry metadata listed no required config paths, but the SKILL.md frontmatter declares a configPath (~/.config/nemovideo/) — plausible (for persisted token/config) but the registry and skill document disagree.

Instruction Scope

SKILL.md confines actions to the nemo API: create/refresh anonymous token, create session, upload user video files or URLs, kick off renders, poll for status, and return download URLs. It does not instruct reading unrelated system files or other credentials. It does instruct reading this skill's frontmatter and detecting install path for attribution headers — reasonable for attribution but harmless in itself.

Install Mechanism

Instruction-only skill with no install spec or code files. No downloads or archive extraction are performed, which is the lowest-risk install profile.

Credentials

Only one credential is required (NEMO_TOKEN), which matches the API usage. The skill also references a config path (~/.config/nemovideo/) in its frontmatter (not reflected in registry metadata) which could be used to persist tokens or session state — this is reasonable but should be confirmed. The skill also documents creating an anonymous token when none is present; that behavior is expected for services offering ephemeral tokens.

Persistence & Privilege

The skill is not always-on and does not request elevated platform privileges. It does instruct storing a session_id and using/keeping a token for subsequent requests; this is normal for a remote API client. Autonomous invocation is enabled by default (normal) but not excessive here.

Assessment

This skill appears to do what it says: upload videos to a nemovideo.ai backend, render them, and return shareable download links. Before installing, confirm you trust the endpoint (https://mega-api-prod.nemovideo.ai) and its privacy policy — uploaded videos will be sent off your device. Note the skill can create an anonymous NEMO_TOKEN for you (valid ~7 days); decide whether you want the token stored in your environment or config directory (~/.config/nemovideo/). Avoid uploading sensitive or regulated content unless you verify retention and access controls. If you want to limit risk, require the skill to prompt before creating/storing tokens and review where session/token data will be persisted.

Getting Started

Got video files to work with? Send it over and tell me what you need — I'll take care of the shareable link generation.

Try saying:

• "generate a 2-minute MP4 video file into a 1080p MP4"
• "generate a shareable link for my video so I can send it to a client"
• "generating shareable links from uploaded video files for marketers"

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.

Video Link Generator Free Download — Generate and Share Video Links

Send me your video files and describe the result you want. The shareable link generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute MP4 video file, type "generate a shareable link for my video so I can send it to a client", and you'll get a 1080p MP4 back in roughly under 30 seconds. All rendering happens server-side.

Worth noting: smaller file sizes upload faster and generate links in seconds.

Matching Input to Actions

User prompts referencing video link generator free download, 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-link-generator-free-download
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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.

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a shareable link for my video so I can send it to a client" — 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.

Common Workflows

Quick edit: Upload → "generate a shareable link for my video so I can send it to a client" → Download MP4. Takes under 30 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.