Image Editing Generator

Get edited image videos ready to post, without touching a single slider. Upload your images or photos (JPG, PNG, WEBP, HEIC, up to 200MB), say something like...

Security Scan

The skill's requirements and runtime instructions are coherent with an image-editing cloud service: it needs a single service token, talks to a nemo video API, and has no install steps or unrelated credential requests.

Purpose & Capability

The name/description (cloud image editing and video export) aligns with the runtime actions in SKILL.md: uploading images, creating sessions, sending edits, polling export status. Requesting a single service token (NEMO_TOKEN) is consistent with calling that API.

Instruction Scope

Instructions direct the agent to obtain/use a service token, create a session, upload files, stream edits via SSE, poll render status, and return download URLs. These actions match the stated purpose. One minor scope note: the frontmatter mentions a config path (~/.config/nemovideo/) even though the registry metadata listed none; SKILL.md does not otherwise instruct the agent to read unrelated system files or other environment variables.

Install Mechanism

There is no install spec and no code files — runtime behavior is fully covered by SKILL.md network calls. This is the lowest install risk (nothing is written to disk by the skill itself).

Credentials

The only credential required is NEMO_TOKEN (primaryEnv), which matches the cloud API usage. Minor inconsistency: SKILL.md/frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata indicated no required config paths; unclear whether the skill expects to read/write that path.

Persistence & Privilege

always is false and the skill has no install-time persistence. The skill can be invoked autonomously (default platform behavior), which is expected for an integration like this and not in itself a red flag.

Scan Findings in Context

[NO_SCAN_FINDINGS] expected: The regex scanner had no code to analyze (instruction-only skill). Absence of findings is expected but not a security guarantee; the runtime instructions are the primary surface to review.

Assessment

This skill appears to do what it says: upload images to nemo video's cloud, run edits server-side, and return a video URL. Before installing/using it: 1) Understand that your images will be uploaded to https://mega-api-prod.nemovideo.ai — do not send sensitive or regulated images unless you trust this service and its privacy terms. 2) NEMO_TOKEN is the only required credential; the skill can also fetch a short-lived anonymous token automatically if none is set — consider whether you want to supply your own token or let it obtain one. 3) There is an inconsistency about a config path (~/.config/nemovideo/) declared in the skill frontmatter but not in registry metadata — ask the publisher whether the skill will read/write that directory. 4) If you need stronger assurance, request the skill's source or a homepage, verify the nemo video domain ownership/terms, or run the workflow with non-sensitive test images first.

Getting Started

Share your images or photos and I'll get started on AI image editing. Or just tell me what you're thinking.

Try saying:

• "edit my images or photos"
• "export 1080p MP4"
• "remove the background, adjust brightness, and"

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.

Image Editing Generator — Edit Images and Export Videos

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

A quick example: upload three product photos in JPG format, type "remove the background, adjust brightness, and add a text overlay", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: higher resolution images produce sharper output but take slightly longer to process.

Matching Input to Actions

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

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	image-editing-generator
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 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

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 "remove the background, adjust brightness, and add a text overlay" — 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.

Common Workflows

Quick edit: Upload → "remove the background, adjust brightness, and add a text overlay" → 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.