Jogg Ai Image To Video

Get animated video clips ready to post, without touching a single slider. Upload your static images (JPG, PNG, WEBP, HEIC, up to 200MB), say something like "...

Security Scan

The skill's declared purpose (convert images to short videos) aligns with the requests it makes (a single NEMO_TOKEN and calls to nemovideo.ai); there are minor metadata inconsistencies and you should still review privacy/trust before uploading images.

Purpose & Capability

The skill's name/description match the actions in SKILL.md: uploading images, creating sessions, rendering, and returning video URLs on mega-api-prod.nemovideo.ai. Requesting NEMO_TOKEN is coherent for an API-backed renderer. One inconsistency: the SKILL.md frontmatter advertises a config path (~/.config/nemovideo/) while the registry metadata listed no required config paths — this is likely benign but worth confirming.

Instruction Scope

Runtime instructions stay within the described domain: authenticate (or obtain an anonymous token), create a session, upload media, use SSE for edits, poll export status, and return download URLs. The skill instructs generating an anonymous token if NEMO_TOKEN is not present and to avoid showing raw tokens to users. The instructions do not ask the agent to read unrelated files, other service credentials, or arbitrary system data.

Install Mechanism

No install spec and no code files — instruction-only skill. No downloads or archive extraction. This is the lowest install risk.

Credentials

Only NEMO_TOKEN is required/declared as the primary credential, which is proportionate to a cloud-rendering API. The frontmatter's mention of a config path (~/.config/nemovideo/) is not reflected in the registry metadata; it could indicate the skill expects or can use a local config directory but SKILL.md doesn't instruct reading it. No other unrelated credentials are requested.

Persistence & Privilege

always:false (not force-included). The skill suggests storing session_id and using tokens for subsequent requests, which is normal for an API client. It does not request to modify other skills or global agent settings.

Assessment

This skill appears to do what it says: it uploads images to a nemovideo.ai backend to render short videos and only needs an API token. Before installing, consider: (1) Privacy — your images (up to 200MB) will be sent to an external service; avoid uploading sensitive or private photos unless you trust the provider. (2) Token handling — the skill can auto-generate an anonymous token if NEMO_TOKEN is not set; if you prefer control, set NEMO_TOKEN yourself. (3) Metadata mismatch — the frontmatter mentions a local config path (~/.config/nemovideo/) which the registry did not list; confirm whether the skill will read or write local files if that matters. (4) Trust the domain — requests go to mega-api-prod.nemovideo.ai; if you need stronger assurance, ask for a homepage, privacy policy, or the operator identity before use. If you are comfortable with those trade-offs, the skill is internally consistent and low-risk from an installation perspective.

Getting Started

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

Try saying:

• "convert my static images"
• "export 1080p MP4"
• "convert this image into a short"

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 <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. 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.

Jogg AI Image to Video — Convert Images into Video Clips

This tool takes your static images and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a single product photo or portrait image and want to convert this image into a short animated video clip — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

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

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	jogg-ai-image-to-video
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.

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)

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 this image into a short animated video clip" → 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 "convert this image into a short animated video clip" — 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 social platforms.