Video Hook Generator Free

Skip the learning curve of professional editing software. Describe what you want — generate a compelling opening hook for my video to stop viewers from scrol...

Security Scan

The skill's network calls and required API token align with a remote video-rendering service, but there are small inconsistencies (declared config path in the skill frontmatter vs registry metadata) and some behaviors you should verify before trusting it with video files or credentials.

Purpose & Capability

The name/description claim remote video hook generation and the SKILL.md directs traffic to a remote render API (mega-api-prod.nemovideo.ai) — that is coherent with the stated purpose. The required env var NEMO_TOKEN as primary credential is reasonable for an API-backed service. However, the SKILL.md frontmatter lists a configPaths entry (~/.config/nemovideo/) while the registry metadata reports no required config paths — this mismatch is unexplained and worth asking the publisher about.

Instruction Scope

Instructions are explicit about creating sessions, uploading video files, running SSE chat streams, polling render endpoints, and always including attribution headers. Those actions are within scope for a cloud video-editing service. The instructions do require reading NEMO_TOKEN from the environment and optionally generating an anonymous token via a network POST. They also ask agents to 'auto-detect' platform from install path (implies reading an install path), which is not clearly justified. No instructions request unrelated local files or secrets beyond NEMO_TOKEN, but the configPaths discrepancy suggests the skill may attempt to access a local config directory.

Install Mechanism

This is instruction-only with no install spec or code files, so it does not write to disk or download archives. That is the lowest-risk install model.

Credentials

Only one declared credential (NEMO_TOKEN) is requested, which fits an API client. But the frontmatter's configPaths implies access to ~/.config/nemovideo/, which would give the skill filesystem access to persistent tokens or other user data — this access is not justified in the prose. Also the skill requires including persistent attribution headers on every request; while not a secret, that is a tracking vector you should be aware of.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request forced installation or modification of other skills. Autonomous invocation is allowed (platform default) but not combined with broad credential access here.

What to consider before installing

This skill mostly does what it says (uploads clips to a remote renderer) but verify a few things before installing: 1) Confirm the publisher and the legitimacy of the backend domain (mega-api-prod.nemovideo.ai) and read its privacy/terms — your uploaded videos are sent there. 2) Ask why the skill frontmatter lists ~/.config/nemovideo/ (local config access) when the registry metadata shows no config paths; if the skill reads that directory it could access stored tokens or files. 3) Treat NEMO_TOKEN like any API secret — only supply a token with limited scope, or use an anonymous starter token if you don’t trust persistence. 4) Be cautious about uploading sensitive/private footage. 5) If you need higher assurance, ask the publisher for source or a documented privacy policy, or run uploads from an isolated environment.

Getting Started

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

Try saying:

• "generate a 2-minute product demo video into a 1080p MP4"
• "generate a compelling opening hook for my video to stop viewers from scrolling"
• "generating attention-grabbing opening hooks for social media videos for TikTok 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.

Video Hook Generator Free — Generate Hooks for Your Videos

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

A quick example: upload a 2-minute product demo video, type "generate a compelling opening hook for my video to stop viewers from scrolling", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: clips under 60 seconds produce the most focused and punchy hooks.

Matching Input to Actions

User prompts referencing video hook 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	video-hook-generator-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a compelling opening hook for my video to stop viewers from scrolling" — 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 a compelling opening hook for my video to stop viewers from scrolling" → Download MP4. Takes 20-40 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.