← Back to Skills Marketplace
omgate234

VideoDB Monitoring

by omgate234 · GitHub ↗ · v1.0.1 · MIT-0
cross-platform ✓ Security Clean
222
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install videodb-monitoring
Description
Screen recording capabilities. Generate stream URLs, search recordings, get transcripts.
README (SKILL.md)

VideoDB Screen Recording Skill

Screen recording capabilities powered by VideoDB. Use this when the user asks for screen recordings, wants to search past activity, or needs transcripts.

Run commands from {baseDir} using npx tsx videodb.ts.

Prerequisites

1. Check API Key

Before using any commands, verify the API key is configured:

openclaw config get skills.entries.videodb-monitoring.env.VIDEODB_API_KEY

If not set or empty:

  • Ask the user for their VideoDB API key
  • If they provide it, set it for them:
    openclaw config set skills.entries.videodb-monitoring.env.VIDEODB_API_KEY 'sk-xxx'
    
  • If they don't have one, direct them to: https://console.videodb.io

2. Check Monitor is Running

openclaw config get skills.entries.videodb-monitoring.env.VIDEODB_IS_RUNNING

If not true, start the monitor:

cd {baseDir} && nohup npx tsx monitor.ts > ~/.videodb/logs/monitor.log 2>&1 & disown && sleep 3

Verify it started:

openclaw config get skills.entries.videodb-monitoring.env.VIDEODB_CAPTURE_SESSION_ID

If you get a session ID (e.g., cap-xxxxxxxx-...), the monitor is ready.

Commands

Get Current Timestamp

cd {baseDir} && npx tsx videodb.ts now

Returns current Unix timestamp (seconds since epoch).

Generate Stream URL

cd {baseDir} && npx tsx videodb.ts stream \x3Cstart_timestamp> \x3Cend_timestamp>
cd {baseDir} && npx tsx videodb.ts stream \x3Cstart_timestamp> \x3Cend_timestamp> --title "Checkout flow" --description "OpenClaw browser run"

Creates a playable recording URL for the time range. If --title or --description is provided, the generated player share page uses that metadata.

Start Indexing

Start indexing only when the user asks for search, summaries, or transcripts:

cd {baseDir} && npx tsx videodb.ts start-indexing

This starts:

  • transcript capture for system audio
  • audio indexing
  • visual indexing

You can also control them individually:

cd {baseDir} && npx tsx videodb.ts start-visual-index
cd {baseDir} && npx tsx videodb.ts start-transcript
cd {baseDir} && npx tsx videodb.ts start-audio-index

Stop Indexing

Stop indexing as soon as it is no longer needed to save cost:

cd {baseDir} && npx tsx videodb.ts stop-indexing

Individual stop commands:

cd {baseDir} && npx tsx videodb.ts stop-visual-index
cd {baseDir} && npx tsx videodb.ts stop-transcript
cd {baseDir} && npx tsx videodb.ts stop-audio-index

Search Recordings

cd {baseDir} && npx tsx videodb.ts search "user opened Amazon"

Searches indexed screen activity for matching events. If no visual index exists yet, start indexing first.

Activity Summary

cd {baseDir} && npx tsx videodb.ts summary              # last 30 minutes
cd {baseDir} && npx tsx videodb.ts summary --hours 2    # last 2 hours

Audio Transcripts

cd {baseDir} && npx tsx videodb.ts transcript           # last 30 minutes
cd {baseDir} && npx tsx videodb.ts transcript --hours 1 # last hour

Recording Workflow

When user requests screen recording of a task:

  1. Capture start time:

    cd {baseDir} && npx tsx videodb.ts now
    

    Store this as start_time.

  2. Do the work (browser actions, file editing, etc.)

  3. Capture end time:

    cd {baseDir} && npx tsx videodb.ts now
    
  4. Generate stream URL:

    cd {baseDir} && npx tsx videodb.ts stream \x3Cstart_time> \x3Cend_time>
    

    Optional player metadata:

    cd {baseDir} && npx tsx videodb.ts stream \x3Cstart_time> \x3Cend_time> --title "Task recording" --description "Captured during OpenClaw task execution"
    
  5. Include URL in response:

    Screen recording: https://rt.stream.videodb.io/...
    

    If the command prints a player page URL, prefer sharing that URL with the user.

Indexing is not started automatically by the monitor. If the user also wants search, summaries, or transcripts, start indexing explicitly before those commands and stop it afterwards.

Example

User: "Open example.com and send me the recording"

# Check prerequisites
openclaw config get skills.entries.videodb-monitoring.env.VIDEODB_IS_RUNNING
# true

# Start time
cd {baseDir} && npx tsx videodb.ts now
# 1709740800

# Do the work (open browser, navigate)
# ...

# End time
cd {baseDir} && npx tsx videodb.ts now
# 1709740830

# Generate URL
cd {baseDir} && npx tsx videodb.ts stream 1709740800 1709740830 --title "example.com walkthrough" --description "OpenClaw browser automation"
# 📹 Screen recording (30s): https://rt.stream.videodb.io/abc123
# Player page: https://player.videodb.io/watch?v=example-slug

