Free Video Hook Generator

Skip the learning curve of professional editing software. Describe what you want — generate 5 attention-grabbing opening hooks for my fitness tutorial video...

Security Scan

The skill's requirements and instructions are consistent with a cloud video hook/render service (it needs a single NEMO_TOKEN and uploads media to nemovideo.ai), though there are a few small inconsistencies and privacy considerations you should understand before using it.

Purpose & Capability

Name/description (generate hooks and short rendered clips) align with the runtime instructions (upload video, create/render session, export). Requested credential (NEMO_TOKEN) is appropriate for a third‑party cloud API. One minor incoherence: registry metadata listed no required config paths while the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/).

Instruction Scope

Instructions are detailed and focused on the rendering workflow (session creation, SSE chat, upload, export). They instruct the agent to obtain an anonymous token if NEMO_TOKEN is absent and to include specific attribution headers. They also instruct the agent to 'keep the technical details out of the chat' (i.e., hide backend actions from users), which is a design choice but reduces transparency. The frontmatter's configPaths suggests the skill may expect local config data, though SKILL.md does not explicitly direct reading local config files.

Install Mechanism

Instruction-only skill with no install spec and no code files — minimal disk footprint and no remote installs. This is the lowest-risk install model.

Credentials

Only one credential is requested (NEMO_TOKEN), which is proportional to a cloud render API. The skill will also mint an anonymous token if none is provided. Consider that providing a long‑lived NEMO_TOKEN gives the service access to upload/export actions; anonymous tokens are time/credit-limited per the instructions. No other unrelated secrets or credentials are requested.

Persistence & Privilege

always:false and no indication the skill modifies other skills or system settings. It creates short-lived sessions on the remote service but does not request persistent agent privileges.

Assessment

This skill appears to do what it says: upload your clip(s) to a nemovideo.ai backend, run AI-driven hook generation and cloud rendering, and return exported MP4s. Before installing or using it: (1) Be aware your video/audio files and any metadata you send will be transmitted to https://mega-api-prod.nemovideo.ai — do not upload sensitive content unless you trust that service and its terms/privacy policy. (2) Prefer using an anonymous/starter token rather than pasting a long‑lived NEMO_TOKEN; if you must provide a token, understand its scope and revoke it when not needed. (3) Ask the publisher to clarify the configPaths entry (~/.config/nemovideo/) and whether the skill will read local config files. (4) If you need more assurance, request the skill source or a verification URL for the backend domain and review its privacy/terms. Overall the skill is coherent with its purpose, but verify privacy and token handling before use.

Getting Started

Share your video script or topic and I'll get started on AI hook generation. Or just tell me what you're thinking.

Try saying:

• "generate my video script or topic"
• "export 1080p MP4"
• "generate 5 attention-grabbing opening hooks for"

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 Video Hook Generator — Generate Hooks for Videos

This tool takes your video script or topic and runs AI hook generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 60-second product demo video and want to generate 5 attention-grabbing opening hooks for my fitness tutorial video — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: shorter input clips under 60 seconds produce the most focused and punchy hook suggestions.

Matching Input to Actions

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

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

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

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.

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

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

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 5 attention-grabbing opening hooks for my fitness 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 across TikTok, Instagram, and YouTube.

Common Workflows

Quick edit: Upload → "generate 5 attention-grabbing opening hooks for my fitness tutorial video" → 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.