Design Generator

Turn a product name and brand color palette into 1080p designed video output just by typing what you need. Whether it's generating branded video designs from...

Security Scan

The skill's behavior matches a cloud-based video-renderer (NEMO_TOKEN, API endpoints, upload/export flow), but it will automatically acquire/use tokens and send user uploads to an external, unvetted domain with no homepage or publisher information — proceed cautiously.

Purpose & Capability

The declared purpose (generate branded 1080p videos) aligns with the instructions: session creation, upload, SSE-based editing, export/polling and download. Required credential (NEMO_TOKEN) is consistent with a third‑party API. Minor incoherence: the SKILL.md frontmatter references a config path (~/.config/nemovideo/) not listed in the registry metadata; the skill source/homepage is unknown which reduces trust even though the technical requirements are plausible.

Instruction Scope

Runtime instructions explicitly upload user images/text and stream edits to https://mega-api-prod.nemovideo.ai and require anonymous token creation if no NEMO_TOKEN is present. That behavior is expected for a cloud render service but means user data (and potentially any files the user supplies) will be transmitted to a third party. The skill also instructs polling and SSE handling and to store/use a session token. There are no instructions that read unrelated system files, but automatic token generation and persistent session handling broaden the data the skill will send externally.

Install Mechanism

Instruction-only skill with no install spec or downloaded code; no binaries installed. This minimizes filesystem/installation risk.

Credentials

Only one credential (NEMO_TOKEN) is required and is appropriate for an API-backed renderer. However SKILL.md frontmatter lists a config path (~/.config/nemovideo/) which was not in the registry's required config paths — that mismatch should be clarified. The skill also instructs creating an anonymous token via the API if NEMO_TOKEN is absent, which implicitly gives the service a persistent credential (7‑day expiry) and could be stored for reuse.

Persistence & Privilege

always:false and the skill does not request system-wide configuration changes or access to other skills' credentials. Autonomous invocation is allowed (platform default) but not an additional flagged privilege here.

What to consider before installing

This skill appears to do what it says (remote video rendering) but it will upload any images/text you provide to an external service (mega-api-prod.nemovideo.ai) and will generate/use an anonymous NEMO_TOKEN if you don't supply one. There is no homepage or publisher info to verify the service. Before installing or using: 1) Avoid uploading sensitive images or private data. 2) Prefer providing a token you control only if you trust the provider; otherwise expect the skill to mint a short‑lived anonymous token. 3) Ask the publisher for documentation, privacy/terms links, and details on where tokens are stored (in-memory vs saved to ~/.config). 4) Clarify the configPath discrepancy in the metadata. If you cannot verify the service identity and data handling, treat this skill as untrusted for confidential content.

Getting Started

Got images or text to work with? Send it over and tell me what you need — I'll take care of the AI design creation.

Try saying:

• "generate a product name and brand color palette into a 1080p MP4"
• "generate a promotional video with animated design elements and logo"
• "generating branded video designs from images or text prompts for marketers"

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.

Design Generator — Generate Videos from Design Assets

This tool takes your images or text and runs AI design creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a product name and brand color palette and want to generate a promotional video with animated design elements and logo — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: simpler input prompts with clear brand colors produce more consistent results.

Matching Input to Actions

User prompts referencing design 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	design-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 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 → "generate a promotional video with animated design elements and logo" → Download MP4. Takes 30-60 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 "generate a promotional video with animated design elements and logo" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.