← Back to Skills Marketplace
vcarolxhberger

Video Motion

by vcarolxhberger · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
65
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install video-motion
Description
Skip the learning curve of professional editing software. Describe what you want — add smooth motion blur and dynamic camera movement to my static footage —...
Usage Guidance
What to consider before installing: - This skill will upload user video files to an external service at mega-api-prod.nemovideo.ai and use an API token (NEMO_TOKEN) or an anonymous token it can obtain for you — only install if you trust that service with the videos you plan to upload. - Metadata mismatches: the registry marks NEMO_TOKEN as required but SKILL.md describes an anonymous-token fallback, and the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry said none. Ask the publisher to clarify whether NEMO_TOKEN is mandatory and whether the skill will read/write ~/.config/nemovideo/. - Privacy: confirm retention/processing policies on the service (where files are stored, how long, whether outputs are shared). Avoid uploading sensitive or private footage until you have those answers. - Operational: the skill requires adding specific headers and will store session_id and use bearer tokens for requests; ensure the agent implementation will not log or expose raw tokens. - If you still want to proceed, prefer using an isolated, revokable token (or the anonymous flow) and test with non-sensitive sample clips first. If the publisher cannot clarify the config-path and credential behavior, treat the metadata mismatch as a red flag and refrain from installing.
Capability Analysis
Type: OpenClaw Skill Name: video-motion Version: 1.0.0 The video-motion skill is a functional wrapper for a video processing service hosted at mega-api-prod.nemovideo.ai. It defines standard API interactions for session management, file uploads, and cloud rendering. The instructions in SKILL.md are well-structured for an AI agent, including error handling and privacy measures (e.g., instructing the agent not to print tokens). No evidence of data exfiltration, malicious execution, or harmful prompt injection was found.
Capability Assessment
Purpose & Capability
The skill's declared purpose (AI motion enhancement of uploaded videos) matches the runtime instructions (upload endpoints, render/export workflow). However the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths, and the registry lists NEMO_TOKEN as required even though the instructions include an anonymous-token fallback. These mismatches reduce confidence that metadata accurately reflects runtime needs.
Instruction Scope
The SKILL.md instructs only actions related to the video-processing service: creating/using a session, uploading files, SSE chat, polling export status, and returning download URLs. It does not instruct reading unrelated system files or secrets. It does require including specific attribution headers on every request and instructs not to print tokens or raw JSON.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing will be written to disk by an installer. That minimizes supply-chain/install risk.
Credentials
The registry declares a single credential (NEMO_TOKEN) which is appropriate for an external API. But SKILL.md provides a complete anonymous-token acquisition flow, implying NEMO_TOKEN is optional. Also the frontmatter's config path (~/.config/nemovideo/) suggests the skill may read or write a local config directory despite the registry saying no config paths are required. These inconsistencies mean the declared environment/credential requirements are not fully trustworthy without clarification.
Persistence & Privilege
The skill does ask to 'save session_id' for job tracking and carries session tokens in requests, which is normal for a cloud-render tool. It does not request 'always: true' or other elevated privileges. The mention of a config path suggests the skill might persist credentials or session info to ~/.config/nemovideo/ — confirm whether it will create/read files and whether that's limited to its own directory.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install video-motion
  3. After installation, invoke the skill by name or use /video-motion
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Video Motion — Add Motion Effects to Videos v1.0.0 - Initial release providing AI-powered motion enhancement for video clips. - Supports uploading MP4, MOV, AVI, and WebM files up to 500MB. - Automated setup includes free anonymous access with 100 credits for 7 days. - Cloud-based editing: add smooth motion blur and dynamic camera movement without complex software. - Exports 1080p MP4 videos in 30–90 seconds per clip. - Includes simple commands for upload, status, credits, and export workflows.
Metadata
Slug video-motion
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Video Motion?

Skip the learning curve of professional editing software. Describe what you want — add smooth motion blur and dynamic camera movement to my static footage —... It is an AI Agent Skill for Claude Code / OpenClaw, with 65 downloads so far.

How do I install Video Motion?

Run "/install video-motion" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Video Motion free?

Yes, Video Motion is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Video Motion support?

Video Motion is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Video Motion?

It is built and maintained by vcarolxhberger (@vcarolxhberger); the current version is v1.0.0.

💬 Comments