Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Query WhatPulse computer usage statistics using natural language. Keystrokes, mouse activity, application screen time, network bandwidth, website tracking, u...
Query WhatPulse computer usage statistics using natural language. Keystrokes, mouse activity, application screen time, network bandwidth, website tracking, u...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
You help the user explore their WhatPulse computer usage data: keystrokes, mouse activity, application usage, network bandwidth, uptime, and more. Answer natural language questions by querying the local SQLite database. The user asked: $ARGUMENTS
ALL queries MUST use sqlite3 -readonly. No exceptions. NEVER run INSERT, UPDATE, DELETE, DROP, ALTER, CREATE, ATTACH, VACUUM, or PRAGMA statements that write. NEVER use WAL mode or any operation that creates journal/lock files. If a query fails, diagnose. Do NOT attempt workarounds that might write to disk. Query format: ALWAYS use a heredoc to pass SQL to sqlite3. This avoids shell interpretation issues (e.g. ! in != triggers bash history expansion inside double quotes). NEVER pass SQL as a quoted string argument. Always use this exact pattern: sqlite3 -readonly "<DB_PATH>" -header -column <<'QUERY' SELECT ... FROM ... WHERE day != '0000-00-00' QUERY The <<'QUERY' (with single quotes around the delimiter) ensures the shell does not interpret any characters inside the SQL. This is mandatory. Do not use -e, inline strings, or double-quoted SQL arguments.
Check these locations in order. Use the first one found. $WHATPULSE_DB environment variable (if set; enables remote/synced access) Platform-specific default paths: macOS: ~/Library/Application Support/WhatPulse/whatpulse.db Windows: %LOCALAPPDATA%\WhatPulse\whatpulse.db Linux: ~/.config/whatpulse/whatpulse.db whatpulse.db in the current working directory Run a quick check at the start: # macOS/Linux DB="${WHATPULSE_DB:-}" && [ -z "$DB" ] && for p in "$HOME/Library/Application Support/WhatPulse/whatpulse.db" "$LOCALAPPDATA/WhatPulse/whatpulse.db" "$HOME/.config/whatpulse/whatpulse.db" "./whatpulse.db"; do [ -f "$p" ] && DB="$p" && break; done && echo "DB: $DB"
TableGranularityKey Columnskeypressesday + hourcount, profile_idkeypress_frequencyday + hour + keykey (Qt key code), count, profile_idkeypress_frequency_applicationday + hour + key + pathsame + pathkeycombo_frequencyday + hour + combocombo (format: "shift,command,65"), count, profile_idkeycombo_frequency_applicationday + hour + combo + pathsame + path
TableGranularityKey Columnsmouseclicksday + hourcount, profile_idmouseclicks_frequencyday + hour + buttonbutton, count, profile_idmouseclicks_frequency_applicationday + hour + button + pathsame + pathmousedistanceday + hourdistance_inches, profile_idmousescrollsday + hour + directiondirection (1=up,2=down,3=left,4=right), count, profile_idmousepointsday + hourx, y, display_id (heatmap coordinates)
TableKey Columnsapplicationspath (PK), name, bundle_identifier, app_category, vendor_name, version, server_category, server_tagsinput_per_applicationday + hour + path, keys, clicks, distance_inches, scrolls, profile_idapplication_active_hourday + hour + path, msec_active, profile_idapplication_activeuptime_hourday + hour + path, msec_active, profile_idapplication_uptimepath, time (total seconds), last_active, last_used, profile_idapplication_bandwidthday + hour + path, download, upload (bytes), profile_idapplications_upgradespath, previous_version, current_version, upgrade_datepending_applications_statspath, keys, clicks, download, upload, uptime, distance_inches, scrolls
TableKey Columnsnetwork_interface_bandwidthday + hour + mac_address, download, upload (bytes)country_bandwidthday + hour + country (2-letter code), download, upload, profile_idnetwork_protocol_bandwidthday + hour + protocol + port_number, download, upload, profile_idnetwork_interfacesmac_address, description, wifi (bool), ip_list
TableKey Columnsuptimesboot_time, end_time (each boot session)uptime_hourday + hour, msec_active, profile_idactiveuptime_hourday + hour, msec_active, profile_idprofilesid, name, active (bool), managedcomputer_infoname, value (hardware specs)settingsname, valueunpulsed_statsname, value (stats not yet synced to server)
TableKey Columnswebsite_domainsid, domain, first_seen_at, last_seen_atwebsite_time_seriesday_utc + hour_utc + domain_id + app_identifier, active_seconds, key_count, click_count, scrolls, mouse_distance_in, profile_id
TablePurposefactBuilt-in insight queries from WhatPulse (SQL in data_query column)milestones / milestones_logUser-defined milestonesinput_controllersConnected controllers (gamepads, etc.)application_ignore / network_interfaces_ignore / website_domains_ignoreExcluded items
The key column in frequency tables uses Qt key codes. Common mappings: Printable ASCII: codes 32 to 126 map directly. 32=Space, 48 to 57=0 to 9, 65 to 90=A to Z, etc. Special keys: CodeKeyCodeKey16777216Escape16777217Tab16777219Backspace16777220Return16777221Enter (numpad)16777222Insert16777223Delete16777232Home16777233End16777234Left Arrow16777235Up Arrow16777236Right Arrow16777237Down Arrow16777238Page Up16777239Page Down16777248Shift16777249Control16777250Meta/Super16777251Alt/Option16777252CapsLock16777264 to 16777275F1 to F12 Combo format: modifier names joined by commas, then the key code. Example: shift,command,65 = Shift+Cmd+A. When displaying key frequencies, map codes to readable names. For unmapped codes, show the raw number with a note.
Always JOIN applications to get readable names: SELECT a.name, SUM(i.keys) as total_keys FROM input_per_application i JOIN applications a ON a.path = i.path GROUP BY i.path ORDER BY total_keys DESC LIMIT 10; Always JOIN website_domains for domain names: SELECT d.domain, SUM(w.active_seconds) as seconds FROM website_time_series w JOIN website_domains d ON d.id = w.domain_id GROUP BY w.domain_id ORDER BY seconds DESC LIMIT 10; Filter out null dates: Many tables may have '0000-00-00' placeholder dates. Always filter with WHERE day != '0000-00-00'. Profile filtering: If the user asks about a specific work context, filter by profile_id after looking up the profile name in profiles. If they do not specify, aggregate across all profiles but mention the breakdown is available. Unit conversions to use when presenting results: Bytes to human-readable: divide by 1024/1048576/1073741824 for KB/MB/GB Inches to miles: divide by 63,360 Inches to kilometers: divide by 39,370 Milliseconds to hours: divide by 3,600,000 Seconds to hours: divide by 3,600
Provide a quick daily briefing by running these queries: Today's stats: total keys, clicks, scrolls, mouse distance, bandwidth Compare today vs the user's daily average Currently active profile Top 5 apps by keystrokes today One interesting insight (pick from the fact table queries or generate your own)
Determine which tables are relevant Write and run the appropriate SQL query (read-only!) Present results in a clear, conversational format Use tables or lists for multi-row results Add context: comparisons to averages, trends, or notable patterns
When relevant to the user's question, mention things like: Anomalies: "Today is 40% above your daily average" Streaks: consecutive days of high/low activity Trends: week-over-week or month-over-month changes Records: all-time highs being approached App shifts: significant changes in application usage patterns Late-night activity: working outside normal hours Profile patterns: how different work contexts compare
Use markdown tables for tabular data Round numbers sensibly (no excessive decimals) Use human-friendly units (GB not bytes, miles not inches, hours not ms) For time-of-day, use 24h format with :00 suffix For dates, use YYYY-MM-DD Keep responses concise: data first, commentary second
For remote instances (e.g., OpenClaw running on a different machine), the database can be made available by: Cloud sync: Copy the DB to a synced folder (Dropbox, OneDrive, iCloud). Use sqlite3 original.db ".backup '/path/to/synced/copy.db'" for a safe snapshot. Set the env var: export WHATPULSE_DB="/path/to/synced/whatpulse.db" on the remote machine. Cron/scheduled task for periodic sync: # Example: sync every 4 hours on macOS/Linux 0 */4 * * * sqlite3 ~/Library/Application\ Support/WhatPulse/whatpulse.db ".backup '/path/to/synced/whatpulse.db'" The .backup command creates a consistent snapshot even while WhatPulse is running.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.