Clock Video Production

create images or footage into polished product videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. product marketers use it for producin...

Security Scan

The skill's declared purpose (cloud video rendering) matches most of its behavior, but it reaches out to an external API, contains metadata inconsistencies (config path present in SKILL.md but not in registry metadata), and will auto-provision tokens — review network endpoints, data handling, and the missing provenance before installing.

Purpose & Capability

The skill's name/description (cloud video creation/export) aligns with its runtime instructions (upload files, start render, download MP4). Requesting a single service token (NEMO_TOKEN) is proportional. However, SKILL.md's YAML frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata listed no required config paths — a mismatch worth checking.

Instruction Scope

The SKILL.md instructs the agent to automatically obtain an anonymous token and to call multiple external endpoints on mega-api-prod.nemovideo.ai (auth, upload, SSE, render). It also derives headers from local install paths and references a local config path (~/.config/nemovideo/), which implies the agent may read local paths to populate headers. The skill stores session_id for subsequent requests and instructs not to display raw tokens — these are expected for a remote service but increase the data/network footprint and deserve review. There is no explicit guidance about where session_id or tokens are stored (file vs memory).

Install Mechanism

Instruction-only skill with no install spec or code files; nothing is written to disk by an installer step. This minimizes on-device install risk.

Credentials

Only NEMO_TOKEN is declared as required, which is consistent with a remote rendering service. Still, SKILL.md will auto-generate an anonymous token by POSTing to an external endpoint if NEMO_TOKEN is not set, meaning the skill will create/use credentials on the user's behalf. The presence of a config path in the frontmatter suggests possible access to ~/.config/nemovideo/, which could contain unrelated sensitive configuration. Confirm whether that local config access is necessary.

Persistence & Privilege

The skill is not marked always:true and does not request permanent agent-wide privileges. It does instruct storing a session_id for the render session, but there is no instruction to persistently modify other skills or global agent settings.

What to consider before installing

What to consider before installing: - Provenance: The skill has no listed homepage or source and was published by an unknown owner. Confirm the service (nemovideo / mega-api-prod.nemovideo.ai) is legitimate and review its privacy and data-retention policies before uploading media. - Network activity: The skill instructs the agent to call external endpoints (auth, upload, SSE, render). If you run sensitive footage through it, assume those files are transmitted to that external service. - Auto-generated credentials: If NEMO_TOKEN is not provided, the skill will generate an anonymous token by contacting the service and use it. Consider providing a dedicated token/account rather than allowing anonymous provisioning, and verify what the token permits and how long it is valid. - Local file/config access: SKILL.md references ~/.config/nemovideo/ and derives headers from install paths (e.g., ~/.clawhub/). Ask the author whether the skill will read those paths and why; only allow access if necessary. - Lack of code to inspect: This skill is instruction-only, so there is no code to audit. If you need higher assurance, request the skill's source code, a service SLA, or a privacy statement from the publisher. - Practical steps: (1) Verify the external domain and service operator, (2) avoid uploading highly sensitive media until you confirm data handling, (3) use an isolated account/token or ephemeral token with limited scope, and (4) ask the publisher to reconcile the configPath metadata mismatch and to document where tokens/session IDs are stored.

Getting Started

Share your images or footage and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "create my images or footage"
• "export 1080p MP4"
• "create a 30-second product video showing"

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.

Clock Video Production — Create and Export Clock Product Videos

Send me your images or footage and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload five clock product photos and a logo file, type "create a 30-second product video showing the clock from multiple angles with smooth transitions", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: use high-contrast background images of the clock for sharper AI-generated transitions.

Matching Input to Actions

User prompts referencing clock video production, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is clock-video-production, 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).

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

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.

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

Common Workflows

Quick edit: Upload → "create a 30-second product video showing the clock from multiple angles with smooth transitions" → Download MP4. Takes 1-2 minutes 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 "create a 30-second product video showing the clock from multiple angles with smooth transitions" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across e-commerce and social platforms.