Ai Image Creator

Cloud-based ai-image-creator tool that handles generating images from text prompts for video content. Upload JPG, PNG, WEBP, SVG files (up to 200MB), describ...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based image/video rendering tool and do not request unrelated credentials or risky installs.

Purpose & Capability

Name/description, required env var (NEMO_TOKEN), declared config path (~/.config/nemovideo/) and the API endpoints all align with a cloud image/video rendering service; nothing requested appears unrelated to the stated purpose.

Instruction Scope

SKILL.md confines operations to the nemovideo.ai backend (session creation, SSE chat, upload, export/polling). It also instructs the agent to auto-create an anonymous token if NEMO_TOKEN is not present. Minor ambiguity: headers include X-Skill-Platform determined from an install path — that implies reading the agent's install location, but the doc does not instruct reading other unrelated files.

Install Mechanism

Instruction-only skill with no install spec and no code files, so nothing is downloaded or written by an installer—lowest install risk.

Credentials

Only a single credential (NEMO_TOKEN) is required and is appropriate for a cloud API. The skill instructs generating an anonymous token via the service if none is present (ephemeral, 7-day). It's not explicit whether the token should be persisted to disk/config, though metadata lists a config path; that is a small inconsistency to be aware of.

Persistence & Privilege

always: false and no install actions. The skill can be invoked autonomously (default) which is expected behavior; it does not request elevated platform privileges or modify other skills/configs.

Assessment

This skill routes your prompts and any uploaded media to mega-api-prod.nemovideo.ai and requires a NEMO_TOKEN (or will request an anonymous token from the service). Before installing, confirm you trust nemovideo.ai with your media and understand their privacy/retention and billing model (anonymous tokens have limited credits and expire). Ask the publisher whether the token is persisted (and where) if you are concerned about long-lived credentials in ~/.config/nemovideo/. If you do not want autonomous calls to an external service, avoid enabling autonomous invocation or do not provide a private NEMO_TOKEN. Overall the skill appears coherent for its stated purpose, but exercise normal caution when sending private or sensitive media to an external cloud API.

Getting Started

Got text prompts to work with? Send it over and tell me what you need — I'll take care of the AI image generation.

Try saying:

• "generate a short text description like 'sunset over a mountain lake' into a 1080p MP4"
• "create a realistic image of a futuristic city skyline at night"
• "generating images from text prompts for video content for content 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.

AI Image Creator — Generate Images From Text Prompts

Drop your text prompts in the chat and tell me what you need. I'll handle the AI image generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short text description like 'sunset over a mountain lake', ask for create a realistic image of a futuristic city skyline at night, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — more specific prompts produce more accurate and usable images.

Matching Input to Actions

User prompts referencing ai image creator, 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 ai-image-creator, 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 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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a realistic image of a futuristic city skyline at night" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "create a realistic image of a futuristic city skyline at night" → 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.