Ai Viral Title Generator

Skip the learning curve of professional editing software. Describe what you want — generate 10 viral title options for my cooking video that will get more cl...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-processing / title-generation service and its single required credential (NEMO_TOKEN) — nothing in the bundle demands unrelated credentials or unusual installs.

Purpose & Capability

Name/description (generate viral titles from uploaded videos) matches the instructions: the SKILL.md describes uploading video, creating a session, sending SSE messages for generation, and returning titles or exported video URLs. Required env var (NEMO_TOKEN) and the declared config path (~/.config/nemovideo/) are reasonable for a cloud video-processing integration.

Instruction Scope

Instructions perform network calls to the nemovideo API (auth, session, upload, render, status, credits) and instruct the agent to accept and forward user-uploaded video files. They also describe generating an anonymous token when NEMO_TOKEN is absent. The only slightly unexpected action is detecting an install path to set X-Skill-Platform (requires probing local paths), which is attribution-only and not essential to core title-generation — minor scope creep but explained in the file.

Install Mechanism

No install spec and no code files — instruction-only skill. This is the lowest-risk install model because nothing is written or downloaded by the skill itself.

Credentials

The skill declares a single required environment variable (NEMO_TOKEN) and a config path. That aligns with the API bearer-token model described. The SKILL.md also documents a safe fallback (anonymous-token) rather than requiring other unrelated secrets. No unrelated credentials, passwords, or cloud provider keys are requested.

Persistence & Privilege

always is false and the skill does not request elevated platform privileges. It does ask to save session_id and reuse tokens for its own API sessions (normal for a service integration). Autonomous invocation is allowed but that is the default for skills and not a problem here.

Assessment

This skill is internally consistent with a cloud video-processing/title-generation service, but you should still exercise normal caution: 1) The skill will upload your video content to https://mega-api-prod.nemovideo.ai — do not upload private or sensitive footage unless you trust that domain and its privacy policy. 2) If you already have a NEMO_TOKEN, prefer using a limited-scope token; otherwise the skill will obtain an anonymous 7-day token for you. 3) The SKILL.md references reading the install path and a config directory (~/.config/nemovideo/) for attribution/session use — ensure those files do not contain other secrets you care about. 4) The package has no homepage and an unknown source owner; if you need higher assurance, ask the publisher for a homepage, documentation, or a privacy policy before using it with sensitive data.

Getting Started

Share your video content and I'll get started on AI title generation. Or just tell me what you're thinking.

Try saying:

• "generate my video content"
• "export 1080p MP4"
• "generate 10 viral title options for"

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.

AI Viral Title Generator — Generate Click-Worthy Video Titles

Drop your video content in the chat and tell me what you need. I'll handle the AI title generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 10-minute YouTube tutorial video, ask for generate 10 viral title options for my cooking video that will get more clicks, and about under 20 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — uploading the first 60 seconds of your video gives the AI enough context to generate more accurate titles.

Matching Input to Actions

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

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 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

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.

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 → "generate 10 viral title options for my cooking video that will get more clicks" → 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.

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 cooking video that will get more clicks" — 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.