Interaction Logger

Append interaction logs to user-specific history files with atomic writes and rotation.

26|5|Updated Feb 19, 2026

Search Tags:#logging #session management #history #interaction #data persistence

Ready to run

npx skills add https://github.com/kunwl123456/zeroclaw-skills-collection --skill interaction-logger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Interaction Logger
Source: https://github.com/kunwl123456/zeroclaw-skills-collection/tree/main/interaction-logger
Command: npx skills add https://github.com/kunwl123456/zeroclaw-skills-collection --skill interaction-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of logging interactions, preventing common errors associated with manual file editing and ensuring compliance with logging rules.

Core Features & Use Cases

Atomic Writes: Ensures log integrity even during system crashes.
Log Rotation: Automatically manages log file size to prevent performance issues.
Dynamic Target Support: Logs interactions for different users to their respective history files.
Use Case: Automatically log every user-assistant turn in a conversation to a dedicated history file for later review or analysis.

Quick Start

Log a message from the assistant to the user 'zhy'.

Frequently Asked Questions about Interaction Logger

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

FAQPage Schema

How do I automatically log conversation history to a persistent file?▼

To log conversation history, you can automatically append user-assistant interactions to dedicated history files, abstracting JSON parsing and file I/O. This ensures every turn is recorded securely for later review or analysis.

How does atomic writing prevent data loss during interaction logging?▼

Atomic writing ensures interaction logging integrity by completing file writes as a single, uninterrupted operation. This mechanism prevents partial log corruption and data loss even if a system crash occurs during the process.

What is the best way to manage log file size for conversation history?▼

The best way to manage log file size for conversation history is through automatic log rotation. This built-in mechanism manages file growth by rotating logs, preventing performance degradation caused by oversized history files.

Can I log interactions for different users to separate history files?▼

Yes, you can log interactions for different users to separate history files using dynamic target support. This feature routes each user's interaction logs to their respective dedicated history file for isolated session management.

How do I sync conversation sessions for persistent history management?▼

To sync conversation sessions, you use the 'sync' action to manage persistent history across sessions. This handles session syncing by updating user-specific history files to maintain consistent conversation records.

Do I need to manually validate JSON schema when appending interaction logs?▼

No, you do not need to manually validate JSON schema when appending interaction logs. The process automatically abstracts schema validation and JSON parsing, preventing common errors associated with manual file editing.