Title Generator

generate video content into video title suggestions with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. YouTubers use it for generating catchy...

Security Scan

The skill mostly matches its stated purpose (cloud title generation + video processing) but includes surprising behaviors around automatic token provisioning, opaque handling of API responses/tokens, and mandatory uploads of user videos to a third‑party endpoint — these raise privacy and transparency concerns.

Purpose & Capability

The name/description claim title generation for videos; the instructions actually perform full cloud uploads, session management, and video rendering/exports (MP4 outputs). Requiring a single service credential (NEMO_TOKEN) and contacting nemo video APIs is coherent with cloud processing, but the skill is broader than a simple 'title generator' (it also queues renders and returns video files).

Instruction Scope

Runtime instructions instruct the agent to: auto-generate anonymous tokens by POSTing to an external API if NEMO_TOKEN is absent, upload user video files to the remote domain, create/persist sessions, and include attribution headers on every request. The SKILL.md also advises not to display raw API responses or token values to users, which reduces transparency. These actions involve transmitting user data off-device and creating credentials without explicit, prominent user consent.

Install Mechanism

No install spec and no code files — instruction-only. This reduces disk-write risk and matches the packaging, but network activity still occurs at runtime per the instructions.

Credentials

The skill requests a single primary credential (NEMO_TOKEN) and indicates a config path (~/.config/nemovideo/). That is proportionate to a cloud-processing service. However, the skill will attempt to auto-obtain an anonymous token if none is present, blurring the meaning of 'required env var' and potentially creating persisted tokens/config without explicit user action.

Persistence & Privilege

always:false and normal autonomous invocation settings. The skill instructs storing a session_id for requests, which is reasonable. There is no indication it tries to modify other skills or global agent settings.

What to consider before installing

This skill uploads user videos to a third-party domain (mega-api-prod.nemovideo.ai) and will auto-create anonymous tokens if you don't provide NEMO_TOKEN. Before installing or using it: 1) Do not upload sensitive or private video content unless you trust the service. 2) Consider setting NEMO_TOKEN yourself (instead of letting the skill auto-generate/store credentials) so you control token lifetime/storage. 3) Ask for clarification from the publisher about where tokens/sessions are persisted (does it write to ~/.config/nemovideo/?) and what the service's privacy/retention policy is. 4) Be cautious that the SKILL.md instructs hiding raw API responses/tokens from users — lack of transparency is a red flag. If you accept these tradeoffs and trust the backend, the skill's behavior is coherent; otherwise treat it as risky and avoid uploading sensitive media.

Getting Started

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

Try saying:

• "generate a 3-minute YouTube tutorial video into a 1080p MP4"
• "generate 10 title ideas for my cooking tutorial video"
• "generating catchy titles for YouTube and social media videos for YouTubers"

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.

Title Generator — Generate Titles for Your Videos

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 3-minute YouTube tutorial video, ask for generate 10 title ideas for my cooking tutorial video, 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 for accurate titles.

Matching Input to Actions

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

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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: title-generator
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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.

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 "generate 10 title ideas for my cooking tutorial video" — 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 title ideas for my cooking tutorial video" → 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.