← Back to Skills Marketplace
VideoMemory
by
Clamepending
· GitHub ↗
· v0.1.15
· MIT-0
180
Downloads
0
Stars
0
Active Installs
14
Versions
Install in OpenClaw
/install videomemory
Description
Start VideoMemory from OpenClaw and return the local UI link.
Usage Guidance
This skill appears to do what it claims (install and start VideoMemory), but before running it: (1) verify the package source — check the GitHub repo and confirm the package name and expected version (the README refers to 0.1.7 while the registry shows 0.1.15); (2) prefer using the OpenClaw plugin install path when possible and inspect the plugin code on GitHub first; (3) run npx --explain / --dry-run or use --safe --explain as recommended and review the onboarding plan output before executing onboarding; (4) avoid running npx -y blindly in sensitive environments — consider installing in a sandbox or VM first; (5) ensure you have backups and understand that installing the plugin will modify local files and may restart services. If you can, ask the maintainer for a signed release artifact or checksum for the package version you intend to install.
Capability Tags
Capability Assessment
Purpose & Capability
The name/description (start VideoMemory and return a local UI link) align with the commands in SKILL.md (openclaw plugin install, npx onboarding, health check). However the SKILL.md references specific package versions (npx @clamepending/[email protected] and repo-ref v0.1.3) while the registry metadata shows version 0.1.15 — the mismatched versions are unexplained and should be clarified.
Instruction Scope
The instructions direct the agent to run plugin installs and npx commands that will download and execute code from the npm registry and to restart/operate the OpenClaw gateway. These steps go beyond simple read-only queries and can change system state; the guide does not require checksums or other verification beyond a --safe flag and asks the agent to run the onboarding automatically after inspection (which could still execute arbitrary package install scripts).
Install Mechanism
There is no formal install spec, but the runtime instructions rely on npx -y @clamepending/[email protected] (dynamic fetch from npm) and openclaw plugin installation. Fetching and running packages with npx executes remote code; no integrity verification (checksums/signatures) or pinned, consistent versions are provided. Using the public npm package may be legitimate, but it increases risk compared with a vetted release or an explicit install artifact.
Credentials
The skill requests no environment variables or credentials, which is proportionate to its stated purpose. That said, the actions it instructs (installing a plugin, writing bridge files, restarting the gateway, opening a local UI) require local filesystem and service control privileges not called out explicitly in the metadata — the user should be aware these operations will modify the local OpenClaw installation and may require elevated rights.
Persistence & Privilege
The skill is not marked always:true and is user-invocable only (normal). Installing the plugin will persist in the OpenClaw instance (expected for plugin installs). This persistent presence combined with code fetched from npm increases the blast radius if the package is malicious, but persistence itself is coherent with the stated purpose.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install videomemory - After installation, invoke the skill by name or use
/videomemory - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.15
- Bumped Videomemory plugin version references from 0.1.6 to 0.1.7.
- Updated CLI commands to use videomemory package version 0.1.7.
- Changed default --repo-ref from v0.1.2 to v0.1.3 in onboarding and relaunch commands.
v0.1.14
Point VideoMemory onboarding at the first-class OpenClaw plugin package @clamepending/[email protected].
v0.1.13
Prefer first-class OpenClaw plugin install with safe CLI fallback.
v0.1.12
Use clean instruction-only skill pointing at VideoMemory CLI 0.1.3
v0.1.11
Use instruction-only ClawHub skill that delegates onboarding to the published VideoMemory CLI
v0.1.10
Remove secret and token handling from the safe ClawHub launcher
v0.1.9
Simplify safe ClawHub launcher to avoid generated secrets and provider-key scanning
v0.1.8
Run safe onboarding from bundled ClawHub launcher without remote bootstrap execution
v0.1.7
Verify the pinned VideoMemory commit before running onboarding launchers
v0.1.6
Bundle local onboarding launchers so OpenClaw can install from ClawHub without global npm install
v0.1.5
Keep VideoMemory skill eligible after ClawHub install while avoiding npx first-run scanner friction.
v0.1.4
Make VideoMemory onboarding seamless after ClawHub install by using pinned npx first-run commands and removing the helper binary eligibility gate.
v0.1.3
Simplifies marketplace onboarding text for smoother OpenClaw setup while preserving safe explain-first onboarding.
v0.1.2
Adds safer OpenClaw onboarding with packaged scripts, safe dry-run inspection, and VideoMemory update notifications.
Metadata
Frequently Asked Questions
What is VideoMemory?
Start VideoMemory from OpenClaw and return the local UI link. It is an AI Agent Skill for Claude Code / OpenClaw, with 180 downloads so far.
How do I install VideoMemory?
Run "/install videomemory" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is VideoMemory free?
Yes, VideoMemory is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does VideoMemory support?
VideoMemory is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created VideoMemory?
It is built and maintained by Clamepending (@clamepending); the current version is v0.1.15.
More Skills