Free Image Maker

Skip the learning curve of professional editing software. Describe what you want — create a promotional image with my logo and product on a white background...

Security Scan

The skill's instructions and required credential (NEMO_TOKEN) are coherent with an image-generation service that uploads user files to a remote GPU-backed API, but there are metadata inconsistencies and privacy implications you should consider before installing.

Purpose & Capability

Name/description (image generation, uploads, exports) align with the declared primary credential NEMO_TOKEN and the API endpoints in SKILL.md. However, registry metadata earlier listed no required config paths while the SKILL.md YAML frontmatter declares a configPaths entry (~/.config/nemovideo/). The skill's unknown source/homepage increases uncertainty about provenance.

Instruction Scope

Runtime instructions stay within the image-generation scope: establish a session, optionally obtain an anonymous token, upload media, stream edits via SSE, and poll for exports. Notable operational behaviors: the agent is told to POST user files and metadata to a third-party API, to generate a UUID and exchange it for a token if none is present, and to detect the install path to set an X-Skill-Platform header (which implies reading agent install paths). These actions are expected for this service but do involve sending user content and reading local install path information.

Install Mechanism

Instruction-only skill with no install spec and no code files, so nothing is downloaded or written by an installer. This is the lowest-risk install mechanism in terms of arbitrary code being pulled from the network.

Credentials

Only one credential is declared (NEMO_TOKEN), which is proportional for calling the provider's API. The skill also documents an anonymous-token flow (POST to /api/auth/anonymous-token) to obtain a short-lived token if none is present. The frontmatter's configPaths entry (~/.config/nemovideo/) is declared in the SKILL.md metadata but not listed in the registry summary; this mismatch should be clarified. The skill will transmit whatever user files are uploaded to theremote API — ensure you are comfortable with that.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and does not request system-wide privileges. It stores session_id and uses it for API calls (normal behavior). Autonomous invocation is allowed (platform default) but not an additional privilege requested by the skill.

Assessment

This skill appears to do what it says (remote image/video rendering) and only requires the provider token, but before installing you should: (1) confirm the skill's origin or vendor (there's no homepage or source URL in the registry entry); (2) understand that any files you upload will be sent to mega-api-prod.nemovideo.ai — avoid uploading sensitive or proprietary images until you verify the provider's privacy/BYOD/billing policies; (3) prefer using the anonymous-token flow for ephemeral access rather than placing a long-lived token in your environment; (4) ask the publisher to clarify the configPaths discrepancy (~/.config/nemovideo/ appears in the skill metadata but not in the registry summary) and why the agent must detect install paths for the X-Skill-Platform header; and (5) if you need higher assurance, request a verifiable homepage, privacy policy, or source repository before trusting the skill with sensitive content.

Getting Started

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

Try saying:

• "generate three product photos and a brand description into a 1080p MP4"
• "create a promotional image with my logo and product on a white background"
• "generating custom images from text prompts or uploaded photos for marketers, bloggers, social media creators"

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.

Free Image Maker — Generate and Export Custom Images

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

A quick example: upload three product photos and a brand description, type "create a promotional image with my logo and product on a white background", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: simple, descriptive prompts produce sharper results than vague ones.

Matching Input to Actions

User prompts referencing free image maker, 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.

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

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

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 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 promotional image with my logo and product on a white background" — concrete instructions get better results.

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

Export as PNG for transparent backgrounds or MP4 for animated image slideshows.

Common Workflows

Quick edit: Upload → "create a promotional image with my logo and product on a white background" → 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.