Free Youtube Video Tiktok

Get short TikTok clips ready to post, without touching a single slider. Upload your YouTube or video clips (MP4, MOV, WebM, AVI, up to 500MB), say something...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud video-repackaging service, but there are minor metadata inconsistencies and obvious privacy considerations (it uploads user videos to an external API).

Purpose & Capability

Name/description match the instructions: upload video, create session, render/export via nemovideo.ai. Requested credential (NEMO_TOKEN) is appropriate for an external API. Minor inconsistency: the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths.

Instruction Scope

Instructions direct the agent to upload user-supplied video files and associated render commands to https://mega-api-prod.nemovideo.ai and to poll for results — this is expected for a cloud render service. The skill also auto-generates an anonymous token if no NEMO_TOKEN is present (by POSTing with a generated UUID). No instructions ask the agent to read unrelated files or extra environment variables, but the skill will transmit potentially sensitive user content to a third-party service, which is a privacy consideration.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. This is the lowest-risk install profile.

Credentials

Only NEMO_TOKEN is declared as required, which is proportionate to calling a protected API. However, SKILL.md references a config path (~/.config/nemovideo/) not present in the registry's 'required config paths' field — a small metadata mismatch. The skill will also read NEMO_TOKEN from the environment or obtain an anonymous token from the remote API if absent.

Persistence & Privilege

The skill is not 'always: true' and does not request elevated persistence or global configuration changes. It can be invoked by the agent normally; that is the expected behavior.

Scan Findings in Context

[no_regex_findings] expected: The static regex scanner found nothing to analyze because this is an instruction-only skill (no code files). That is expected, but absence of findings is not proof of safety — runtime behavior depends on calls to the external API described in SKILL.md.

Assessment

This skill appears to do what it says: it uploads your videos to nemovideo.ai and uses a NEMO_TOKEN (or an anonymously acquired starter token) to create sessions and render TikTok-ready clips. Before installing or using it: 1) Be aware your uploaded media will be sent to an external service — don't upload private/sensitive content unless you trust the service. 2) Check the reputation/privacy policy of nemovideo.ai and confirm how long uploads/derivatives are retained. 3) Note the small metadata mismatch about a config path (~/.config/nemovideo/) — ask the maintainer which local files, if any, the skill will access. 4) Prefer using a limited-scope or disposable token if you don’t want to expose long-lived credentials. If you need higher assurance, request source code or an official homepage from the publisher before proceeding.

Getting Started

Send me your YouTube or video clips and I'll handle the AI video repurposing. Or just describe what you're after.

Try saying:

• "convert a 10-minute YouTube video URL or MP4 file into a 1080p MP4"
• "cut this YouTube video into short TikTok clips with captions"
• "converting YouTube videos into free TikTok-ready short clips for TikTok creators and YouTubers"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Free YouTube Video to TikTok — Convert YouTube Videos into TikTok Clips

Drop your YouTube or video clips in the chat and tell me what you need. I'll handle the AI video repurposing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 10-minute YouTube video URL or MP4 file, ask for cut this YouTube video into short TikTok clips with captions, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — vertical 9:16 crop is applied automatically for TikTok format.

Matching Input to Actions

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

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

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)

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut this YouTube video into short TikTok clips with captions" — 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, and Instagram.

Common Workflows

Quick edit: Upload → "cut this YouTube video into short TikTok clips with captions" → 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.