Video Letter Maker Free

create photos or clips into personal video letters with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. everyday users and gift senders use it f...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based video rendering service; it asks for a single API token and uses network calls to an external nemo video API to upload files and request renders.

Purpose & Capability

The name/description (video letter maker) aligns with the declared requirement for a NEMO_TOKEN and the SKILL.md instructions to call the nemovideo.ai API to create and export videos. One minor inconsistency: the registry metadata lists no required config paths while the SKILL.md frontmatter includes a config path (~/.config/nemovideo/). This mismatch should be clarified but does not by itself indicate malicious intent.

Instruction Scope

The SKILL.md instructs the agent to (a) obtain or use a NEMO_TOKEN, (b) create a session and perform SSE/text-stream interactions, and (c) upload user-provided files (multipart or URL) to mega-api-prod.nemovideo.ai. These actions are expected for a cloud render service. Note: the skill will upload any files the user supplies to a third-party API and may read local file paths provided for upload — only provide files you consent to transmit.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest-risk install mechanism. Nothing is downloaded or written by an install step.

Credentials

Only a single credential (NEMO_TOKEN) is required, which matches the described API usage. The SKILL.md also supports generating an ephemeral anonymous token via the service's anonymous-token endpoint when no env var is present; this is proportionate. The earlier-noted config path in frontmatter could be used to store session info — verify whether that behavior exists and whether it's documented.

Persistence & Privilege

The skill does not request permanent/global presence (always:false) and has no install-time persistence. Aside from the frontmatter-configPath hint, there is no instruction to modify other skills or system-wide configuration.

Assessment

This skill appears to do what it says: it will upload files you provide to an external nemo video API and use a token called NEMO_TOKEN to authenticate. Before installing or using it, confirm you trust mega-api-prod.nemovideo.ai and are willing to upload any photos, videos, or audio you send. If you already have a NEMO_TOKEN stored in your environment, the skill will use it (so avoid putting long-lived or high-privilege credentials there unless intended). If no token is present, the skill will request an anonymous short-lived token from the service. Also ask the publisher to confirm whether the skill will write session data under ~/.config/nemovideo/ (frontmatter mentions it) and review the service's privacy policy for retention/processing of uploaded media.

Getting Started

Send me your photos or clips and I'll handle the AI video letter creation. Or just describe what you're after.

Try saying:

• "create three personal photos and a short voice recording into a 1080p MP4"
• "create a heartfelt video letter with my photos, voice message, and background music"
• "creating personalized video messages to send to friends or family for everyday users and gift senders"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Letter Maker Free — Create and Send Personal Video Letters

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

Here's a typical use: you send a three personal photos and a short voice recording, ask for create a heartfelt video letter with my photos, voice message, and background music, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — adding a voiceover makes the video letter feel more personal than text alone.

Matching Input to Actions

User prompts referencing video letter maker 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.

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

Header	Value
X-Skill-Source	video-letter-maker-free
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.

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.

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.

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

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a heartfelt video letter with my photos, voice message, and background music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across phones and email sharing.

Common Workflows

Quick edit: Upload → "create a heartfelt video letter with my photos, voice message, and background music" → 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.