
Libtv Video
Seedance 2.0 video & image generation via LibTV Gateway - AI text-to-video...
Install
npx skills add nexu-io/nexu --skill libtv-video -g -a claude-code -y- Repository
- nexu-io/nexu3.3k
- Category
- Media
- Updated
- 6mo ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Seedance 2.0 video & image generation via LibTV Gateway - AI text-to-video, image-to-video, video continuation, style transfer, and text-to-image using Seedance 2.0 model. Also supports Kling 3.0, Wan 2.6, Midjourney, Seedream 5.0. Trigger phrases: seedance, generate video, make a video, generate image, make an image, draw, libtv, liblib.
LibTV - Image & Video Generation (Seedance 2.0)
Generate AI images and videos through one bundled LibTV skill, powered by Seedance 2.0. Supports text-to-image, image-to-image, text-to-video, and image-to-video workflows, via both Nexu-managed Seedance execution and direct LibTV execution with a user-owned sk-libtv-... key.
Key routing:
mgk_...keys use Nexu-managed Seedance throughhttps://seedance.nexu.io/sk-libtv-...keys use direct LibTV OpenAPI throughhttps://im.liblib.tv
Delivery architecture (currently Feishu only):
create-sessioncapturesOPENCLAW_CHANNEL_TYPE+OPENCLAW_CHAT_ID, persists them as the session'sdeliveryblock, forks a detachedwait-and-deliverbackground process viasubprocess.Popen(..., start_new_session=True), and returns immediately with a single-line JSON submit confirmation on stdout.- The forked waiter polls the upstream LibTV API (Seedance gateway or
direct LibTV) and, on terminal success, shells out to
feishu_send_video.py, the same proven helper used bymedeo-video, which downloads each result URL, uploads it to Feishu's file API, and posts a native media message to the originating chat. - The waiter's output is captured in
$NEXU_HOME/libtv-waiter-<id>.logfor post-hoc debugging. Adelivered_attimestamp is persisted when the Feishu helper reports success, so re-invokingwait-and-deliveron a delivered session is a safe no-op.
No sessions_spawn, no subagent model-speech contract, no HTTP
notification callback, no stale routing fields. Delivery is a direct
HTTP call using stable per-user identifiers (open_id / chat_id)
that never go stale the way the old account_id did.
Multi-channel support is a follow-up: adding Discord / Slack / WeChat
means dropping a new <channel>_send_video.py helper next to
feishu_send_video.py and adding one branch in _deliver_results.


