Youtube Video Converter

v1.0.0

convert YouTube video links into converted MP4 files with this skill. Works with MP4, WebM, AVI, MOV files up to 500MB. YouTubers use it for converting YouTu...

0· 124·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for vynbosserman65/youtube-video-converter.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Youtube Video Converter" (vynbosserman65/youtube-video-converter) from ClawHub.
Skill page: https://clawhub.ai/vynbosserman65/youtube-video-converter
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install youtube-video-converter

ClawHub CLI

Package manager switcher

npx clawhub@latest install youtube-video-converter
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill's declared purpose (convert YouTube links to MP4/WebM/etc.) matches the runtime instructions (calls to a nemo video API, upload/render/export endpoints). Requesting a single token (NEMO_TOKEN) is appropriate for this purpose. However, registry metadata reported 'no config paths' while the SKILL.md frontmatter lists a config path (~/.config/nemovideo/), which is an inconsistency to resolve.
Instruction Scope
SKILL.md contains explicit API calls (session creation, upload, render, credit checks) and SSE handling that stay within the stated purpose of driving a cloud render pipeline. The instructions expect the agent to upload user-provided videos/URLs and to include Authorization headers. They also advise deriving an anonymous token if none exists. Nothing in the instructions asks the agent to read unrelated secrets or system data beyond possible install/config paths mentioned.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so it does not write new binaries or download archives. That lowers installation risk.
Credentials
The skill requires a single environment variable (NEMO_TOKEN) which aligns with the API-based workflow. Minor proportionality concerns: SKILL.md references a config path (~/.config/nemovideo/) and detection of install paths for header population; the registry metadata did not list this path. Also the skill will send user-supplied video data to an external domain (mega-api-prod.nemovideo.ai), so users should consider privacy of uploaded content and whether they trust the remote service.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It instructs storing session_id/token in-session for API use, which is typical for this functionality. It does not try to modify other skills or system-wide agent settings.
Assessment
This skill appears to do what it says: it talks to a nemo video API and needs one token (NEMO_TOKEN). Before installing, confirm you trust the remote service (mega-api-prod.nemovideo.ai) because any video or link you submit will be uploaded/processed there. Note the registry metadata vs SKILL.md mismatch: SKILL.md references a config path (~/.config/nemovideo/) while the registry reported none — ask the publisher which is correct. Also the skill has no public source or homepage; if you need stronger assurance, request the skill's source or documentation and verify the API domain and privacy policy. If you proceed, prefer using an ephemeral/anonymous token for testing rather than a long-lived secret tied to other accounts.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk975y7x4mvcyb4eypew8qsn0d584mq59
124downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Getting Started

Got YouTube video links to work with? Send it over and tell me what you need — I'll take care of the format conversion processing.

Try saying:

  • "convert a 10-minute YouTube tutorial video into a 1080p MP4"
  • "convert this YouTube video to MP4 at 1080p"
  • "converting YouTube videos to downloadable MP4 files for YouTubers"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

YouTube Video Converter — Convert YouTube Videos to MP4

This tool takes your YouTube video links and runs format conversion processing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 10-minute YouTube tutorial video and want to convert this YouTube video to MP4 at 1080p — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: shorter clips under 5 minutes convert significantly faster.

Matching Input to Actions

User prompts referencing youtube video converter, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is youtube-video-converter, 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.

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

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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 saysYou 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 Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

Common Workflows

Quick edit: Upload → "convert this YouTube video to MP4 at 1080p" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "convert this YouTube video to MP4 at 1080p" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, WebM, AVI, MOV for the smoothest experience.

Export as MP4 for widest compatibility across devices and platforms.

Comments

Loading comments...