ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

LogBook

Write journal entries, search history, and export your personal log digitally. Use when journaling thoughts, searching past entries, exporting notes.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/ckchzh/logbook
Or

LogBook

LogBook is a data processing and analysis toolkit for querying, importing, exporting, transforming, validating, and visualizing datasets from the terminal. It provides 10 core commands for working with structured data, plus built-in history logging and a quick dashboard view. All operations are local — no external APIs, databases, or network connections required.

Commands

CommandDescription
logbook query <args>Query data from the local data store. Logs the query action to history for auditing.
logbook import <file>Import a data file into the local store. Accepts any file path as input.
logbook export <dest>Export processed results to a specified destination (defaults to stdout).
logbook transform <src> <dst>Transform data from one format or structure to another.
logbook validate <args>Validate data against the built-in schema. Reports schema compliance status.
logbook stats <args>Display basic statistics — total record count from the data log.
logbook schema <args>Show the current data schema. Default fields: id, name, value, timestamp.
logbook sample <args>Preview the first 5 records from the data store, or "No data" if the store is empty.
logbook clean <args>Clean and deduplicate the data store, removing redundant entries.
logbook dashboard <args>Quick dashboard showing total record count and summary metrics.
logbook helpShow help with all available commands and usage information.
logbook versionPrint version string (logbook v2.0.0).

Data Storage

All data is stored locally in ~/.local/share/logbook/ (override with LOGBOOK_DIR or XDG_DATA_HOME environment variables).

Directory structure:

~/.local/share/logbook/
├── data.log         # Main data store (line-based records)
└── history.log      # Unified activity log with timestamps

Every command logs its action to history.log with a timestamp (MM-DD HH:MM) for full traceability. The main data file data.log holds all imported and processed records.

Requirements

  • Bash (with set -euo pipefail)
  • Standard Unix utilities: date, wc, head, du, echo
  • No external dependencies, databases, or API keys required
  • Optional: Set LOGBOOK_DIR environment variable to customize the data directory location

When to Use

Metadata

Author@ckchzh
Stars3562
Views0
Updated2026-03-29
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-ckchzh-logbook": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags

#journal#diary#log#daily#writing#personal#productivity#notes
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.