Viral Title Generator Free

generate video content details into viral title suggestions with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. YouTubers and content creators...

Security Scan

The skill's functionality (cloud video/title generation) mostly matches its requirements, but there are inconsistencies and privacy concerns — it will obtain/use tokens and upload user videos to an external API whose provenance is unclear and the SKILL.md asks the agent to hide token values and may reference a user config path that wasn't declared.

Purpose & Capability

The stated purpose (generate viral titles and render/export videos) aligns with calls to a video-processing backend and the single required credential NEMO_TOKEN. However: (1) the registry metadata shown earlier states no required config paths, while the SKILL.md frontmatter lists ~/.config/nemovideo/ (inconsistency), and (2) the skill's source and homepage are unknown, so the external endpoint (mega-api-prod.nemovideo.ai) cannot be validated from the registry data.

Instruction Scope

Runtime instructions tell the agent to automatically obtain an anonymous token, create sessions, upload user video files (up to 500MB), and keep token values hidden from users. Uploading user videos to a third-party API is expected for this service, but the instructions also instruct the agent not to show raw API responses or tokens (which reduces transparency) and reference storing session_id for subsequent requests without specifying where/how (in-memory vs disk). The SKILL.md frontmatter requires attribution headers and detection of install path, which implies the agent may inspect its environment/paths.

Install Mechanism

There is no install spec and no code files — this instruction-only skill does not install packages or write archives to disk by itself, which is low-risk from an install perspective.

Credentials

The skill declares a single required credential (NEMO_TOKEN), which is proportionate to a hosted video-processing service. Caveats: the SKILL.md instructs the agent to auto-generate and use an anonymous token if NEMO_TOKEN isn't provided (so the agent can operate without user-supplied credentials), and the frontmatter's configPaths (~/.config/nemovideo/) introduces potential access to user config files that wasn't reflected in the registry summary — this mismatch should be clarified.

Persistence & Privilege

always:false (normal). The skill may persist a session token/session_id for ongoing uploads/exports; the SKILL.md doesn't explicitly say whether those are stored only in memory or written to ~/.config/nemovideo/ (frontmatter suggests that path). Persisting tokens to disk or modifying user config would increase privilege and privacy impact — clarify where session data and tokens are stored and how long they are retained.

What to consider before installing

This skill appears to be what it claims (cloud title/video processing) but has ambiguous and potentially privacy-sensitive behaviors you should confirm before installing: 1) It uploads your video files to https://mega-api-prod.nemovideo.ai — only use it for content you are comfortable sending to a third party. 2) The SKILL.md will auto-create an anonymous token if you don't provide one; ask whether that token and any session_id are stored on disk (and where) and for how long jobs/files are retained on their servers. 3) The frontmatter mentions ~/.config/nemovideo/, but the registry listed no config paths — ask the maintainer to explain and to remove any unnecessary file-system access. 4) The instructions request the agent to hide raw API responses and token values from the user — request transparency or prefer to supply your own token. 5) Because the skill source/homepage is unknown, prefer not to use it with sensitive or private video content until you can verify the service's operator and privacy policy. If you decide to proceed, set a token you control (if possible), test with non-sensitive sample videos, and ask the publisher to reconcile the metadata/configPath inconsistency and explicitly document storage/retention and data-handling practices.

Getting Started

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

Try saying:

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

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Viral Title Generator Free — Generate Click-Worthy Video Titles

Drop your video content details 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 cooking tutorial about pasta, ask for generate 10 viral title options for my cooking video about homemade pasta, 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 — include your target keyword and video topic for more relevant title suggestions.

Matching Input to Actions

User prompts referencing viral title generator free, 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.

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

Header	Value
X-Skill-Source	viral-title-generator-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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)

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

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.

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 cooking video about homemade pasta" → 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 about homemade pasta" — 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.