🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί Video Publish
πŸ¦€ ClawHub

Video Publish

by @vynbosserman65

Turn a 2-minute edited product demo in MP4 into 1080p publish-ready videos just by typing what you need. Whether it's publishing finished videos directly to...

Versionv1.0.0
Downloads281
#video#legal
TERMINAL
clawhub install video-publish

πŸ“– About This Skill

name: video-publish version: "1.0.0" displayName: "Video Publish β€” Prepare and Publish Videos Online" description: > Turn a 2-minute edited product demo in MP4 into 1080p publish-ready videos just by typing what you need. Whether it's publishing finished videos directly to platforms without extra software or quick social content, drop your edited video files and describe the result you want. No timeline dragging, no export settings β€” 30-60 seconds from upload to download. metadata: {"openclaw": {"emoji": "πŸ“€", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "short_prompts"}}

Getting Started

> Share your edited video files and I'll get started on AI publishing preparation. Or just tell me what you're thinking.

Try saying:

  • "publish my edited video files"
  • "export 1080p MP4"
  • "optimize and publish this video to"

    • First-Time Connection

    When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

    Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

    1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN β€” 100 free credits, valid 7 days. 2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer , Content-Type: application/json, and body {"task_name":"project","language":""}. Store the returned session_id for all subsequent requests.

    Keep setup communication brief. Don't display raw API responses or token values to the user.

    Video Publish β€” Prepare and Publish Videos Online

    This tool takes your edited video files and runs AI publishing preparation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

    Say you have a 2-minute edited product demo in MP4 and want to optimize and publish this video to YouTube with a title and description β€” the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

    Tip: keeping videos under 5 minutes speeds up processing and platform upload significantly.

    Matching Input to Actions

    User prompts referencing video publish, 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 requests must include: Authorization: Bearer , X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

    Skill attribution β€” read from this file's YAML frontmatter at runtime:

  • X-Skill-Source: video-publish
  • X-Skill-Version: from frontmatter version
  • X-Skill-Platform: detect from install path (~/.clawhub/ β†’ clawhub, ~/.cursor/skills/ β†’ cursor, else unknown)

    • API base: https://mega-api-prod.nemovideo.ai

    Create session: POST /api/tasks/me/with-session/nemo_agent β€” body {"task_name":"project","language":""} β€” returns task_id, session_id.

    Send message (SSE): POST /run_sse β€” body {"app_name":"nemo_agent","user_id":"me","session_id":"","new_message":{"parts":[{"text":""}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

    Upload: POST /api/upload-video/nemo_agent/me/ β€” file: multipart -F "files=@/path", or URL: {"urls":[""],"source_type":"url"}

    Credits: GET /api/credits/balance/simple β€” returns available, frozen, total

    Session state: GET /api/state/nemo_agent/me//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_","sessionId":"","draft":,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/ 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.

    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=, 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

    • 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

    • 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.

    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)

    Common Workflows

    Quick edit: Upload β†’ "optimize and publish this video to YouTube with a title and description" β†’ 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 "optimize and publish this video to YouTube with a title and description" β€” concrete instructions get better results.

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

    Export as MP4 for widest compatibility across all publishing platforms.

    πŸ’‘ Examples

    > Share your edited video files and I'll get started on AI publishing preparation. Or just tell me what you're thinking.

    Try saying:

  • "publish my edited video files"
  • "export 1080p MP4"
  • "optimize and publish this video to"

    • First-Time Connection

    When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

    Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

    1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN β€” 100 free credits, valid 7 days. 2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer , Content-Type: application/json, and body {"task_name":"project","language":""}. Store the returned session_id for all subsequent requests.

    Keep setup communication brief. Don't display raw API responses or token values to the user.

    Video Publish β€” Prepare and Publish Videos Online

    This tool takes your edited video files and runs AI publishing preparation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

    Say you have a 2-minute edited product demo in MP4 and want to optimize and publish this video to YouTube with a title and description β€” the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

    Tip: keeping videos under 5 minutes speeds up processing and platform upload significantly.