Best Video Letter Maker

Skip the learning curve of professional editing software. Describe what you want — turn my written message and photos into a heartfelt video letter with back...

Security Scan

The skill's requests and runtime instructions are consistent with a remote video-rendering client that uses a single service token (NEMO_TOKEN); nothing in the package indicates hidden or unrelated access, though there is a small metadata inconsistency to review and you should be cautious about uploading personal media to an external service.

Purpose & Capability

The skill claims to create server-side video letters and its instructions call a remote nemo video API and request a service token (NEMO_TOKEN). Requesting a token for the video backend is proportionate and expected for this purpose.

Instruction Scope

SKILL.md instructs the agent to create/use an anonymous token if none is present, create a session, upload media, drive edits via SSE or API calls, poll export status, and return download URLs. These actions are within the stated scope and do not ask the agent to read unrelated system files or other credentials. The instructions explicitly warn not to print tokens or raw JSON.

Install Mechanism

This is an instruction-only skill with no install spec or code files. That minimizes on-disk execution risk; network calls are required to the documented nemo API domain (mega-api-prod.nemovideo.ai).

Credentials

The only declared credential is NEMO_TOKEN, which is appropriate. However, the SKILL.md frontmatter embeds a configPaths entry (~/.config/nemovideo/) while the registry metadata shows no required config paths — this mismatch should be clarified. Access to a user config directory could be reasonable (to read/store tokens), but it is not justified or described clearly in the instructions.

Persistence & Privilege

The skill is not always-enabled and does not request elevated or persistent platform privileges. It instructs creating a session and saving session_id (normal for remote-service clients). Autonomous invocation is allowed by default but is expected for skills of this type.

Assessment

This skill appears to be what it claims: a client for a remote video-rendering service that needs a single service token (NEMO_TOKEN). Before installing or using it, consider: 1) Only provide a token you intend to give the nemovideo service — treat NEMO_TOKEN like an account credential. 2) If you don't want to expose your primary account, use the anonymous-token flow described in the SKILL.md to obtain a temporary token. 3) Ask the skill author (or inspect runtime behavior) to clarify the frontmatter configPaths (~/.config/nemovideo/) vs. registry metadata mismatch — confirm whether the agent will read or write files in your home config directory. 4) Review the service's privacy/retention policy before uploading personal photos/audio. 5) If you want extra caution, run the skill with a temporary or scoped token and avoid uploading sensitive media until you confirm behavior.

Getting Started

Share your text, photos, audio and I'll get started on AI video letter creation. Or just tell me what you're thinking.

Try saying:

• "create my text, photos, audio"
• "export 1080p MP4"
• "turn my written message and photos"

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.

Best Video Letter Maker — Create and Send Personal Video Letters

Send me your text, photos, audio and describe the result you want. The AI video letter creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a written message and three personal photos, type "turn my written message and photos into a heartfelt video letter with background music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: adding a voiceover recording makes the video letter feel more personal than text-to-speech alone.

Matching Input to Actions

User prompts referencing best video letter maker, 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	best-video-letter-maker
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)

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.

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

Common Workflows

Quick edit: Upload → "turn my written message and photos into a heartfelt video letter with 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn my written message and photos into a heartfelt video letter with 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, email, and social sharing.