Tiktok Video Editing With

v1.0.0

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

0· 98·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/tiktok-video-editing-with.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Tiktok Video Editing With" (vynbosserman65/tiktok-video-editing-with) from ClawHub.
Skill page: https://clawhub.ai/vynbosserman65/tiktok-video-editing-with
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 tiktok-video-editing-with

ClawHub CLI

Package manager switcher

npx clawhub@latest install tiktok-video-editing-with
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description, required env var (NEMO_TOKEN), and instructions all point to a single external video-editing backend (mega-api-prod.nemovideo.ai). There are no unrelated credentials or binaries requested.
Instruction Scope
Instructions direct the agent to upload user media and interact with the remote API (create session, SSE chat, upload, export). This is expected for a cloud render workflow. Minor scope notes: the frontmatter mentions a config path (~/.config/nemovideo/) and automatic detection of install path for X-Skill-Platform — the SKILL.md does not clearly explain what local path reading (if any) is required; that could require the agent to inspect its install environment for a platform string.
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing is written to disk by an installer, which keeps install risk low.
Credentials
Only NEMO_TOKEN is declared as required, which is proportional to a third‑party API integration. Small inconsistency: the SKILL.md frontmatter metadata lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths; confirm whether the skill will attempt to read that path or other local config files before installing.
Persistence & Privilege
always is false and the skill does not request persistent agent-wide privileges or modify other skills. Autonomous invocation is allowed (platform default) — expected for skills.
Assessment
This skill appears coherent: it uploads and edits videos on the nemo video backend and needs a NEMO_TOKEN (or will obtain a short-lived anonymous token). Before installing, consider: 1) Privacy — user videos will be uploaded to mega-api-prod.nemovideo.ai; review that service's terms and retention policy. 2) Credential use — the agent will send your NEMO_TOKEN as a Bearer token in requests; only provide a token if you trust the backend. 3) Confirm the minor metadata mismatch: the frontmatter mentions ~/.config/nemovideo/ and auto-detecting an install path for X-Skill-Platform; ask the publisher whether the agent will read local config or install paths. If you need stronger guarantees, test with non-sensitive media first or use the anonymous-token flow instead of an account token.

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

Runtime requirements

🎵 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk9746j36a5geb2edyzqc7jsqr184njea
98downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

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 best 30 seconds,"

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.

TikTok Video Editing With AI — Edit and Export TikTok Videos

Send me your raw video clips and describe the result you want. The AI TikTok editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute vertical phone recording, type "cut to the best 30 seconds, add trending text overlays and sync cuts to the beat", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: keeping clips under 60 seconds gives the AI more precise cut suggestions.

Matching Input to Actions

User prompts referencing tiktok video editing with, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

  1. SessionPOST /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. UploadPOST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
  4. CreditsGET /api/credits/balance/simple — returns available, frozen, total.
  5. StateGET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
  6. ExportPOST /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.

Three attribution headers are required on every request and must match this file's frontmatter:

HeaderValue
X-Skill-Sourcetiktok-video-editing-with
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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.

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)

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut to the best 30 seconds, add trending text overlays and sync cuts to the beat" — concrete instructions get better results.

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

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

Common Workflows

Quick edit: Upload → "cut to the best 30 seconds, add trending text overlays and sync cuts to the beat" → 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.

Comments

Loading comments...