Video Maker Happy Birthday

create photos or clips into birthday celebration video with this skill. Works with JPG, PNG, MP4, MOV files up to 200MB. friends and family celebrators use i...

Security Scan

The skill's requirements and runtime instructions align with a cloud-based birthday-video service (it needs a NEMO_TOKEN and describes session, upload, render, and download flows), but it will upload user media and obtain/use an external anonymous token—review privacy and trust of the remote endpoint before use.

Purpose & Capability

Name/description describe a cloud video creation service and the SKILL.md requests a single service token (NEMO_TOKEN) and details API calls to a remote render backend. Requiring a service token and upload/render endpoints is proportional to the stated purpose.

Instruction Scope

Instructions explicitly cover creating a session, uploading user photos/clips (via multipart or URL), sending SSE messages, polling render status, and returning download URLs. This is within expected scope for a cloud render skill, but it does instruct the agent to upload user media to an external server and to automatically request an anonymous token if none is present—both are privacy-relevant actions the user should be aware of.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk or pulled from third-party package sources. This is the lowest install risk.

Credentials

Only one environment credential (NEMO_TOKEN) is required, which is appropriate for a cloud API. The skill will auto-fetch an anonymous NEMO_TOKEN if none exists (100 free credits, 7-day expiry). Metadata declares a config path (~/.config/nemovideo/) which is reasonable for storing session/token data but should be confirmed by the user if they want tokens written to disk.

Persistence & Privilege

Skill is not always-enabled and does not request elevated system-wide privileges. It does not attempt to modify other skills or system settings in the instructions. Autonomous invocation is enabled (default) but not unusual for skills; nothing else indicates excessive persistence.

Assessment

This skill appears to be a coherent cloud-based birthday-video creator, but it will transmit whatever photos/videos you send to an external service (https://mega-api-prod.nemovideo.ai) and may automatically obtain an anonymous API token if none is set. Before installing/using it: 1) Decide whether you trust the remote service to handle your media (do not upload sensitive/private images if unsure). 2) Prefer setting your own NEMO_TOKEN (if you have one) rather than relying on the skill to obtain an anonymous token automatically. 3) Check whether the skill will write tokens or session info to ~/.config/nemovideo/ and whether you’re comfortable with that. 4) If the service/provider is unknown, look for a homepage or privacy policy (none is listed in the metadata)—lack of a trusted operator reduces confidence. If you want, I can help draft a short privacy prompt to show users before uploading media, or try to contact the vendor/domain for more provenance.

Getting Started

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

Try saying:

• "create my photos or clips"
• "export 1080p MP4"
• "create a happy birthday video with"

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.

Video Maker Happy Birthday — Create and Share Birthday Videos

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

A quick example: upload five birthday photos and a name, type "create a happy birthday video with music, my friend's name, and a slideshow of these photos", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: adding a name or short message makes the video feel more personal and takes no extra time.

Matching Input to Actions

User prompts referencing video maker happy birthday, 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 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.

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

Header	Value
X-Skill-Source	video-maker-happy-birthday
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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.

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 "create a happy birthday video with music, my friend's name, and a slideshow of these photos" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across WhatsApp, Instagram, and email.

Common Workflows

Quick edit: Upload → "create a happy birthday video with music, my friend's name, and a slideshow of these photos" → 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.