← Back to Skills Marketplace
Youtube Video Editing With
by
linmillsd7
· GitHub ↗
· v1.0.0
· MIT-0
115
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install youtube-video-editing-with
Description
Cloud-based youtube-video-editing-with tool that handles editing raw footage into upload-ready YouTube videos. Upload MP4, MOV, AVI, WebM files (up to 500MB)...
Usage Guidance
This skill appears to implement a cloud video-editing workflow and will upload user media to an external service (mega-api-prod.nemovideo.ai). Before installing: (1) Decide whether you trust that external provider with your videos (sensitive footage will leave your device). (2) Note the skill will either use NEMO_TOKEN from env or automatically obtain an anonymous token and store session state — ask where tokens/session IDs are persisted (the SKILL.md mentions '~/.config/nemovideo/'). (3) Verify the registry metadata vs SKILL.md mismatch (config path vs 'none' and NEMO_TOKEN labeled required but auto-obtained) — ask the publisher to clarify. (4) If you prefer control, set your own NEMO_TOKEN and confirm the agent will not create/retain tokens automatically. If any of these points are unacceptable or unclear, do not install or invoke the skill.
Capability Analysis
Type: OpenClaw Skill
Name: youtube-video-editing-with
Version: 1.0.0
The skill facilitates cloud-based video editing by integrating with a third-party API (mega-api-prod.nemovideo.ai). While its behavior aligns with the stated purpose, it contains a high-risk instruction in SKILL.md directing the agent to "process internally" any tool calls received via the remote Server-Sent Events (SSE) stream. This creates a potential remote code execution (RCE) vulnerability where the backend could trigger arbitrary local tools available to the agent. Additionally, the skill automatically 'phones home' to obtain an anonymous token and generates a unique client identifier upon first use.
Capability Assessment
Purpose & Capability
The name/description (cloud YouTube video editing) lines up with the endpoints and SSE-based render pipeline described in SKILL.md. Requiring a service token (NEMO_TOKEN) and a nemovideo config path is consistent with a hosted editing backend. However the registry header given to you earlier said 'Required config paths: none' while SKILL.md metadata lists '~/.config/nemovideo/' — this is an inconsistency in the skill metadata.
Instruction Scope
SKILL.md explicitly instructs the agent to upload user media to https://mega-api-prod.nemovideo.ai and to automatically obtain an anonymous token if NEMO_TOKEN isn't present. That behavior is coherent for a cloud editing service, but it means user video files (possibly sensitive) will be transmitted to an external service. Also the skill instructs the agent to 'connect automatically when a user first opens the skill' and to 'store the returned session_id' — it's not explicit where/how persistent storage is performed. The instructions do not request unrelated system files or other credentials, which is good.
Install Mechanism
This is an instruction-only skill with no install spec and no code files. That minimizes on-disk code risk; nothing is downloaded or installed by the skill itself.
Credentials
The skill declares a single primary env var (NEMO_TOKEN) which is appropriate for a hosted service. But the registry summary you were shown earlier listed 'Required config paths: none' while the SKILL.md metadata requests '~/.config/nemovideo/'. More importantly, the SKILL.md will auto-generate and use an anonymous token if NEMO_TOKEN is not set — so marking NEMO_TOKEN as 'required' in registry metadata is inconsistent. Automatic token creation means the skill can obtain credentials and use them without the user supplying secrets.
Persistence & Privilege
always:false (default) and the skill does not request system-wide privileges. However it instructs the agent to 'connect automatically' on first use and to 'store' session tokens; you should confirm whether stored tokens are persisted to the declared config path and for how long (SKILL.md says anonymous token valid 7 days). Autonomous invocation is allowed (normal) and combined with automatic token acquisition this increases the chance the skill will upload data without an additional explicit user action.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install youtube-video-editing-with - After installation, invoke the skill by name or use
/youtube-video-editing-with - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of YouTube Video Editing With AI.
- Edit and export YouTube-ready videos from raw footage using a cloud AI pipeline.
- Supports uploads up to 500MB in MP4, MOV, AVI, WebM formats; outputs 1080p MP4 in 1–2 minutes.
- Simple workflows: upload, describe edits (e.g., "cut dead air, add transitions"), and download.
- Automated authentication with free trial credits; session management for iterative editing.
- Direct mapping of user actions and prompts to common YouTube video editing tasks.
Metadata
Frequently Asked Questions
What is Youtube Video Editing With?
Cloud-based youtube-video-editing-with tool that handles editing raw footage into upload-ready YouTube videos. Upload MP4, MOV, AVI, WebM files (up to 500MB)... It is an AI Agent Skill for Claude Code / OpenClaw, with 115 downloads so far.
How do I install Youtube Video Editing With?
Run "/install youtube-video-editing-with" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Youtube Video Editing With free?
Yes, Youtube Video Editing With is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Youtube Video Editing With support?
Youtube Video Editing With is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Youtube Video Editing With?
It is built and maintained by linmillsd7 (@linmillsd7); the current version is v1.0.0.
More Skills