← Back to Skills Marketplace
vcarolxhberger

Youtube Video Editor Transitions

by vcarolxhberger · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
127
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install youtube-video-editor-transitions
Description
Skip the learning curve of professional editing software. Describe what you want — add smooth transitions between all clips and export for YouTube — and get...
Usage Guidance
This skill will upload your video and audio files to mega-api-prod.nemovideo.ai and use/obtain a NEMO_TOKEN for API calls. Before installing: 1) Decide whether you’re comfortable sending your media to that external service (don’t use it for sensitive content you cannot share). 2) Ask the publisher to clarify why metadata lists ~/.config/nemovideo/ and why NEMO_TOKEN is declared required when the skill can obtain an anonymous token itself. 3) If you plan to provide a permanent NEMO_TOKEN, treat it like any API secret (use a least-privilege token, rotate it, and avoid embedding it in shared environments). 4) Because this is instruction-only with no code to audit, test with non-sensitive sample videos first and request the service's privacy/retention policy. If you need greater assurance, prefer a skill with a known publisher or open-source code you can review.
Capability Analysis
Type: OpenClaw Skill Name: youtube-video-editor-transitions Version: 1.0.0 The 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 anonymous tokens, handle video uploads, and process server-sent events (SSE) for video rendering. All network activity is directed to the stated domain (mega-api-prod.nemovideo.ai), and there is no evidence of data exfiltration, unauthorized file access, or malicious prompt injection. The instructions are well-aligned with the stated purpose of providing automated video transitions and exports.
Capability Assessment
Purpose & Capability
The skill's name/description, endpoints, and required NEMO_TOKEN are consistent with a cloud video-editing service. However, the metadata declares a required config path (~/.config/nemovideo/) and a required env var (NEMO_TOKEN) while the runtime instructions also include an anonymous-token flow to obtain a token automatically if NEMO_TOKEN is missing — that mismatch is inconsistent (either the token is required or the skill can obtain one itself).
Instruction Scope
SKILL.md explicitly instructs the agent to upload user media and to call specific nemovideo.ai API endpoints (session creation, SSE chat, upload, export, polling). That is coherent with the stated purpose, but it means user video/audio files and session metadata will be transmitted to a third-party backend. The instructions correctly limit actions to the service API and do not ask to read unrelated local files, though the frontmatter's configPaths suggests possible local config access (not explicitly used in the runtime steps).
Install Mechanism
This is instruction-only with no install spec or downloaded code. No install-time code is written to disk, which reduces supply-chain risk.
Credentials
Only NEMO_TOKEN is declared as required (primary credential), which is proportionate for a cloud API. The inconsistency is that the instructions provide an anonymous-token retrieval flow if NEMO_TOKEN is absent. The metadata also lists a config path (~/.config/nemovideo/) — it's unclear whether the skill will read/write files there. Require/env and metadata should be clarified before trusting credentials.
Persistence & Privilege
always is false and the skill makes no requests to change other skills or global agent settings. Autonomous invocation is allowed by default (normal), but the skill does not request elevated persistent privileges.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install youtube-video-editor-transitions
  3. After installation, invoke the skill by name or use /youtube-video-editor-transitions
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
youtube-video-editor-transitions 1.0.0 — Initial Release - Add transitions between clips in uploaded videos and export polished results for YouTube. - Supports MP4, MOV, AVI, WebM uploads up to 500MB; processes edits in 30–90 seconds via cloud GPU. - Simple setup: auto-generates a session and token for new users, with 100 free credits (7-day expiry). - All editing and exports run server-side — no installation or technical know-how required. - Includes built-in commands for exporting, credit checks, state viewing, and video uploads. - Provides user-friendly error handling and clear feedback throughout each workflow.
Metadata
Slug youtube-video-editor-transitions
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Youtube Video Editor Transitions?

Skip the learning curve of professional editing software. Describe what you want — add smooth transitions between all clips and export for YouTube — and get... It is an AI Agent Skill for Claude Code / OpenClaw, with 127 downloads so far.

How do I install Youtube Video Editor Transitions?

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

Is Youtube Video Editor Transitions free?

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

Which platforms does Youtube Video Editor Transitions support?

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

Who created Youtube Video Editor Transitions?

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

💬 Comments