Free Viral Title Generator

Get viral title suggestions ready to post, without touching a single slider. Upload your video topic or keyword (MP4, MOV, AVI, WebM, up to 500MB), say somet...

Security Scan

The skill claims to be a 'title generator' but its runtime instructions perform full video upload/rendering to an external API and request an API token — the scope and data access go beyond what the name/description imply.

Purpose & Capability

The skill's name/description emphasize generating viral titles, but the SKILL.md documents a full cloud render pipeline (video uploads, track edits, SSE chat, render/export endpoints and 1080p MP4 downloads). Requiring media upload, render jobs, and session management is much broader than a simple 'title suggestion' tool and may surprise users.

Instruction Scope

Runtime instructions direct the agent to upload user video files (up to 500MB) and poll/render on a remote service at https://mega-api-prod.nemovideo.ai. The agent is told to create sessions, include Authorization headers, handle SSE streams and poll exports. This involves transmitting potentially sensitive user media and metadata to an external endpoint — behavior not obvious from the skill's name alone. The SKILL.md does not instruct reading unrelated local files, but it does suggest detecting install/config paths and sending attribution headers on every request.

Install Mechanism

This is instruction-only with no install spec and no code files, so nothing is written to disk by an installer here. That reduces the risk from arbitrary installs.

Credentials

Only a single API credential (NEMO_TOKEN) is declared — which is reasonable for calling an external API. The skill also provides a fallback to request an anonymous token from the service if no NEMO_TOKEN is present; that means the agent will perform network requests to obtain credentials on the fly. The metadata also references a config path (~/.config/nemovideo/) which may indicate the skill expects stored tokens or settings — users should verify why that path is needed.

Persistence & Privilege

The skill is not marked always:true and does not request elevated platform-wide privileges. It is user-invocable and allowed to run autonomously by default (normal for skills). It does not declare writing/modifying other skills or system-wide settings.

What to consider before installing

This skill will upload your video and related metadata to a third-party API (mega-api-prod.nemovideo.ai) and may create or use an API token (NEMO_TOKEN) for that service. Before installing or using it: 1) Treat it as a service that sends your files off-device — don't upload sensitive or private videos. 2) If asked, prefer using an anonymous starter token for testing rather than placing a permanent token in your environment. 3) The skill's name implies 'title suggestions' but the runtime behavior includes full cloud rendering and file transfers — verify you want that functionality. 4) There is no homepage or provenance info; consider testing with non-sensitive sample files and look up the service domain and privacy policy externally before trusting it with real content.

Getting Started

Ready when you are. Drop your video topic or keyword here or describe what you want to make.

Try saying:

• "generate a 10-minute cooking tutorial about pasta recipes into a 1080p MP4"
• "generate 10 viral title options for my YouTube video about budget meal prep"
• "generating click-worthy titles for YouTube and social media videos for YouTubers and content creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Free Viral Title Generator — Generate Click-Worthy Video Titles

Send me your video topic or keyword and describe the result you want. The AI title generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 10-minute cooking tutorial about pasta recipes, type "generate 10 viral title options for my YouTube video about budget meal prep", and you'll get a 1080p MP4 back in roughly under 10 seconds. All rendering happens server-side.

Worth noting: include your target audience and video topic for more relevant title suggestions.

Matching Input to Actions

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

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 free-viral-title-generator, 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)

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

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.

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

Common Workflows

Quick edit: Upload → "generate 10 viral title options for my YouTube video about budget meal prep" → Download MP4. Takes under 10 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.

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 YouTube video about budget meal prep" — 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.