Alarm Clock Video

Skip the learning curve of professional editing software. Describe what you want — create a short alarm clock promo video with wake-up sound effects and text...

Security Scan

The skill's requirements and run instructions mostly match an AI video-rendering service: it needs a NEMO_TOKEN (or will obtain an anonymous token) and calls a nemo video backend to upload media and render—no unrelated credentials or installers are requested, but it will upload your files to an external service and there is a small metadata inconsistency to note.

Purpose & Capability

The name/description (AI video creation, uploads, exports) align with the declared primary credential (NEMO_TOKEN) and the SKILL.md which documents endpoints for uploading, session creation, SSE, and exporting. None of the required fields appear unrelated to video rendering.

Instruction Scope

The SKILL.md instructs the agent to: check for NEMO_TOKEN (or generate an anonymous token via the nemovideo API), create sessions, upload user media (multipart or URL), use SSE for edits, poll for render completion, and return download URLs. These are within the service's scope. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier indicated no required config paths — this inconsistency suggests the skill may expect to find or persist local configuration even though the manifest doesn't declare it.

Install Mechanism

Instruction-only skill with no install step and no code files. Nothing is written to disk by an installer; the agent will only perform network requests at runtime per instructions.

Credentials

Only one credential is declared (NEMO_TOKEN) and it is the primary credential for the described cloud API. The SKILL.md also provides a fallback anonymous-token flow when the env var is absent—this is coherent with the described purpose and not disproportionate.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide privileges. Autonomous invocation is allowed by default (normal). There is no install-time behavior or instructions to modify other skills or global agent settings.

Assessment

This skill will upload any media you send to a third-party service at mega-api-prod.nemovideo.ai and may generate/retain an anonymous token if you don't provide NEMO_TOKEN. Before installing or invoking: (1) confirm you trust that domain and its privacy/retention policy; (2) avoid sending sensitive files or credentials; (3) be aware that rendering consumes credits (the doc mentions 100 free credits for anon tokens); and (4) note the manifest inconsistency about a config path (~/.config/nemovideo/) — if you want assurance it won't read or write local config, ask the author to clarify or remove that requirement. If uncertain, test with non-sensitive sample media first.

Getting Started

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

Try saying:

• "create my video clips or images"
• "export 1080p MP4"
• "create a short alarm clock promo"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Alarm Clock Video — Create and Export Alarm Clock Videos

Drop your video clips or images in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 30-second morning routine clip or alarm clock product photo, ask for create a short alarm clock promo video with wake-up sound effects and text overlays, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — adding a short audio cue like an alarm sound in the first second boosts viewer retention.

Matching Input to Actions

User prompts referencing alarm clock video, 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	alarm-clock-video
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 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 Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Common Workflows

Quick edit: Upload → "create a short alarm clock promo video with wake-up sound effects and text overlays" → Download MP4. Takes 30-60 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 "create a short alarm clock promo video with wake-up sound effects and text overlays" — 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 social and e-commerce platforms.