← Back to Skills Marketplace
Video Editor In Browser
by
peandrover adam
· GitHub ↗
· v1.0.0
· MIT-0
119
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install video-editor-in-browser
Description
edit video clips into edited MP4 clips with this skill. Works with MP4, MOV, WebM, AVI files up to 500MB. content creators and marketers use it for editing a...
Usage Guidance
This skill appears to be a legitimate cloud-based video editor, but proceed with caution. Before installing, consider: (1) Privacy — uploaded videos and generated tokens are sent to mega-api-prod.nemovideo.ai; do not use for sensitive content unless you trust the service and its policies. (2) Token handling — the skill will create and store an anonymous token if NEMO_TOKEN is not provided; ask where tokens/session IDs are stored and how long they persist. (3) Metadata mismatch — the SKILL.md references a local config path (~/.config/nemovideo/) while the registry says none; ask the author to clarify. (4) Confirm the service domain and owner identity (no homepage or publisher metadata is present here). If you need stronger guarantees, only install skills with a verified owner, published homepage/privacy policy, and explicit explanations of token storage and data retention.
Capability Analysis
Type: OpenClaw Skill
Name: video-editor-in-browser
Version: 1.0.0
The video-editor-in-browser skill is a legitimate integration for a cloud-based video editing service (nemovideo.ai). It provides detailed instructions for an AI agent to manage authentication via NEMO_TOKEN, upload video files, and poll for rendering status. The skill's behaviors, including network communication with mega-api-prod.nemovideo.ai and file access for uploads, are strictly aligned with its stated purpose. There is no evidence of malicious intent, such as exfiltrating sensitive credentials (SSH/AWS keys) or executing unauthorized commands.
Capability Assessment
Purpose & Capability
Name/description match the runtime instructions: the skill talks to a nemo video backend to upload, edit, render, and return MP4s. Requesting NEMO_TOKEN as the primary credential is consistent. However, the SKILL.md frontmatter includes a required config path (~/.config/nemovideo/) while the registry metadata stated 'required config paths: none' — this mismatch should be resolved.
Instruction Scope
Instructions direct the agent to (a) generate an anonymous token by POSTing to https://mega-api-prod.nemovideo.ai, (b) create and store a session_id, and (c) upload user files (either multipart file paths or URLs). These actions are consistent with the editor purpose but involve sending user video data and session/auth tokens to an external service. The skill also instructs the agent to read install paths to set an X-Skill-Platform header and to read its own YAML frontmatter at runtime — both require filesystem access. The instructions say not to display raw tokens but do not specify secure storage location or retention policy.
Install Mechanism
No install spec or code is present (instruction-only), so nothing is written to disk by an installer. This is the lower-risk model for skills.
Credentials
Only one environment variable (NEMO_TOKEN) is declared and is appropriate for an API-based editor. But the SKILL.md will generate an anonymous token automatically if NEMO_TOKEN is missing — that grants the external service the ability to accept uploads and create render jobs on behalf of the user. The frontmatter's referenced config path (~/.config/nemovideo/) implies the skill might read or use a local config directory even though registry metadata listed none; that mismatch is concerning and should be clarified.
Persistence & Privilege
always:false (normal). The skill instructs storing session_id for the duration of the session and mentions orphaned cloud jobs if the client closes — this is expected for a remote render workflow and does not request elevated platform privileges. There is no instruction 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-editor-in-browser - After installation, invoke the skill by name or use
/video-editor-in-browser - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of Video Editor in Browser — edit and export videos online directly in your browser.
- Upload and edit MP4, MOV, WebM, or AVI files up to 500MB, then export 1080p MP4s.
- No software install required; all processing happens on cloud GPUs in 1–2 minutes per job.
- Simple, conversational commands for editing operations (trim, add overlays, export, etc).
- Automatic session and token management for seamless first-time setup.
- User prompts route intelligently to upload, edit, export, credit check, or status actions.
- Supports modern video and audio formats for both input and output.
Metadata
Frequently Asked Questions
What is Video Editor In Browser?
edit video clips into edited MP4 clips with this skill. Works with MP4, MOV, WebM, AVI files up to 500MB. content creators and marketers use it for editing a... It is an AI Agent Skill for Claude Code / OpenClaw, with 119 downloads so far.
How do I install Video Editor In Browser?
Run "/install video-editor-in-browser" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Video Editor In Browser free?
Yes, Video Editor In Browser is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Video Editor In Browser support?
Video Editor In Browser is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Video Editor In Browser?
It is built and maintained by peandrover adam (@peand-rover); the current version is v1.0.0.
More Skills