Auto Generator Pro

generate raw footage into auto-generated videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for automatically...

Security Scan

The skill's declared purpose (cloud video generation) is plausible, but there are multiple internal inconsistencies and privacy risks (unknown backend, metadata mismatches) that warrant caution before installing or using it with sensitive footage.

Purpose & Capability

The skill claims to provide cloud video generation and all runtime instructions target a single external service (mega-api-prod.nemovideo.ai), so the requested NEMO_TOKEN credential is relevant. However, registry metadata lists NEMO_TOKEN as required while the SKILL.md also describes auto-generating an anonymous NEMO_TOKEN if none is present — that mismatch is inconsistent and unexplained. The SKILL.md frontmatter also mentions a config path (~/.config/nemovideo/) but the registry metadata said no config paths; another mismatch.

Instruction Scope

Instructions explicitly upload user media and send many API calls to the external domain (session creation, uploads, SSE, exports). That is coherent with the stated purpose, but you should note the skill will transmit your raw video/audio files to an external cloud service. The SKILL.md also instructs the agent to generate client UUIDs and fetch anonymous tokens from the backend — functionality that is reasonable for this service but not reflected in the registry's required-env declaration.

Install Mechanism

This is an instruction-only skill with no install spec or shipped code, so nothing is written to disk by an installer. That lowers code-execution risk. However, runtime behavior depends on network calls to a third-party domain with no listed homepage or owner contact, which increases operational/privacy risk even though install is harmless.

Credentials

Only one credential (NEMO_TOKEN) is declared, which fits a cloud API. But the SKILL.md describes creating an anonymous token if none exists, so marking NEMO_TOKEN as strictly required in registry metadata is inconsistent. No unrelated secrets are requested. Still, the skill will use that token to upload user media to a third party, so the sensitivity of that token and the uploaded data matters.

Persistence & Privilege

The skill does not request always:true and does not modify other skills or system-wide settings. It keeps a session_id for operations, which is normal for a session-based API. No elevated persistence privileges are requested.

What to consider before installing

This skill will upload your raw video/audio to an external service (mega-api-prod.nemovideo.ai). Before using it, verify the service owner and privacy policy (there is no homepage listed), and avoid uploading sensitive or private footage until you trust the backend. Note the registry metadata and SKILL.md conflict: the skill declares NEMO_TOKEN as required but will generate an anonymous token itself if none is present, and the SKILL.md mentions a config path not present in registry metadata. If you proceed, test with non-sensitive short clips, monitor network activity, and prefer using your own account/token only if you trust the provider. If you need higher assurance, ask the publisher for source code, a homepage/privacy policy, or more detail about data retention and access controls.

Getting Started

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

Try saying:

• "generate my raw footage"
• "export 1080p MP4"
• "automatically cut, arrange, and generate a"

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.

Auto Generator Pro — Generate Videos From Raw Footage

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

Say you have a 2-minute raw screen recording and want to automatically cut, arrange, and generate a finished video from my raw clips — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter input clips under 3 minutes give the AI more precise output control.

Matching Input to Actions

User prompts referencing auto generator pro, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is auto-generator-pro, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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

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)

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 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

Common Workflows

Quick edit: Upload → "automatically cut, arrange, and generate a finished video from my raw clips" → 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 "automatically cut, arrange, and generate a finished video from my raw clips" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.