event-log

Append session events to an immutable JSONL log at ~/.openclaw/events.jsonl.

5|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/JansenAnalytics/claudex --skill event-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-log
Source: https://github.com/JansenAnalytics/claudex/tree/main/skills/event-log
Command: npx skills add https://github.com/JansenAnalytics/claudex --skill event-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

An immutable, append-only JSONL event log stores Kite's session history to enable rapid context recall without scanning every previous file.

Core Features & Use Cases

  • Append-only log at ~/.openclaw/events.jsonl storing ts, type, session, summary, and meta for each event.
  • Enables quick context retrieval at session start, troubleshooting, and audit trails across restarts and multi-agent interactions.
  • Provides programmatic logging via event-log.cjs and a CLI for ad-hoc logging, querying, and stats.

Quick Start

Log the session_start event to begin a durable activity trail and then log subsequent events to build continuity.

Frequently Asked Questions about event-log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain session continuity for an AI agent across restarts?

An append-only JSONL event log maintains session continuity by securely storing session history at ~/.openclaw/events.jsonl, capturing timestamps, types, and summaries for rapid context recovery and quick retrospection across restarts without scanning previous files.

What is the best way to create an audit trail for multi-agent interactions and decisions?

An append-only JSONL logging mechanism creates an audit trail for multi-agent interactions by immutably recording events with optional metadata, ensuring every decision and action is securely stored for later troubleshooting and auditing.

How do I log session events programmatically using a JSONL format?

You log session events programmatically using the event-log.cjs API to append records to a JSONL file, defining event types with optional metadata to build a durable activity trail for ongoing sessions and error tracking.

Can I query session history and event stats from the command line?

Yes, you can query session history and event stats from the command line using the provided CLI, which supports ad-hoc logging, querying, and retrieving statistics directly from the append-only JSONL event log.

Does this append-only event log require any external dependencies?

No, this append-only event log has no external dependencies. It operates independently to write session events to a local JSONL file, making it lightweight and easy to integrate into existing agent workflows.