Editor Ai Tiktok

edit raw video clips into TikTok-ready clips with this editor-ai-tiktok skill. Works with MP4, MOV, AVI, WebM files up to 500MB. TikTok creators use it for e...

Security Scan

The skill's stated purpose (cloud video editing) broadly matches its instructions, but a few unexplained behaviors (automatic anonymous token acquisition, implicit filesystem probing for 'install path', and no published homepage or provenance) make its runtime behaviour and data flows unclear—review before installing or using with sensitive videos.

Purpose & Capability

Name/description, accepted file types, and required NEMO_TOKEN align with a cloud video-editing backend. Requiring a single NEMO_TOKEN is appropriate for the stated purpose. However, the skill also instructs detection of an install path (~/.clawhub/ or ~/.cursor/skills/) to set an attribution header; that filesystem probing is not strictly necessary for editing and is undocumented in the metadata.

Instruction Scope

SKILL.md directs the agent to POST user media and metadata to https://mega-api-prod.nemovideo.ai and to automatically obtain an anonymous NEMO_TOKEN if none is present (generate UUID, call /api/auth/anonymous-token and treat returned token as NEMO_TOKEN). It also instructs reading/detecting the agent's install path to set X-Skill-Platform. Automatic token acquisition and implicit filesystem reads expand the agent's runtime scope beyond simple request/response editing and could lead to unexpected uploads or token storage without explicit user consent.

Install Mechanism

No install spec or code is provided (instruction-only), so nothing is written to disk by the skill itself. This minimizes installer-side risk.

Credentials

Only one declared credential (NEMO_TOKEN) is required, which is proportional to a cloud API client. The instruction to auto-create and use an anonymous token (and to treat that token as NEMO_TOKEN) implies the skill may populate or rely on an env-var at runtime; where/how that token is persisted is not specified.

Persistence & Privilege

Skill is not always:true and does not request elevated platform privileges. There is no install behavior that claims to modify other skills or global agent config. The main persistence risk is implicit: token acquisition and possible storage/persistence of the returned token are not described.

What to consider before installing

This skill appears to call an external cloud service to edit and export your videos. Before using it, consider: 1) The skill will upload your media to https://mega-api-prod.nemovideo.ai — do not send sensitive or private videos unless you trust that endpoint and its privacy policy. 2) If you do not provide NEMO_TOKEN, the skill will automatically request an anonymous token on your behalf (calls /api/auth/anonymous-token) and treat that as NEMO_TOKEN; confirm you are comfortable with automatic token acquisition and possible token persistence. 3) The skill asks the agent to detect its install path (~/.clawhub / ~/.cursor/skills) to set attribution headers—this implies a filesystem check that you may want to be aware of. 4) The package has no homepage or known source listed; consider verifying the service domain and operator before uploading content or providing credentials. If you proceed, prefer providing a token you control (and understand its scope/expiration) rather than relying on the anonymous flow, and avoid uploading any media you would not want processed by an external third party.

Getting Started

Share your raw video clips and I'll get started on AI TikTok editing. Or just tell me what you're thinking.

Try saying:

• "edit my raw video clips"
• "export 1080p MP4"
• "cut to the beat, add trending"

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.

AI TikTok Editor — Edit and Export TikTok Videos

This tool takes your raw video clips and runs AI TikTok editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 60-second vertical phone recording and want to cut to the beat, add trending captions, and export for TikTok — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: vertical 9:16 footage processes and exports best for TikTok without cropping.

Matching Input to Actions

User prompts referencing editor ai 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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 editor-ai-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).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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

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.

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 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut to the beat, add trending captions, and export for TikTok" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for direct TikTok upload compatibility.

Common Workflows

Quick edit: Upload → "cut to the beat, add trending captions, and export for TikTok" → Download MP4. Takes 30-60 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.