Tiktok Free Youtube Video

convert YouTube video URL into TikTok-ready clips with this skill. Works with MP4, MOV, WebM, AVI files up to 500MB. TikTok creators use it for repurposing Y...

Security Scan

The skill's claimed purpose (convert YouTube to TikTok clips) matches the network calls and token it asks for, but there are a few inconsistencies and UX instructions (automatic anonymous token creation, hiding API responses/tokens, and an undocumented config path in the skill frontmatter) that merit caution before installing.

Purpose & Capability

The skill's dependencies (NEMO_TOKEN and requests to mega-api-prod.nemovideo.ai) are consistent with a cloud-rendering video service—so the required credential is plausible. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that is not listed in the registry metadata, an inconsistency that should be resolved.

Instruction Scope

The runtime instructions tell the agent to automatically obtain an anonymous token and create a session, upload files (including from local paths) and send video data to a remote service. Critically, the instructions also explicitly tell the agent not to display raw API responses or token values to the user, which reduces transparency and could be abused to hide network activity or secrets. The workflow otherwise does not ask the agent to read unrelated system files or credentials.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That reduces installer risk.

Credentials

Only one environment variable (NEMO_TOKEN) is declared and used, which is proportionate for a remote rendering API. Still: the SKILL.md instructs generating and storing tokens automatically and references a config directory in its frontmatter (not declared elsewhere). Also note the skill expects to persist a session_id for subsequent requests but does not specify where/how it will be stored.

Persistence & Privilege

The skill is not always-enabled and has default autonomous invocation allowed (the platform default). There is no request to modify other skills or system-wide settings. Be aware that allowing autonomous invocation gives the skill the ability to call the external service on its own, which combined with the instruction to hide API responses increases the need for caution.

What to consider before installing

This skill otherwise looks like a legitimate client for nemovideo.ai, but exercise caution before installing: 1) Verify you trust the domain mega-api-prod.nemovideo.ai and its privacy/security policies—the skill will upload your video content to that remote service. 2) The skill can auto-generate and store anonymous tokens and explicitly tells the agent not to show raw API responses or token values—ask why responses are hidden and where tokens/session IDs are stored. 3) Avoid uploading sensitive or proprietary videos unless you confirm the service's retention/usage policy. 4) The SKILL.md frontmatter references a local config path (~/.config/nemovideo/) that isn't declared elsewhere—ask the author to clarify. 5) If you want stronger assurance, request the skill's source or a security/privacy statement from the publisher, or use a throwaway/ephemeral token and test with non-sensitive content first.

Getting Started

Ready when you are. Drop your YouTube video URL here or describe what you want to make.

Try saying:

• "convert a 10-minute YouTube tutorial video into a 1080p MP4"
• "extract the best short clips from this YouTube video and format them for TikTok"
• "repurposing YouTube videos into TikTok clips for TikTok 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.

TikTok Free YouTube Video — Convert YouTube Videos to TikTok Clips

Send me your YouTube video URL and describe the result you want. The AI clip extraction runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 10-minute YouTube tutorial video, type "extract the best short clips from this YouTube video and format them for TikTok", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: vertical crop is applied automatically so clips fit TikTok's 9:16 format.

Matching Input to Actions

User prompts referencing tiktok free youtube video, 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.

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

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

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

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 "extract the best short clips from this YouTube video and format them for TikTok" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across TikTok, YouTube Shorts, and Reels.

Common Workflows

Quick edit: Upload → "extract the best short clips from this YouTube video and format them for TikTok" → 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.