← Back to Skills Marketplace
Video Editor Google Pixel
by
vynbosserman65
· GitHub ↗
· v1.0.0
· MIT-0
89
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install video-editor-google-pixel
Description
edit raw footage into edited MP4 clips with this skill. Works with MP4, MOV, WebM, MKV files up to 500MB. Google Pixel users use it for editing Google Pixel...
Usage Guidance
This skill appears to be a straightforward client for a remote video-editing service and only needs a single API token (NEMO_TOKEN). Before installing: (1) confirm you trust the endpoint domain (mega-api-prod.nemovideo.ai) and review its privacy/retention policy for uploaded videos, (2) if you’re uncomfortable storing long-lived credentials, use the anonymous-token flow or a throwaway token as described (tokens are short-lived), (3) ask the maintainer to clarify the metadata inconsistency about config paths (~/.config/nemovideo/) and whether the skill will read local install/config directories, and (4) remember any video you upload will be transmitted to and processed by the external service — don’t upload sensitive content unless you’ve verified the provider’s security/privacy terms.
Capability Analysis
Type: OpenClaw Skill
Name: video-editor-google-pixel
Version: 1.0.0
The skill is a legitimate integration for the nemovideo.ai cloud video editing service. It provides instructions for the OpenClaw agent to manage authentication, sessions, file uploads, and video rendering via a specific set of API endpoints (mega-api-prod.nemovideo.ai). The logic is transparently documented in SKILL.md, including error handling and telemetry headers, and it lacks any indicators of data exfiltration, unauthorized execution, or malicious prompt injection.
Capability Assessment
Purpose & Capability
Name/description (AI video editing for Pixel footage) match the runtime instructions: the SKILL.md describes uploading video files and calling a remote rendering API. The only required secret (NEMO_TOKEN) aligns with authenticating to that API. Minor inconsistency: registry metadata reported 'Required config paths: none' while the SKILL.md frontmatter lists a configPaths entry (~/.config/nemovideo/) — this is likely bookkeeping/inventory drift but should be clarified.
Instruction Scope
Instructions are focused on the service (token acquisition, session creation, uploads, render/export, polling). They do direct the agent to POST files and to include attribution headers. Two items to note: (1) the doc asks the agent to derive X-Skill-Platform by inspecting install paths (e.g. ~/.clawhub/, ~/.cursor/skills/), which implies reading the filesystem to detect install location; (2) the skill instructs generating and then using an anonymous token (NEMO_TOKEN) if none is present and to 'save' the session_id/token — behavior that is reasonable for session continuity but means tokens may be stored in the agent environment. Neither action is out-of-scope for a remote-editing integration, but both have privacy implications.
Install Mechanism
No install spec or code files are present — the skill is instruction-only and will not write or execute downloaded code on install. This is the lowest-risk installation model.
Credentials
Only one environment variable is requested (NEMO_TOKEN) and it is used to authenticate to the described nemo video API. The SKILL.md also describes creating an anonymous token via the service if none exists; no unrelated API keys, cloud credentials, or passwords are requested. The only slight proportionality concern is the earlier-mentioned configPaths entry in the frontmatter, which could imply the skill might read ~/.config/nemovideo/ — reasonable for this service but inconsistent with registry metadata and worth confirming.
Persistence & Privilege
The skill does not request always:true and does not ask to modify other skills or system-wide settings. It instructs saving a session_id and using/storing a short-lived NEMO_TOKEN (tokens expire after 7 days), which is appropriate for session-based remote rendering. The need to derive platform headers from install paths implies limited filesystem reads, but no elevated privileges are requested.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install video-editor-google-pixel - After installation, invoke the skill by name or use
/video-editor-google-pixel - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of Video Editor for Google Pixel.
- Edit and export Google Pixel phone footage (MP4, MOV, WebM, MKV, up to 500MB) directly through cloud-based AI video editing.
- Supports trimming, transitions, text overlays, audio tracks, and exporting to 1080p MP4.
- Simple setup with automatic free token generation and session management.
- Key actions like export, credits check, state, and upload are routed by user prompt.
- Includes error handling and tips for efficient editing workflows.
Metadata
Frequently Asked Questions
What is Video Editor Google Pixel?
edit raw footage into edited MP4 clips with this skill. Works with MP4, MOV, WebM, MKV files up to 500MB. Google Pixel users use it for editing Google Pixel... It is an AI Agent Skill for Claude Code / OpenClaw, with 89 downloads so far.
How do I install Video Editor Google Pixel?
Run "/install video-editor-google-pixel" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Video Editor Google Pixel free?
Yes, Video Editor Google Pixel is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Video Editor Google Pixel support?
Video Editor Google Pixel is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Video Editor Google Pixel?
It is built and maintained by vynbosserman65 (@vynbosserman65); the current version is v1.0.0.
More Skills