Image To Video Ai Discord

convert still images into animated video clips with this skill. Works with JPG, PNG, WEBP, GIF files up to 200MB. Discord community members use it for conver...

Security Scan

The skill's instructions and requested NEMO_TOKEN credential line up with its stated image→video purpose, but there are small inconsistencies (unknown source, an unused local config path declaration, and headers that require exposing install-path info) that warrant caution before installing.

Purpose & Capability

The skill claims to convert images to videos via a remote API and only requests a single credential (NEMO_TOKEN), which is appropriate. However the metadata also declares a local config path (~/.config/nemovideo/) that the SKILL.md never instructs the agent to read — this is an unexplained mismatch (likely benign/oversight but worth flagging).

Instruction Scope

SKILL.md instructs the agent to create/consume an anonymous token, create sessions, upload user files (multipart or by URL), stream SSE responses, poll render status, and include three attribution headers on every request. Those actions are coherent with remote rendering. Minor concern: the requirement to auto-detect X-Skill-Platform from the install path implies the agent may inspect its install location or environment, which is outside the narrow remit of pure media conversion.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest-risk distribution mechanism. Nothing is downloaded or written by an installer.

Credentials

Only a single credential (NEMO_TOKEN) is declared and used in the instructions (including a supported anonymous-token flow). That is proportional to the skill's remote-API workflow. Still: NEMO_TOKEN grants the skill the power to upload user files and trigger renders on an external service, so treat the token as sensitive.

Persistence & Privilege

The skill does not request always:true and has no install-time persistence. It stores/transmits ephemeral session IDs to the backend per the instructions; there is no evidence it modifies other skills or system-wide settings.

What to consider before installing

This skill appears to do what it says — it uploads images to mega-api-prod.nemovideo.ai and returns rendered videos — but take these precautions before installing: - Source and provenance: the registry metadata shows no homepage and an opaque owner ID. If you require provenance, avoid installing until you can verify the publisher or find an official project page. - Privacy: any image you send will be uploaded to the remote service. Do not upload sensitive or private images unless you trust the service and its retention policy. - Token handling: NEMO_TOKEN is effectively an API key. Use an anonymous/ephemeral token if possible (the SKILL.md documents how to request one). Do not paste long-lived secrets you use elsewhere. - Local config mismatch: the skill declares ~/.config/nemovideo/ in metadata but the runtime instructions don't reference it; that mismatch is likely a packaging oversight but verify nothing on your agent will read local files you don't expect. - Headers/install-path: the skill asks that X-Skill-Platform be auto-detected from an install path. Confirm the agent won't leak other local path or system information when doing that auto-detection. If you are comfortable with those trade-offs (uploading images to the external endpoint and granting the skill a single token), this skill is functionally coherent; otherwise skip or request a skill with verifiable source/maintainer information.

Getting Started

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

Try saying:

• "convert my still images"
• "export 1080p MP4"
• "turn my images into a short"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Image to Video AI Discord — Convert Images into Discord Videos

Send me your still 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 or character images, type "turn my images into a short animated video I can share in Discord", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: keep images under 10MB each for faster processing and smoother output.

Matching Input to Actions

User prompts referencing image to video ai discord, 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.

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

Header	Value
X-Skill-Source	image-to-video-ai-discord
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-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.

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.

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

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 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 → "turn my images into a short animated video I can share in Discord" → 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 "turn my images into a short animated video I can share in Discord" — concrete instructions get better results.

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

Export as MP4 for widest compatibility with Discord's video player.