Douyin Short Video

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — cut into a 15-second Douyin clip with music and captions — and get vertica...

0· 26·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 francemichaell-15/douyin-short-video.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Douyin Short Video" (francemichaell-15/douyin-short-video) from ClawHub.
Skill page: https://clawhub.ai/francemichaell-15/douyin-short-video
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 douyin-short-video

ClawHub CLI

Package manager switcher

npx clawhub@latest install douyin-short-video
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description match the required NEMO_TOKEN and the documented API endpoints (mega-api-prod.nemovideo.ai). Requesting a service token and a config path under ~/.config/nemovideo/ is consistent with a cloud video-rendering client.
Instruction Scope
SKILL.md instructs the agent to check for NEMO_TOKEN, create an anonymous token if missing, create sessions, upload user video files, and poll render status — all consistent with a cloud render pipeline. It will send user video files and metadata to the specified API; it also asks the agent to auto-detect platform/install path for an attribution header (this implies reading the agent's install path), which is minor but worth noting.
Install Mechanism
Instruction-only skill with no install spec or downloaded code—lowest-risk installation footprint.
Credentials
Only requests a single service credential (NEMO_TOKEN) and documents how to obtain one anonymously if absent. The declared config path is plausible for storing client config. No unrelated secrets or credentials are requested.
Persistence & Privilege
Does not request always:true or other elevated privileges, nor does it instruct changing other skills or global agent settings.
Assessment
This skill will upload any video files you give it to https://mega-api-prod.nemovideo.ai and may automatically obtain an anonymous NEMO_TOKEN if you don't supply one. That behavior is expected for a cloud-rendering tool, but before installing: (1) confirm you trust the nemovideo service/privacy policy for the videos you plan to upload (sensitive content should be avoided), (2) if you prefer control, set your own NEMO_TOKEN in the environment instead of letting the skill create one, and (3) be aware the skill may read the agent install path to set an attribution header. There are no other unexpected credential requests or install-time downloads.

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

Runtime requirements

🎵 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk977f2kg4tn2asbsp97ghrs39d85pc8r
26downloads
0stars
1versions
Updated 9h ago
v1.0.0
MIT-0

Getting Started

Share your raw video footage and I'll get started on AI short video creation. Or just tell me what you're thinking.

Try saying:

  • "create my raw video footage"
  • "export 1080p MP4"
  • "cut into a 15-second Douyin clip"

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.

Douyin Short Video — Create and Export Douyin Clips

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

Say you have a 3-minute phone recording of a daily vlog and want to cut into a 15-second Douyin clip with music and captions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: keep source clips under 5 minutes for fastest processing.

Matching Input to Actions

User prompts referencing douyin short video, 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.

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

HeaderValue
X-Skill-Sourcedouyin-short-video
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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.

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 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 → "cut into a 15-second Douyin clip with music and captions" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut into a 15-second Douyin clip with music and captions" — 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 best compatibility with Douyin uploads.

Comments

Loading comments...