Image Generation Generator

generate text prompts into AI generated visuals with this skill. Works with JPG, PNG, WEBP, MP4 files up to 200MB. content creators use it for generating ima...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud image/video generation integration and request only a service token; nothing in the package indicates it is doing something other than what it claims.

Purpose & Capability

The skill's name, description, and runtime instructions all target an external Nemo video/image generation API and require a NEMO_TOKEN — this is proportionate. Minor inconsistency: the registry metadata at the top-level lists no required config paths, while the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) to read. That mismatch is likely benign but worth confirming with the author.

Instruction Scope

SKILL.md instructs the agent to authenticate (use NEMO_TOKEN or obtain an anonymous token via the public API), create sessions, send SSE requests, upload user files (multipart or via URL), poll render status, and translate SSE events to user-visible messages. These actions are all consistent with the described function. Scope notes: the skill asks the agent to read its own YAML frontmatter for attribution headers and to detect install path (e.g., ~/.clawhub/, ~/.cursor/skills/) — this requires inspecting known filesystem locations. It also references a config path (~/.config/nemovideo/) in frontmatter. Reading those locations is plausible for attribution but could expose local files if implemented broadly; the instructions do not ask for unrelated files or credentials beyond NEMO_TOKEN.

Install Mechanism

There is no install spec and no code files — instruction-only skill. This is lower-risk because nothing is downloaded or written to disk by an installer step.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required and used for API Bearer auth, which matches the skill's purpose. The skill also documents how to obtain an anonymous token via the service API if NEMO_TOKEN is not provided. The only proportional concern is the SKILL.md's mention of a local config path (~/.config/nemovideo/) which could contain additional tokens/settings; the top-level registry did not declare that path as required — this discrepancy should be clarified.

Persistence & Privilege

The skill is not force-installed (always:false) and does not request elevated or persistent system privileges. It does instruct detecting install location and (optionally) reading a service config directory, but it does not request to modify other skills or system-wide settings. Autonomous invocation is enabled (default) which is expected for skills.

Assessment

This skill appears to do what it says: it calls Nemo's cloud API to generate images/videos and needs a NEMO_TOKEN (or will request an anonymous token from the service). Before installing, consider: - Only provide a NEMO_TOKEN with the minimum privileges needed (do not reuse highly privileged or cross-service tokens). - The SKILL.md mentions reading ~/.config/nemovideo/ and checking install paths (~/.clawhub/, ~/.cursor/skills/) for attribution — confirm you’re comfortable with the skill inspecting those locations. If you prefer, run the skill without a token to force anonymous-session behavior. - Because this is instruction-only, no code will be installed, but the skill will make network requests to https://mega-api-prod.nemovideo.ai — verify that domain is expected and acceptable in your environment. - There is a minor metadata mismatch (registry says no config paths but SKILL.md lists one); if you need higher assurance, ask the publisher to clarify and to publish a homepage/source for audit.

Getting Started

Share your text prompts and I'll get started on AI image generation. Or just tell me what you're thinking.

Try saying:

• "generate my text prompts"
• "export 1080p MP4"
• "generate a photorealistic image of a"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Image Generation Generator — Generate Images From Text Prompts

This tool takes your text prompts and runs AI image generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a short text description like 'sunset over a mountain lake' and want to generate a photorealistic image of a futuristic city at night — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: shorter, more specific prompts tend to produce more accurate results.

Matching Input to Actions

User prompts referencing image generation generator, 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.

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

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

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

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

Tips and Tricks

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

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

Export as MP4 for widest compatibility when embedding generated images into video sequences.

Common Workflows

Quick edit: Upload → "generate a photorealistic image of a futuristic city 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.