← Back to Skills Marketplace
Video Merge
by
dsewell-583h0
· GitHub ↗
· v1.0.0
· MIT-0
109
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install video-merge
Description
Get merged MP4 video ready to post, without touching a single slider. Upload your multiple video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like...
Usage Guidance
This skill is coherent with a cloud video-merge service: it will upload your video files to https://mega-api-prod.nemovideo.ai and requires an API token (NEMO_TOKEN) or will obtain an anonymous token for you. Before installing or using it, consider: (1) Privacy: your videos will be sent to an external service — confirm you are comfortable sharing that content. (2) Verify the endpoint and owner: the skill source is 'unknown' and homepage is absent; if you need stronger assurance, ask the publisher for a home page or documentation and verify the domain. (3) Token handling: confirm whether anonymous tokens or provided NEMO_TOKENs are stored persistently or only used for the session. (4) Metadata mismatch: SKILL.md references a local config path (~/.config/nemovideo/) and install-path-derived headers — ask whether the agent will inspect your filesystem. If any of these leave you uncomfortable or unanswered, do not enable the skill until the publisher clarifies.
Capability Analysis
Type: OpenClaw Skill
Name: video-merge
Version: 1.0.0
The skill bundle provides a legitimate integration for a cloud-based video editing service (nemovideo.ai). It contains detailed instructions for an AI agent to manage sessions, upload media, and trigger rendering tasks via the 'mega-api-prod.nemovideo.ai' endpoint. While it requires an API token (NEMO_TOKEN) and accesses a specific configuration directory (~/.config/nemovideo/), these actions are strictly aligned with the stated purpose of video merging and processing. No evidence of data exfiltration, unauthorized execution, or malicious prompt injection was found.
Capability Assessment
Purpose & Capability
The skill is a cloud video-merge tool and asks only for NEMO_TOKEN (the service API token), which is proportional to its stated purpose. Minor mismatch: the public registry metadata listed no required config paths, but the SKILL.md YAML frontmatter includes a configPaths entry (~/.config/nemovideo/). This is a small inconsistency in metadata but could indicate the skill expects a local nemovideo config directory.
Instruction Scope
The SKILL.md directly instructs the agent to upload user video files and call nemovideo.ai endpoints (session, upload, export, SSE) — exactly what a cloud merge tool must do. It also instructs the agent to detect an install path to set an X-Skill-Platform header, which implies the agent may inspect filesystem paths; that is not clearly declared in the registry. Otherwise the instructions stay within the stated purpose and do not ask for unrelated files or secrets.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest-risk installation model. Nothing is downloaded or written to disk by an install step.
Credentials
Only NEMO_TOKEN is declared as required and is the primary credential, which fits a cloud API workflow. The skill also describes an anonymous-token fallback (POST to mega-api-prod.nemovideo.ai) and says to 'use it as NEMO_TOKEN' — it's unclear whether that token is stored persistently or only used in-memory during a session. The earlier-mentioned configPaths entry (present in SKILL.md but not in registry) raises a small question about whether local config files might be read.
Persistence & Privilege
always:false and default model invocation are normal. The skill does not request permanent platform-level privileges. The only persistence ambiguity is whether the acquired anonymous token might be written or bound to a user account — the docs mention registration links but do not instruct the skill to modify other skills or system-wide settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install video-merge - After installation, invoke the skill by name or use
/video-merge - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
video-merge 1.0.0 — Initial Release
- Seamlessly merge multiple video clips (MP4, MOV, AVI, WebM) into a single 1080p MP4 file with cloud-based AI rendering.
- Simple workflow: upload clips, describe merge preferences, and download the final video.
- Automatic session management with anonymous token creation and free starter credits.
- Built-in support for status checks, timeline previews, and credit balance inquiries.
- Clear error handling and guidance for file format, file size, and export permissions.
- Streamlined process—no complex editing required; ideal for content creators and marketers.
Metadata
Frequently Asked Questions
What is Video Merge?
Get merged MP4 video ready to post, without touching a single slider. Upload your multiple video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like... It is an AI Agent Skill for Claude Code / OpenClaw, with 109 downloads so far.
How do I install Video Merge?
Run "/install video-merge" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Video Merge free?
Yes, Video Merge is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Video Merge support?
Video Merge is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Video Merge?
It is built and maintained by dsewell-583h0 (@dsewell-583h0); the current version is v1.0.0.
More Skills