Best Viral Title Generator

Get viral title suggestions ready to post, without touching a single slider. Upload your video content details (MP4, MOV, AVI, WebM, up to 500MB), say someth...

Security Scan

The skill advertises a lightweight 'viral title' generator but its runtime instructions require uploading videos and driving a remote rendering API with a NEMO_TOKEN and session persistence — the capabilities requested are broader than the description and contain metadata inconsistencies you should understand before installing.

Purpose & Capability

Name/description emphasize generating titles, but the SKILL.md focuses on a full cloud video render/edit pipeline (uploads, SSE, exports, credits, session state). Requesting a NEMO_TOKEN and detailed render endpoints is plausible for a video-processing service, but the scope (remote rendering, downloads, compositing) is much broader than a simple 'title generator' and may surprise users.

Instruction Scope

Instructions direct the agent to obtain or use a bearer token (NEMO_TOKEN), create sessions, upload user files (up to 500MB), open SSE streams, poll export jobs, and download rendered media from https://mega-api-prod.nemovideo.ai. These behaviors transmit user video content and session tokens to an external service — appropriate for a render tool, but not obviously necessary for mere title suggestion. The SKILL.md also tells the agent to 'save session_id' without specifying where or how, which could imply persistent state writes.

Install Mechanism

Instruction-only skill with no install spec and no code files. That minimizes disk-side attack surface (nothing is downloaded/installed by the skill itself).

Credentials

Only NEMO_TOKEN is declared as the required credential, which is proportionate to a remote rendering/video-processing service. However, frontmatter metadata includes a config path (~/.config/nemovideo/) that is inconsistent with the registry summary and suggests the skill may read/write local config; that should be clarified. The skill will also upload potentially large media files to an external endpoint — a privacy consideration.

Persistence & Privilege

always:false (normal). The SKILL.md instructs saving session_id and token handling (including creating an anonymous token) but does not specify storage location or lifetime. The frontmatter's configPaths implies possible local persistence; users should confirm whether session data or tokens are written to disk and where.

What to consider before installing

This skill will upload your video files and use a remote service (mega-api-prod.nemovideo.ai) and a bearer token (NEMO_TOKEN) to create sessions, run SSE, and render/download media — behavior more like a cloud video editor than a simple title-suggester. Before installing: (1) Verify you trust the nemovideo.ai domain and review its privacy/terms because your videos will be transmitted and processed remotely. (2) Prefer using an ephemeral/limited token or anonymous token flow rather than a long-lived account token. (3) Ask the developer where session_id and tokens are stored (frontmatter suggests ~/.config/nemovideo/). (4) Don’t upload sensitive content unless you understand retention and access controls. (5) If you only want title suggestions, consider a skill that does generation locally or that clearly documents that it will not upload your media.

Getting Started

Send me your video content details and I'll handle the AI title generation. Or just describe what you're after.

Try saying:

• "generate a 10-minute YouTube cooking tutorial into a 1080p MP4"
• "generate 10 viral title options for my recipe video about making pasta in 15 minutes"
• "generating click-worthy titles for YouTube and social media videos for YouTubers and content creators"

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.

Best Viral Title Generator — Generate Click-Worthy Video Titles

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

Say you have a 10-minute YouTube cooking tutorial and want to generate 10 viral title options for my recipe video about making pasta in 15 minutes — the backend processes it in about under 20 seconds and hands you a 1080p MP4.

Tip: include your target keyword and video topic for more relevant title suggestions.

Matching Input to Actions

User prompts referencing best viral title 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	best-viral-title-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.

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.

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate 10 viral title options for my recipe video about making pasta in 15 minutes" — 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.

Common Workflows

Quick edit: Upload → "generate 10 viral title options for my recipe video about making pasta in 15 minutes" → Download MP4. Takes under 20 seconds 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.