Professional Generator Free

Skip the learning curve of professional editing software. Describe what you want — turn my raw footage into a professional-looking video with titles and tran...

Security Scan

The skill's declared purpose (cloud video editing) matches most of its runtime instructions, but there are small metadata inconsistencies and privacy-surprising behaviors (automatic anonymous token creation and third-party uploads) you should review before installing.

Purpose & Capability

The name and description (cloud AI video generation) align with the actions in SKILL.md (uploading video files, creating sessions, rendering, exporting). Requesting a single API token (NEMO_TOKEN) is proportional. Minor inconsistency: the registry reported no required config paths, but the skill's frontmatter lists a config directory (~/.config/nemovideo/). This mismatch should be clarified.

Instruction Scope

The SKILL.md instructs the agent to upload user-provided media to a third-party backend (mega-api-prod.nemovideo.ai), create sessions, stream SSE events, and poll/render outputs. It also instructs automatic anonymous token creation (POST to /api/auth/anonymous-token) if NEMO_TOKEN is absent. These are coherent with the stated function, but they mean user files (possibly sensitive) will be transmitted to an external service and the agent will perform network operations without an explicit user-provided credential — a privacy/consent risk to surface to users.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest installation risk. Nothing is written to disk by a package installer here (though the service may expect a local config path).

Credentials

Only one env var is declared (NEMO_TOKEN) which is proportionate. However, the skill will create an anonymous token automatically if NEMO_TOKEN is missing; that network call and returned token act as credentials with 7‑day expiry. The frontmatter also references a config path (~/.config/nemovideo/) which wasn't listed in the registry requirements — unclear whether the agent will read or write that path.

Persistence & Privilege

The skill is not always-enabled and does not request elevated system privileges. It can be invoked autonomously (normal default). No install-time persistence or modification of other skills is described.

What to consider before installing

This skill appears to do what it says (cloud-based AI video editing) but you should: 1) Confirm you trust the backend domain (mega-api-prod.nemovideo.ai) and review its privacy/security policy before uploading any sensitive footage. 2) Decide whether you want the agent to call the anonymous-token endpoint automatically (it creates a temporary token if NEMO_TOKEN isn't provided) — if not, supply your own NEMO_TOKEN or avoid installing. 3) Ask the publisher to resolve the metadata mismatch (the SKILL.md references a config path ~/.config/nemovideo/ but the registry shows none). 4) Prefer skills with a known source/homepage or documented operator; lack of a publisher site reduces traceability. If you proceed, avoid uploading personally identifiable or confidential content until you validate the service's terms and security.

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"
• "turn my raw footage into 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.

Professional Video Generator Free — Generate and Export Professional Videos

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 or phone clip and want to turn my raw footage into a professional-looking video with titles and transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster and give cleaner results.

Matching Input to Actions

User prompts referencing professional generator free, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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	professional-generator-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

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.

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

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)

Common Workflows

Quick edit: Upload → "turn my raw footage into a professional-looking video with titles and transitions" → 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 "turn my raw footage into a professional-looking video with titles and transitions" — 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 across platforms and devices.