← 返回 Skills 市场
Video Editor Google Pixel
作者
vynbosserman65
· GitHub ↗
· v1.0.0
· MIT-0
89
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install 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...
安全使用建议
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.
功能分析
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.
能力评估
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.
如何使用
- 确保已安装 OpenClaw（本地或 Docker 部署）
- 在对话框中输入安装命令：
/install video-editor-google-pixel - 安装完成后，直接呼叫该 Skill 的名称或使用
/video-editor-google-pixel触发 - 根据 Skill 的参数说明提供必要输入，即可获得结构化输出
版本历史
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.
元数据
常见问题
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... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 89 次。
如何安装 Video Editor Google Pixel？
在 OpenClaw 或 Claude Code 对话框中运行命令「/install video-editor-google-pixel」即可一键安装，无需额外配置。
Video Editor Google Pixel 是免费的吗？
是的，Video Editor Google Pixel 完全免费，采用 MIT-0 许可证，可自由下载、安装和使用。
Video Editor Google Pixel 支持哪些平台？
Video Editor Google Pixel 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。
谁开发了 Video Editor Google Pixel？
由 vynbosserman65（@vynbosserman65）开发并维护，当前版本 v1.0.0。
推荐 Skills