← Back to Skills Marketplace
Video Letter
by
vynbosserman65
· GitHub ↗
· v1.0.0
· MIT-0
81
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install video-letter
Description
Skip the learning curve of professional editing software. Describe what you want — turn my footage into a heartfelt video letter with text overlays and music...
Usage Guidance
This skill appears to do what it says (cloud video editing) and only needs a single API token, but there are a few things to confirm before installing or enabling it: 1) Ask the publisher to clarify the mismatch between registry metadata (no config paths) and the SKILL.md frontmatter (~/.config/nemovideo/) — confirm whether the skill will read or write local files and why. 2) Confirm where generated anonymous NEMO_TOKEN and session_id values are stored, who can read them, and how long they persist; avoid installing unless storage and retention are acceptable. 3) Because the skill will upload your video files to mega-api-prod.nemovideo.ai, verify the privacy/retention policy for uploaded media. 4) The SKILL.md asks not to display raw tokens — that's reasonable for secrecy, but makes it important you know where tokens are stored and can be revoked. 5) If you do not trust nemovideo.ai or cannot get answers to the above, do not enable the skill; otherwise proceed with caution and monitor for unexpected file access (install-path probing) or network requests outside the documented API domain.
Capability Analysis
Type: OpenClaw Skill
Name: video-letter
Version: 1.0.0
The video-letter skill is a functional wrapper for an AI video editing service (nemovideo.ai). It manages authentication via environment variables or anonymous token generation and handles video processing through standard REST and SSE API calls. The instructions in SKILL.md are aligned with the stated purpose of creating video messages, and there is no evidence of data exfiltration, unauthorized file access, or malicious command execution.
Capability Assessment
Purpose & Capability
The skill is a cloud-based video-editing front end and requests a single credential NEMO_TOKEN which aligns with calling a nemo video API. However, the SKILL.md frontmatter includes a config path (~/.config/nemovideo/) while the registry metadata listed no required config paths — this mismatch should be clarified (does the skill need local config access?). Overall the requested credential and endpoints are coherent with the stated purpose.
Instruction Scope
Instructions direct the agent to obtain an anonymous token automatically if NEMO_TOKEN is absent, create and persist a session_id, and call a set of backend endpoints for upload/rendering. The SKILL.md also requires generating attribution headers and 'auto-detecting' the install platform from the install path, which implies the agent may need to inspect installation paths or environment metadata. The skill also instructs not to display raw API responses or token values to the user — this is unusual (it hides token values) and should be documented where the token/session are stored and who can access them. All network calls are limited to the nemovideo API domain; there are no other external endpoints in the instructions.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest risk from installation. Nothing is being downloaded or written by an installer step described in the registry.
Credentials
Only a single credential (NEMO_TOKEN) is required which is proportional to a backend API-driven renderer. The frontmatter mention of a config path (~/.config/nemovideo/) is not declared in the registry requirements and should be clarified (why and how is that path used?). The skill's ability to generate an anonymous token itself reduces the need for pre-provisioned credentials, but you should confirm where that token and session data are stored and for how long.
Persistence & Privilege
always=false and autonomous invocation is the platform default. The skill does request creation/storage of a session_id and use of a token, but it does not ask for system-wide or other-skills' configuration changes. No elevated persistent privilege is requested in the registry.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install video-letter - After installation, invoke the skill by name or use
/video-letter - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Video Letter 1.0.0 — Initial Release
- Instantly create heartfelt video letters from your clips with AI — no editing required.
- Supports uploads of MP4, MOV, AVI, WebM files up to 500MB.
- Automated cloud processing adds text overlays, music, and exports 1080p MP4 in 1–2 minutes.
- Simple workflows: upload, describe your intent, and download your personalized video message.
- Built-in session management and free credits on first use; requires no local installation.
Metadata
Frequently Asked Questions
What is Video Letter?
Skip the learning curve of professional editing software. Describe what you want — turn my footage into a heartfelt video letter with text overlays and music... It is an AI Agent Skill for Claude Code / OpenClaw, with 81 downloads so far.
How do I install Video Letter?
Run "/install video-letter" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Video Letter free?
Yes, Video Letter is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Video Letter support?
Video Letter is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Video Letter?
It is built and maintained by vynbosserman65 (@vynbosserman65); the current version is v1.0.0.
More Skills