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

Cover Generator

by @whitejohnk-26

generate images or video into video cover images with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. YouTubers, content creators, marketers use...

Versionv1.0.0
Downloads306
#writing#video#legal
TERMINAL
clawhub install cover-generator

πŸ“– About This Skill

name: cover-generator version: "1.0.0" displayName: "Cover Generator β€” Generate Covers for Videos" description: > generate images or video into video cover images with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. YouTubers, content creators, marketers use it for generating thumbnail covers for YouTube or social media videos β€” processing takes 15-30 seconds on cloud GPUs and you get 1080p MP4 files. metadata: {"openclaw": {"emoji": "πŸ–ΌοΈ", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "greeting_v2"}}

Getting Started

> Send me your images or video and I'll handle the AI cover image generation. Or just describe what you're after.

Try saying:

  • "generate a 2-minute YouTube video or a product photo into a 1080p MP4"
  • "generate a thumbnail cover for my video with bold title text"
  • "generating thumbnail covers for YouTube or social media videos for YouTubers, content creators, marketers"

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

    Cover Generator β€” Generate Covers for Videos

    Drop your images or video in the chat and tell me what you need. I'll handle the AI cover image generation on cloud GPUs β€” you don't need anything installed locally.

    Here's a typical use: you send a a 2-minute YouTube video or a product photo, ask for generate a thumbnail cover for my video with bold title text, and about 15-30 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

    One thing worth knowing β€” uploading a still frame from your video gives the AI better context for the cover.

    Matching Input to Actions

    User prompts referencing cover generator, 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 calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

    1. Session β€” POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":""}. 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. Upload β€” POST /api/upload-video/nemo_agent/me/ β€” multipart file or JSON with URLs. 4. Credits β€” GET /api/credits/balance/simple β€” returns available, frozen, total. 5. State β€” GET /api/state/nemo_agent/me//latest β€” current draft and media info. 6. Export β€” POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/ every 30s for completed status and download URL.

    Formats: 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 cover-generator, 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 , X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

    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)

    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.

    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

    • Common Workflows

    Quick edit: Upload β†’ "generate a thumbnail cover for my video with bold title text" β†’ Download MP4. Takes 15-30 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 "generate a thumbnail cover for my video with bold title text" β€” concrete instructions get better results.

    Max file size is 200MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

    Export as MP4 for widest compatibility.

    πŸ’‘ Examples

    > Send me your images or video and I'll handle the AI cover image generation. Or just describe what you're after.

    Try saying:

  • "generate a 2-minute YouTube video or a product photo into a 1080p MP4"
  • "generate a thumbnail cover for my video with bold title text"
  • "generating thumbnail covers for YouTube or social media videos for YouTubers, content creators, marketers"

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

    Cover Generator β€” Generate Covers for Videos

    Drop your images or video in the chat and tell me what you need. I'll handle the AI cover image generation on cloud GPUs β€” you don't need anything installed locally.

    Here's a typical use: you send a a 2-minute YouTube video or a product photo, ask for generate a thumbnail cover for my video with bold title text, and about 15-30 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

    One thing worth knowing β€” uploading a still frame from your video gives the AI better context for the cover.