Generator Skill

Skip the learning curve of professional editing software. Describe what you want — generate a 30-second video of a sunset beach scene with upbeat background...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud video-generation integration and do not request unrelated credentials or risky installs.

Purpose & Capability

The skill is a cloud video-generation front end and only asks for a service token (NEMO_TOKEN) and interactions with the nemo API; those map to its stated purpose. Declared primaryEnv is NEMO_TOKEN which is appropriate.

Instruction Scope

SKILL.md directs the agent to obtain/use NEMO_TOKEN, create sessions, upload files, stream SSE responses, and poll render status — all consistent with a cloud video generator. It also instructs the agent to detect install path and read this file's YAML frontmatter for attribution headers (reading local agent paths like ~/.clawhub/ or ~/.cursor/skills/). That filesystem detection is not required for core generation but is only for attribution headers; it is a minor scope creep to be aware of.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest risk from install mechanism (nothing downloaded or written by an installer).

Credentials

Only a single service token (NEMO_TOKEN) is required, which aligns with the API calls described. There are no unrelated SECRET/TOKEN requirements. Note: the skill's YAML frontmatter includes a configPaths entry (~/.config/nemovideo/) although the registry metadata listed none — this is an inconsistency but not a secret-exfiltration indicator by itself.

Persistence & Privilege

Skill is not always-enabled and does not request elevated or persistent platform privileges. It does instruct saving session_id and using tokens for API calls, which is normal for a session-based cloud integration.

Assessment

This skill appears to do what it says: it will call mega-api-prod.nemovideo.ai to create sessions, stream SSE responses, and upload files. Before installing or using it: 1) Only provide a NEMO_TOKEN if it is a token you trust to give this skill access to your account; treat NEMO_TOKEN like a password. 2) The skill will upload media you give it to the service — don't upload sensitive/private files unless you trust the service's privacy policy. 3) The skill can generate an anonymous token for you via the service (100 credits, 7-day expiry) if no token is present; be aware of where that token is stored and used. 4) There is a small inconsistency: the skill's frontmatter references a config path (~/.config/nemovideo/) and asks the agent to detect install paths for attribution headers — this is mostly for analytics/attribution but you should confirm you’re comfortable with the skill reading those local paths. If you need more assurance, ask the publisher for a canonical homepage or documentation and confirm the mega-api-prod.nemovideo.ai domain and token lifecycle policies.

Getting Started

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

Try saying:

• "generate my text prompts"
• "export 1080p MP4"
• "generate a 30-second video of a"

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.

Generator Skill — Create Videos From Text Prompts

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

Here's a typical use: you send a a short text description of a product launch scene, ask for generate a 30-second video of a sunset beach scene with upbeat background music, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter, specific prompts tend to produce more accurate results than vague long ones.

Matching Input to Actions

User prompts referencing generator skill, 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: generator-skill
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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.

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

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)

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 30-second video of a sunset beach scene with upbeat background music" → Download MP4. Takes 1-2 minutes 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 30-second video of a sunset beach scene with upbeat background music" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, WebM, GIF for the smoothest experience.

Export as MP4 for widest compatibility.