Uncensored Ai Image To Video

convert still images into animated video clips with this skill. Works with JPG, PNG, WEBP, BMP files up to 200MB. digital artists, content creators, adult co...

Security Scan

The skill mostly matches an image→video service but has a few inconsistent or unclear instructions (metadata vs registry, implicit filesystem detection, automatic token minting/storage and remote upload of user images) that warrant caution before installing.

Purpose & Capability

Name and description match the runtime instructions (upload image → remote GPU render → download MP4). Requesting a single service credential (NEMO_TOKEN) is coherent. However, the SKILL.md metadata declares a config path (~/.config/nemovideo/) and platform-detection logic based on install paths, while the registry summary lists no required config paths — this inconsistency is unexplained and could cause the agent to access local filesystem locations it doesn't need to.

Instruction Scope

Most runtime steps stay within the stated purpose (create session, upload images, SSE for progress, poll export). But the instructions also: (a) auto-create and store an anonymous token if NEMO_TOKEN is not set, (b) instruct the agent to include a platform header derived from the install path (implies probing filesystem paths), and (c) the SKILL.md metadata references a local config path. The skill will transmit user images and metadata to https://mega-api-prod.nemovideo.ai — expected for a cloud render service but important to note. The combination of automatic token minting, hidden storage, and implicit filesystem checks increases the attack surface and privacy risk.

Install Mechanism

Instruction-only skill with no install spec or code files — nothing is downloaded or written by an installer. This minimizes supply-chain risk.

Credentials

Only one credential is declared (NEMO_TOKEN), which is appropriate for a third-party API. However, the skill offers to mint and store an anonymous token automatically and also references a config path in its metadata that could contain other secrets; the registry summary did not list that config path. Ask whether the skill will read that config directory and where it stores tokens.

Persistence & Privilege

The skill is not always:true and does not request elevated system privileges. It will store a session_id/token for its own requests, which is normal for a remote service client. It does not claim to modify other skills or system-wide settings.

What to consider before installing

This skill appears to be a straightforward cloud image→video renderer, but before installing: 1) Verify the backend domain (mega-api-prod.nemovideo.ai) — do you trust that third-party service and its privacy/terms, especially since it advertises 'uncensored' uploads? 2) Decide whether to set NEMO_TOKEN yourself (recommended) rather than allowing the skill to generate and store an anonymous token. 3) Ask the publisher or inspect runtime logs (if possible) whether the agent will read ~/.config/nemovideo/ or probe install paths — that behavior is not necessary for rendering and could expose local config. 4) Remember all images are uploaded to a remote service; do not upload anything you consider highly sensitive. If you cannot confirm the domain, storage location for tokens, or why the config path is needed, treat this skill with caution or avoid installing it.

Getting Started

Ready when you are. Drop your still images here or describe what you want to make.

Try saying:

• "convert a single portrait photo or illustrated scene into a 1080p MP4"
• "animate this image into a 5-second video clip with natural motion"
• "converting static images into short animated video clips without content restrictions for digital artists, content creators, adult content creators"

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.

Uncensored AI Image to Video — Animate Images Into Video Clips

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

A quick example: upload a single portrait photo or illustrated scene, type "animate this image into a 5-second video clip with natural motion", and you'll get a 1080p MP4 back in roughly 30-90 seconds. All rendering happens server-side.

Worth noting: higher resolution input images produce smoother and more detailed motion output.

Matching Input to Actions

User prompts referencing uncensored 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is uncensored-ai-image-to-video, 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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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

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 Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Common Workflows

Quick edit: Upload → "animate this image into a 5-second video clip with natural motion" → Download MP4. Takes 30-90 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 "animate this image into a 5-second video clip with natural motion" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for widest compatibility across platforms.