← Back to Skills Marketplace
Video Factory
by
francemichaell-15
· GitHub ↗
· v1.0.0
· MIT-0
44
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install video-factory
Description
create raw video clips into finished MP4 videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and marketers use it for...
Usage Guidance
This skill will upload any videos you give it to a third‑party service at mega-api-prod.nemovideo.ai and use a NEMO_TOKEN to authenticate. Before installing: 1) Confirm the service/domain is legitimate and acceptable for your content (privacy/legal). 2) Ask the skill author to clarify: why is NEMO_TOKEN labeled 'required' when an anonymous token flow exists, and why does the frontmatter reference ~/.config/nemovideo/ and 'auto-detect' of install path? 3) If you don't want to tie this to an account, avoid setting a persistent NEMO_TOKEN and rely on the anonymous flow, but know anonymous tokens still grant the service access to uploads. 4) Do not use with sensitive or confidential videos until you verify the provider's data retention/privacy policy. 5) If possible, test with non-sensitive sample media first and monitor network requests. If the author cannot explain the config-path / install-path reads or the required-env mismatch, treat the skill cautiously.
Capability Analysis
Type: OpenClaw Skill
Name: video-factory
Version: 1.0.0
The video-factory skill is a functional integration for a cloud-based video processing service (nemovideo.ai). It provides clear instructions for the agent to manage API authentication, session state, and video rendering workflows. While it performs network requests to external endpoints (mega-api-prod.nemovideo.ai) and handles user-provided files, these actions are strictly aligned with its stated purpose. The skill includes security-conscious instructions, such as advising the agent not to print raw tokens or JSON to the user.
Capability Assessment
Purpose & Capability
The skill's stated purpose (batch video processing via a cloud API) aligns with the endpoints and flows in SKILL.md. Requesting a NEMO_TOKEN credential is reasonable for that purpose. However, the frontmatter references a local config path (~/.config/nemovideo/) that the registry metadata did not list, and the SKILL.md both treats NEMO_TOKEN as 'required' and documents an anonymous-token flow — those are inconsistent and deserve explanation.
Instruction Scope
The instructions direct the agent to upload user-supplied video files to https://mega-api-prod.nemovideo.ai and to create/use session tokens — that is expected for a cloud render service but is a material privacy action (user files leave the machine). The SKILL.md also requires adding attribution headers where one header value is 'auto-detect: install path' (X-Skill-Platform), which implies the agent may need to inspect its installation path or environment; this is not documented elsewhere and could cause unexpected filesystem or environment reads. The doc explicitly says not to print tokens/raw JSON, which is good, but the scope of file/env access should be clarified.
Install Mechanism
Instruction-only skill with no install spec or code files — lowest install risk. Nothing will be downloaded or written to disk by an install step.
Credentials
The registry lists NEMO_TOKEN as a required environment variable / primary credential, which makes sense for a service token. But the SKILL.md also documents an anonymous-token flow (generate UUID → POST anonymous-token) if NEMO_TOKEN is not set. Declaring NEMO_TOKEN as required while providing an anonymous fallback is inconsistent and should be corrected. No other secrets are requested, which is proportionate to the task.
Persistence & Privilege
The skill does not request 'always' presence and does not include install-time persistence. The only potential privileged action is the implied need to read an install path and a local config path (frontmatter), which could give it access to files under ~/.config/nemovideo/ or to the agent's install location — the purpose of those reads is not explained.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install video-factory - After installation, invoke the skill by name or use
/video-factory - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Video Factory 1.0.0 — Initial Release
- Launches a batch video production tool for combining, editing, and exporting video clips up to 500MB.
- Supports MP4, MOV, AVI, and WebM input, exporting polished 1080p MP4 videos in 1-2 minutes.
- Simple upload, edit, and export workflows; automatically manages sessions and cloud GPU processing.
- Integrates free token retrieval for new users and seamless session handling.
- Offers clear user prompts for actions like uploads, exports, credit checks, and timeline status.
- Displays concise progress/status updates and handles backend errors with helpful guidance.
Metadata
Frequently Asked Questions
What is Video Factory?
create raw video clips into finished MP4 videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and marketers use it for... It is an AI Agent Skill for Claude Code / OpenClaw, with 44 downloads so far.
How do I install Video Factory?
Run "/install video-factory" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Video Factory free?
Yes, Video Factory is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Video Factory support?
Video Factory is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Video Factory?
It is built and maintained by francemichaell-15 (@francemichaell-15); the current version is v1.0.0.
More Skills