Paid Content Generator Online

Get monetizable video content ready to post, without touching a single slider. Upload your text prompts, footage (MP4, MOV, AVI, WebM, up to 500MB), say some...

Security Scan

The skill's declared purpose (cloud-based monetizable video generation) aligns with its instructions and minimal requirements, but it will send your prompts and uploaded footage to an external API and has a small metadata inconsistency you should be aware of.

Purpose & Capability

The skill claims to generate monetizable videos and requires a single API credential (NEMO_TOKEN). All API endpoints, upload and export flows described in SKILL.md are consistent with that purpose.

Instruction Scope

The runtime instructions direct the agent to: check for NEMO_TOKEN, obtain an anonymous token if missing (via POST to /api/auth/anonymous-token), create a session, upload user-provided media, run SSE-based generation, and poll for/export results. These steps are within the expected scope, but they involve sending user prompts and media files (up to 500MB) to an external domain (mega-api-prod.nemovideo.ai). The skill also indicates it will derive an X-Skill-Platform header by detecting install paths (e.g., checking ~/.clawhub/ or ~/.cursor/skills/), which implies the agent may probe the user's home filesystem for those paths.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. Nothing will be written to disk by an installer as part of the skill package itself.

Credentials

The only required credential is NEMO_TOKEN (primaryEnv), which is proportional to a cloud API-backed video service. However, the SKILL.md frontmatter includes a configPaths value (~/.config/nemovideo/) that is not listed in the registry Requirements summary; this is an inconsistency to clarify. The instructions also create an anonymous token if NEMO_TOKEN is absent — expected behavior but worth noting since it causes runtime network auth and uses a generated client ID.

Persistence & Privilege

The skill does not request always:true and contains no install-time persistence. It asks to retain session_id in memory for the session which is normal. The skill does not declare writing to other skills' configs or system-wide settings.

Assessment

This skill will upload your text prompts and any media files you provide to an external service (mega-api-prod.nemovideo.ai). Before installing or invoking it: (1) Decide whether you are comfortable sending those files (no special encryption is described); avoid uploading sensitive personal or proprietary media. (2) If you have your own NEMO_TOKEN, provide it rather than relying on the anonymous-token flow to retain more control. (3) Verify the service/domain independently (there's no homepage listed) if provenance matters. (4) Ask the author to clarify the registry vs. SKILL.md discrepancy about ~/.config/nemovideo/ and whether the skill will read other filesystem locations. (5) Expect the agent to probe for install paths to set headers — this requires reading paths in your home directory but not arbitrary files. If any of these points are unacceptable, do not install/use the skill.

Getting Started

Ready when you are. Drop your text prompts, footage here or describe what you want to make.

Try saying:

• "generate a 60-second product demo clip with voiceover script into a 1080p MP4"
• "turn this product footage into a monetizable YouTube video with intro, transitions, and call-to-action"
• "generating ready-to-publish paid content videos for online platforms for content creators, 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.

Paid Content Generator Online — Generate and Export Monetizable Videos

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

Say you have a 60-second product demo clip with voiceover script and want to turn this product footage into a monetizable YouTube video with intro, transitions, and call-to-action — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: adding a clear call-to-action in your prompt improves conversion-focused output.

Matching Input to Actions

User prompts referencing paid content generator online, 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 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is paid-content-generator-online, 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).

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.

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

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

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.

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 this product footage into a monetizable YouTube video with intro, transitions, and call-to-action" → 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 this product footage into a monetizable YouTube video with intro, transitions, and call-to-action" — 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 monetization platforms like YouTube and Vimeo.