← Back to Skills Marketplace
Video Trimmer App
by
peandrover adam
· GitHub ↗
· v1.0.0
· MIT-0
49
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install video-trimmer-app
Description
trim video clips into trimmed video clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for cutting unwanted sec...
Usage Guidance
This skill appears to implement cloud-based video trimming and needs a single token (NEMO_TOKEN); that is reasonable. Before installing, consider: 1) The skill uploads your video files to https://mega-api-prod.nemovideo.ai — do you trust this third party with potentially sensitive footage? Check their privacy/retention policy. 2) Ask where session tokens and session_id are stored (memory vs written to ~/.config/nemovideo/) and how long they persist; if they are stored on disk, ask how to revoke/delete them. 3) The SKILL.md will auto-create anonymous tokens if none are provided — test with non-sensitive video first. 4) The registry metadata and SKILL.md disagree about config path requirements; request clarification or source/homepage information from the publisher. If you need stronger assurance, ask for the service's privacy docs or for source code/host verification of the backend domain before proceeding.
Capability Analysis
Type: OpenClaw Skill
Name: video-trimmer-app
Version: 1.0.0
The video-trimmer-app skill facilitates video editing by interfacing with a cloud-based API (mega-api-prod.nemovideo.ai). The logic includes standard authentication via anonymous tokens, session management, and file uploads for GPU-accelerated rendering, all of which align with the stated purpose. While it requests access to a specific configuration path (~/.config/nemovideo/) and performs automated network requests for setup, these actions are narrowly scoped to the service's functionality and do not exhibit signs of malicious intent or data exfiltration.
Capability Assessment
Purpose & Capability
The name/description (video trimming, cloud GPU rendering) lines up with the API endpoints and upload/export flow described in SKILL.md and the single required credential (NEMO_TOKEN). However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata said 'Required config paths: none' — this mismatch is unexplained and may indicate the skill expects to read or write local config files.
Instruction Scope
Instructions direct the agent to check/set NEMO_TOKEN, obtain anonymous tokens via an external API, create and store session_id, upload user video files to an external service, and poll rendering endpoints. Uploading user files to a third‑party service is expected for a cloud render skill, but the doc does not specify where session_id or tokens are persisted (memory, agent storage, or the user's filesystem), and it references a local config path. The instructions also require adding attribution headers and explicitly tell the agent not to display raw API responses or token values — this is unusual but not necessarily malicious. Overall the scope includes network I/O and potential local config access; these are coherent with cloud processing but the persistence details are vague.
Install Mechanism
No install spec and no code files (instruction-only) — lowest-risk install model. Nothing is downloaded or written during install by the skill itself, according to the provided package data.
Credentials
Only one environment variable (NEMO_TOKEN) is declared as required and is the primary credential — that is proportionate for a third‑party API integration. The skill will auto-create an anonymous token if NEMO_TOKEN is absent; that behavior is documented but raises questions about where the obtained token/session will be stored. The SKILL.md frontmatter also mentions a config path (~/.config/nemovideo/) which was not listed in registry metadata — this is an unexplained request for filesystem access that could allow persistence of tokens or other data.
Persistence & Privilege
always:false and normal autonomous invocation are fine. Concern arises from unspecified persistence: SKILL.md instructs to 'store the returned session_id for all subsequent requests' but doesn't specify storage location or lifecycle, and frontmatter references a local config directory. This could result in tokens or session IDs being written to disk without clear user-visible controls or cleanup.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install video-trimmer-app - After installation, invoke the skill by name or use
/video-trimmer-app - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
video-trimmer-app 1.0.0
- Initial release.
- Trim, edit, and export videos (MP4, MOV, AVI, WebM up to 500MB) using a cloud-based processing backend.
- Automatic backend authentication and session management with up to 100 free credits.
- Support for quick trims, batch editing, and iterative workflows—all in 1080p MP4 output.
- Handles files via chat upload; responds to commands for export, credits balance, upload status, and more.
- Robust error handling and detailed guidance for supported formats and workflows.
Metadata
Frequently Asked Questions
What is Video Trimmer App?
trim video clips into trimmed video clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for cutting unwanted sec... It is an AI Agent Skill for Claude Code / OpenClaw, with 49 downloads so far.
How do I install Video Trimmer App?
Run "/install video-trimmer-app" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Video Trimmer App free?
Yes, Video Trimmer App is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Video Trimmer App support?
Video Trimmer App is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Video Trimmer App?
It is built and maintained by peandrover adam (@peand-rover); the current version is v1.0.0.
More Skills