Best Paid Content Generator

generate text prompts or footage into polished content videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and markete...

Security Scan

The skill's declared purpose (cloud video generation) mostly matches its runtime instructions (uploading footage and calling a remo te rendering API), but there are metadata inconsistencies, an unknown source, and unclear handling of tokens/where they are stored — so proceed with caution.

Purpose & Capability

The skill claims to generate monetizable videos from prompts/footage and its instructions call a video-processing backend (upload, session, render endpoints). Requesting a NEMO_TOKEN is appropriate for that purpose. However there is an inconsistency between the registry metadata (no required config paths) and the SKILL.md frontmatter (metadata.claims configPaths: ~/.config/nemovideo/). The skill also asks for attribution headers that must match the frontmatter, coupling runtime behavior to the packaged metadata.

Instruction Scope

SKILL.md instructs the agent to look for NEMO_TOKEN, and if missing POST to the external anonymous-token endpoint to obtain a token using a generated UUID, then create sessions and upload user files (videos/audio) to mega-api-prod.nemovideo.ai. Those actions are consistent with the described functionality (cloud render pipeline). Points to watch: it will transmit user files and metadata to an external service; the doc does not clearly state whether the obtained token is persisted to disk, nor whether personal/identifiable data is retained by the service. The frontmatter reference to a local config path (~/.config/nemovideo/) suggests possible file I/O that is not described in the registry requirements — an inconsistency.

Install Mechanism

Instruction-only skill with no install spec or code files; nothing will be downloaded or written by an installer. This minimizes installation-time risk.

Credentials

The skill declares a single required env var (NEMO_TOKEN), which is proportional for a third-party API. However: (1) SKILL.md defines a flow to obtain an anonymous NEMO_TOKEN via the public endpoint when none is present, which will create a short-lived credential tied to a generated client id — the spec does not state whether the token will be stored persistently or where; (2) frontmatter metadata references a config path (~/.config/nemovideo/) that the registry metadata did not list as required, implying the skill may access a local config directory. Both points raise questions about where credentials are read/written and how long-lived they are.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It does not include an install script or appear to modify other skills. Autonomous invocation is allowed (platform default) but is not combined here with other major red flags.

What to consider before installing

This skill appears to do what it says (upload footage and call a cloud render API), but it will send your files and generate/consume API tokens on a third-party domain (mega-api-prod.nemovideo.ai). Consider: (1) Only upload footage you are comfortable having processed/stored by an external service; avoid sensitive or private content. (2) The skill will try to read NEMO_TOKEN from your environment; if missing it will obtain an anonymous token by POSTing to the service using a generated client id — ask the maintainer how/if that token is persisted and for how long. (3) The skill metadata references a local config path (~/.config/nemovideo/) even though registry metadata did not require it — confirm whether the skill will read or write files in that directory. (4) The skill source and homepage are unknown; prefer skills with an identifiable maintainer or a published privacy/security policy for handling uploaded media and tokens. If you proceed, avoid supplying a long-lived production token unless you trust the service and understand retention/usage policies; use the anonymous flow or a scoped/test token first.

Getting Started

Send me your text prompts or footage and I'll handle the AI content video creation. Or just describe what you're after.

Try saying:

• "generate a 200-word product description or a 30-second raw clip into a 1080p MP4"
• "turn this product description into a 60-second promotional video with voiceover and captions"
• "generating professional promotional or monetizable videos from text or raw footage for content creators and 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.

Best Paid Content Generator — Generate and Export Monetizable Videos

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

Say you have a 200-word product description or a 30-second raw clip and want to turn this product description into a 60-second promotional video with voiceover and captions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 150 words produce tighter, more monetizable videos.

Matching Input to Actions

User prompts referencing best paid content 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.

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	best-paid-content-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.

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this product description into a 60-second promotional video with voiceover and captions" — 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 YouTube, TikTok, and ad platforms.

Common Workflows

Quick edit: Upload → "turn this product description into a 60-second promotional video with voiceover and captions" → 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.