← Back to Skills Marketplace
Video Editing Ai Auto
by
peandrover adam
· GitHub ↗
· v1.0.0
· MIT-0
82
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install video-editing-ai-auto
Description
Skip the learning curve of professional editing software. Describe what you want — automatically cut dead air, add transitions, and sync to background music...
Usage Guidance
This skill appears to be a legitimate cloud video-editing integration, but review these before installing: (1) Source and trust — there is no homepage or publisher info; confirm you trust mega-api-prod.nemovideo.ai. (2) Config-path mismatch — the frontmatter references a local config directory (~/.config/nemovideo/) though the registry metadata did not; ask the author why the skill would need to read/write local config. (3) Token handling — the skill will mint an anonymous token if none is provided; ensure you understand where that token will be stored and its permissions/expiry. (4) File access — the upload examples reference local file paths; ensure the agent only uploads files you explicitly attach and does not scan arbitrary filesystem locations. (5) Privacy — uploading video/audio sends content to a third-party service; confirm the privacy/retention policy before sending sensitive footage. If you cannot verify the upstream service or the config-path rationale, treat this skill with caution.
Capability Analysis
Type: OpenClaw Skill
Name: video-editing-ai-auto
Version: 1.0.0
The skill is a functional integration for a cloud-based video editing service (nemovideo.ai). It provides the AI agent with clear instructions for managing authentication via the NEMO_TOKEN, handling sessions, and interacting with REST and SSE endpoints for video processing. The skill includes appropriate error handling and security instructions (e.g., not printing raw tokens). No evidence of data exfiltration, malicious code execution, or harmful prompt injection was found; the behavior is consistent with the stated purpose of automated video editing.
Capability Assessment
Purpose & Capability
The skill name/description align with a cloud video-editing API and the required NEMO_TOKEN credential fits that purpose. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that is not listed in the registry metadata (which said no config paths). That mismatch is unexplained: a pure cloud API integration should not need a local config directory unless it plans to read/write local config files.
Instruction Scope
Instructions are specific about creating anonymous tokens, opening sessions, using SSE, uploading files, polling render status, and returning download URLs — all expected for a remote render service. But the doc also asks to auto-detect an install path to set X-Skill-Platform and references a local config path in frontmatter. Auto-detection would require reading system/install paths; the instructions are vague about how to detect or what files to read. The upload examples use multipart file paths (e.g. -F "files=@/path") which, if followed literally, could cause the agent to read arbitrary local paths instead of only user-provided attachments. These scope items expand the agent's filesystem/network access beyond simple API calls.
Install Mechanism
Instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. This is the lower-risk install model.
Credentials
Only one credential (NEMO_TOKEN) is declared and that aligns with a cloud API. The SKILL.md also documents generating an anonymous token via an API call (100 credits, 7-day expiry) if no token exists; creating such a token is plausible but means the skill may request network calls to mint tokens and (implicitly) store them for the session. The earlier-mentioned config path in frontmatter is not justified by instructions and looks unnecessary for the stated purpose.
Persistence & Privilege
The skill does not set always:true and does not include an install that persists code. It asks to save a session_id returned by the API (expected for session flows) but gives no guidance about secure storage. Autonomous invocation is allowed (platform default) and not combined with an always:true flag or broad unrelated credential access.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install video-editing-ai-auto - After installation, invoke the skill by name or use
/video-editing-ai-auto - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of Video Editing AI Auto skill.
- Instantly auto-edits uploaded videos: automatically cuts dead air, adds transitions, and syncs to background music.
- Supports MP4, MOV, AVI, and WebM video files up to 500MB.
- Simple setup with automatic free token generation—no registration required for basic use.
- Cloud-based editing—no local install needed; jobs return downloadable MP4 in 1–2 minutes.
- Includes error handling, credits checking, and session management for a seamless workflow.
Metadata
Frequently Asked Questions
What is Video Editing Ai Auto?
Skip the learning curve of professional editing software. Describe what you want — automatically cut dead air, add transitions, and sync to background music... It is an AI Agent Skill for Claude Code / OpenClaw, with 82 downloads so far.
How do I install Video Editing Ai Auto?
Run "/install video-editing-ai-auto" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Video Editing Ai Auto free?
Yes, Video Editing Ai Auto is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Video Editing Ai Auto support?
Video Editing Ai Auto is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Video Editing Ai Auto?
It is built and maintained by peandrover adam (@peand-rover); the current version is v1.0.0.
More Skills