Response:

Done! I opened example.com.

Screen recording: https://rt.stream.videodb.io/abc123

When to Use

User Request Command
"Record my screen while you do X" Use workflow above
"What did I do in the last hour?" start-indexing, then summary --hours 1, then stop-indexing
"Find when I opened the spreadsheet" start-indexing, then search "opened spreadsheet"
"What was said in that meeting?" start-indexing, then transcript
"Get the recording from 5 mins ago" stream with timestamps
"Record this and set the title/description" stream with --title and --description

Troubleshooting

If commands fail with "No capture session":

  1. Check if monitor is running: openclaw config get skills.entries.videodb-monitoring.env.VIDEODB_IS_RUNNING
  2. If not, start it (see Prerequisites above)
  3. If it shows running but still fails, restart the monitor

If summary/search/transcript say no index or no transcript:

  1. Start indexing with cd {baseDir} && npx tsx videodb.ts start-indexing
  2. Wait briefly for data to accumulate
  3. Retry the command
  4. Stop indexing with cd {baseDir} && npx tsx videodb.ts stop-indexing when done
Usage Guidance
This skill will: (1) ask for and store a VideoDB API key (VIDEODB_API_KEY); (2) start a background monitor process that requests screen-capture and optionally microphone permission and records your screen and system audio; (3) write logs to ~/.videodb/logs and update the OpenClaw config (~/.openclaw/openclaw.json) under the skill's own entries. These behaviors are consistent with its purpose but are privacy-sensitive — recordings and transcripts are handled by the VideoDB service, so only install/use this skill if you trust that service. Before installing: review the 'videodb' npm package and its source, confirm you are comfortable with a persistent recorder running on your machine, and only provide the API key from a trusted VideoDB account. Stop indexing and the monitor when not needed, and review the logs and OpenClaw config changes if you want to audit activity.
Capability Analysis
Type: OpenClaw Skill Name: videodb-monitoring Version: 1.0.1 The videodb-monitoring skill provides legitimate screen recording, transcription, and search capabilities using the VideoDB service. The bundle includes a background monitor (monitor.ts) that captures screen and audio data and a CLI tool (videodb.ts) for generating stream URLs and searching recordings. While the skill requires high-privilege permissions (screen/microphone access) and modifies the OpenClaw configuration file to store session state and API keys, these actions are explicitly documented and necessary for the stated functionality. No evidence of malicious exfiltration, obfuscation, or unauthorized command execution was found.
Capability Assessment
Purpose & Capability
The name/description (screen recording, stream URLs, search, transcripts) match the included CLI (videodb.ts) and monitor (monitor.ts). The skill requires a VideoDB API key (VIDEODB_API_KEY) and uses the videodb npm client to create capture sessions, index visuals/audio, and generate stream URLs — all expected for this functionality.
Instruction Scope
SKILL.md instructs the agent to check/set the VideoDB API key, ensure the background monitor is running (nohup npx tsx monitor.ts ...), start/stop indexing, capture timestamps, and run videodb.ts commands. The monitor and CLI request screen-capture and (optionally) microphone permissions and will record and upload streams/transcripts via the VideoDB client — this is within the described scope. The instructions do read/write the OpenClaw config at ~/.openclaw/openclaw.json and write logs to ~/.videodb/logs, which are used only to store skill state and logs.
Install Mechanism
There is no platform install spec (instruction-only skill), but package.json declares an npm dependency on "videodb"; the README instructs users to run npm install when installing the skill. Installing an npm package is a normal step but carries the usual supply-chain risk of third-party packages — review/audit the 'videodb' package before installing if you have concerns.
Credentials
The skill's primary credential is VIDEODB_API_KEY, which is appropriate for contacting the VideoDB service. The code also reads and writes skill-specific state variables (VIDEODB_IS_RUNNING, VIDEODB_CAPTURE_SESSION_ID, VIDEODB_MONITOR_PID) in the OpenClaw config; those are used to manage the monitor and are proportional to the skill's operation. No unrelated external credentials are requested.
Persistence & Privilege
always:false (no forced always-on). The skill spawns a background monitor process that persists until stopped and updates OpenClaw config to record its PID and session state — this is expected for a recording daemon. It does not modify other skills' configs and its persistent behavior is limited to its own skill entries.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install videodb-monitoring
  3. After installation, invoke the skill by name or use /videodb-monitoring
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
Version 1.0.1 - Removed `child_process` dependency from `monitor.ts` for writing config
v1.0.0
Initial release.
Metadata
Slug videodb-monitoring
Version 1.0.1
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is VideoDB Monitoring?

Screen recording capabilities. Generate stream URLs, search recordings, get transcripts. It is an AI Agent Skill for Claude Code / OpenClaw, with 222 downloads so far.

How do I install VideoDB Monitoring?

Run "/install videodb-monitoring" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is VideoDB Monitoring free?

Yes, VideoDB Monitoring is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does VideoDB Monitoring support?

VideoDB Monitoring is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created VideoDB Monitoring?

It is built and maintained by omgate234 (@omgate234); the current version is v1.0.1.

💬 Comments