Image To Video Bot Telegram

Turn three product photos or a single portrait image into 1080p animated video clips just by typing what you need. Whether it's converting still images into...

Security Scan

This instruction-only skill is internally consistent: it routes uploaded images to a nemovideo.ai backend and requires a single service token (NEMO_TOKEN), which matches its stated purpose.

Purpose & Capability

Name/description (image→video via Telegram) align with the actions in SKILL.md (upload images, create render jobs, return download URLs). One small mismatch: the registry metadata lists no required config paths, while the SKILL.md frontmatter metadata mentions a config path (~/.config/nemovideo/). That appears minor and does not change the core purpose.

Instruction Scope

The instructions consistently describe contacting the nemovideo.ai API (auth, session creation, uploads, SSE for chat/edits, render/export polling). They require uploading user images to the remote backend and handling tokens; those actions are necessary for the stated functionality. The skill also asks the agent to read its frontmatter/version and detect install path (to populate attribution headers) — this involves checking local paths but is limited to attribution and not broad data collection.

Install Mechanism

No install spec and no code files — instruction-only. This is lowest-risk from an install perspective because nothing is downloaded or written by an installer.

Credentials

Only a single credential (NEMO_TOKEN) is required and used by the SKILL.md. The doc explains fallback behavior (request an anonymous token from the backend if NEMO_TOKEN is absent). That is proportional to a cloud-rendering service. There is no request for unrelated credentials.

Persistence & Privilege

Skill is not forced-always, and it does not request system-wide privileges. It does instruct storing the session_id in-memory for operations but does not ask to modify other skills or system settings.

Assessment

This skill will upload images and session data to mega-api-prod.nemovideo.ai and needs a NEMO_TOKEN (or it will obtain a short-lived anonymous token). Before installing, confirm you are comfortable sending images (possibly sensitive) to that external service and review the service's privacy/terms. Note the skill will attempt to include attribution headers (reading its own frontmatter/version and checking common install paths) — this is benign but means the agent may inspect small local paths for attribution. Also verify the backend domain (mega-api-prod.nemovideo.ai) is the expected vendor; the skill's source/homepage are missing, so exercise extra caution and avoid providing long-lived or privileged credentials beyond the intended NEMO_TOKEN.

Getting Started

Got images to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "convert three product photos or a single portrait image into a 1080p MP4"
• "convert my photos into a smooth video with transitions"
• "converting still images into short videos via Telegram bot for Telegram users and social media creators"

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.

Image to Video Bot Telegram — Convert Images into Video Clips

Send me your images and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload three product photos or a single portrait image, type "convert my photos into a smooth video with transitions", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: high-contrast images with clear subjects produce smoother motion results.

Matching Input to Actions

User prompts referencing image to video bot telegram, 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":"<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. Upload — POST /api/upload-video/nemo_agent/me/<sid> — 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/<sid>/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/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: image-to-video-bot-telegram
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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)

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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 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=<id>, 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 → "convert my photos into a smooth video with transitions" → Download MP4. Takes 20-40 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 "convert my photos into a smooth video with transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across all platforms and devices.